[PD-dev] bang [block~] to query current blocksize

[Hans-Christoph Steiner]

On May 25, 2008, at 12:31 PM, zmoelnig at iem.at wrote:

> Quoting Frank Barknecht <fbar at footils.org>:
>
>> with other messages later. Notice that I included "samplerate" here:
>> such an object could be a general info object for the dsp state
>> ([dspinfo~]?)
>>
>
> i think it is a good idea, but some remarks which nobody has  
> mentioned yet:
>
> afair [samplerate~] will give you the system-samplerate which might be
> different from the patch's samplerate. that's one of the reasons why i
> don't like miller's suggestion.
>
> [dspinfo~] sounds very generic too: i would expect to give me
> information about the system's dsp state rather than a patch's state.
>
> this might be nitpicking.
>
>
> anyhow, it would be nice to have an object telling me whether dsp has
> been turned on (or off!) in a certain sub-patch (as well as giving
> more info on this).
> i think the [r pd][route dsp] approach is a kludge...

Maybe this:

[dsp(
|
[s pd]


[r pd]
|
[route dsp]

A similar thing could be used for getting the block size, etc. from  
the patch, so you could send [; pd samplerate( to get the main  
samplerate, then [; pd-mypatch.pd samplerate( to get the current  
patch's samplerate, etc.

.hc

>
> mfgasdr
> IOhannes
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
> _______________________________________________
> PD-dev mailing list
> PD-dev at iem.at
> http://lists.puredata.info/listinfo/pd-dev




------------------------------------------------------------------------ 
----

You can't steal a gift. Bird gave the world his music, and if you can  
hear it, you can have it. - Dizzy Gillespie