[PD] Any problems else/blocksize changing subpatch blocking during dsp?

[Christof Ressi]

I also think that messaging an outlet in the "dsp" method is not a good idea and it's better to use a clock with delay 0. The user might take the output of [blocksize~] and accidentally do something which interferes with DSP graph generation, e.g. by resizing an array, creating/deleting objects, etc.

Christof

> Gesendet: Donnerstag, 16. Januar 2020 um 16:34 Uhr
> Von: "Charles Z Henry" <czhenry at gmail.com>
> An: Pd-List <pd-list at lists.iem.at>
> Betreff: [PD] Any problems else/blocksize changing subpatch blocking during dsp?
>
> Hi list,
>
> Is there any potential problem using [else/blocksize~ ] and setting
> the switch~ settings of a subpatch?
>
> blocksize~.c tells me that outlet_float is called during the "dsp"
> method.  Will "set" messages to sub-patches with [switch~] during
> "dsp" interfere with dsp graph generation?
>
> I have a solution (a subpatch named "switchbang") to delay the output
> by one dsp cycle.
> [inlet]  // bang input
> |
> [switch~]
> [bang~]
> |
> [outlet]
>
> But I'm wondering if I'm being overly cautious.
>
> Chuck
>
>
>
> _______________________________________________
> Pd-list at lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
>