[PD] query dsp state

[Joe White]

>
> I don't understand how this will report a wrong value. If you start Pd and
> turn the DSP on, then [f ] will hold 1, right? If you bang it, it will
> output 1, which is the DSP state. And if you turn the DSP off, it will hold
> 0. How is that wrong?


If the abstraction/patch is instantiated *after* DSP has been turned on
then the [f ] object (within the respective abstraction) will not hold the
correct value as it never received a change. I think this is case with
respect to Katja's original problem when opening help patches.

On 12 January 2015 at 15:28, Alexandros Drymonitis <adrcki at gmail.com> wrote:

>
>
> On Mon, Jan 12, 2015 at 5:11 PM, IOhannes m zmölnig <zmoelnig at iem.at>
> wrote:
>
>> On 01/12/2015 09:49 AM, Alexandros Drymonitis wrote:
>> > Why not store what [r pd] -> [route dsp] outputs to [f ]'s right inlet,
>> and
>> > bang the left inlet whenever you want to know the dsp state?
>>
>> maybe because it reports the wrong value if you:
>> - start Pd
>> - turn DSP on
>> - query your [dspstate] abstraction (that implements your suggestion)
>>
> I don't understand how this will report a wrong value. If you start Pd and
> turn the DSP on, then [f ] will hold 1, right? If you bang it, it will
> output 1, which is the DSP state. And if you turn the DSP off, it will hold
> 0. How is that wrong?
>
> _______________________________________________
> Pd-list at lists.iem.at mailing list
> UNSUBSCRIBE and account-management ->
> http://lists.puredata.info/listinfo/pd-list
>
>


-- 
Follow me on Twitter @diplojocus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20150112/42b9f3f0/attachment.html>