hmm, what other info you can get from [r pd]? tnx
2013/4/28 IOhannes zmölnig zmoelnig@iem.at
On 04/28/2013 03:14 PM, Olivier Baudry wrote:
dear all
Is there any equivalent of Dspstate~ in puredata?
i don't know [Dspstate~], care to explain what and where it is?
in the meantime, you could try
[r pd] | [route dsp] | [print]
fgmsdt IOhannes
______________________________**_________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/** listinfo/pd-list http://lists.puredata.info/listinfo/pd-list
From: Alexandre Torres Porres porres@gmail.com To: IOhannes zmölnig zmoelnig@iem.at Cc: pd-list@iem.at Sent: Tuesday, April 30, 2013 11:43 AM Subject: Re: [PD] Dspstate~ in puredata
hmm, what other info you can get from [r pd]? tnx
You get literally anything sent to the "pd" symbol:
[hey rocky watch me pull a rabbit out of my hat( | [s pd]
[r pd] | [print from_pd]
However that one will also produce an error.
The valid methods are mostly (all?) in m_glob.c.
Still, there is a difference between inspecting messages that get sent to pd and querying Pd's global attributes.
Example: the pddp/dsp object tries to show dsp state by using a global s/r variable that newly created pddp/dsp objects can query, but you must _guarantee_ that the first pddp/dsp object existed before the user (or some other part of the program) decided to turn on dsp. Otherwise every single pddp/dsp will be inaccurate. This is because they all rely on [r pd] to get the dsp state.
Also very few of the methods are meant to be visible to the user. The "version" method is completely useless, while "sys_getversion" isn't even
accessible from within a pd patch (or designed to be). I made [pdinfo] so that the user can actually query all these attributes in a simple way using a single object.
-Jonathan
2013/4/28 IOhannes zmölnig zmoelnig@iem.at
On 04/28/2013 03:14 PM, Olivier Baudry wrote:
dear all
Is there any equivalent of Dspstate~ in puredata?
i don't know [Dspstate~], care to explain what and where it is?
in the meantime, you could try
[r pd] | [route dsp] | [print]
fgmsdt IOhannes
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-l2ork
-----Original Message----- From: pd-list-bounces@iem.at [mailto:pd-list-bounces@iem.at] On Behalf Of João Pais Sent: Wednesday, May 01, 2013 5:26 AM To: Alexandre Torres Porres; IOhannes zmölnig; Jonathan Wilkes Cc: pd-list@iem.at Subject: Re: [PD] Dspstate~ in puredata
accessible from within a pd patch (or designed to be). I made [pdinfo] so that the user can actually query all these attributes in a simple way using a single object.
where is [pdinfo] to be found?
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
----- Original Message -----
From: João Pais jmmmpais@googlemail.com To: Alexandre Torres Porres porres@gmail.com; IOhannes zmölnig zmoelnig@iem.at; Jonathan Wilkes jancsika@yahoo.com Cc: "pd-list@iem.at" pd-list@iem.at Sent: Wednesday, May 1, 2013 5:26 AM Subject: Re: [PD] Dspstate~ in puredata
accessible from within a pd patch (or designed to be). I made [pdinfo] so that the user can actually query all these attributes in a simple way using a single object.
where is [pdinfo] to be found?
In pd-l2ork
-Jonathan
-
Alexandre Torres Porres -
IOhannes zmölnig -
Ivica Ico Bukvic -
Jonathan Wilkes -
João Pais -
Olivier Baudry