sletz

In our external, we need to stop (if running...) the DSP chain when dynamically changing it's signal inlet/outlet number. We can do that

- either in the patch where our external lives (using the method explained here : 

https://cycling74.com/forums/stopping-the-dsp-from-inside-an-external)

- even globally using the method explained in the last message, that is: object_method(gensym("dsp")->s_thing, gensym("stop")); is there is no explicit adc~/dac in the patcher.

But the thing is that DSP on/off state can be local to a patch: that is we don't want to re-start the DSP for all patchers using the previously described "global" way (calling start/stop on "dsp"). We should re-start DSP only for patchers where is was previously on. So we would need to iterate over *all* patchers, to properly handle the DSP state.

In our external, we need to stop (if running...) the DSP chain when dynamically changing it's signal inlet/outlet number. We can do that 

- either in the patch where our external lives (using the method explained here : https://cycling74.com/forums/stopping-the-dsp-from-inside-an-external) when the adc~/dac is located inside it, 

But the thing is that DSP on/off state can be local to a patch: that is we don't want to re-start the DSP for all patchers using the previously described "global" way (calling start/stop on "dsp"). We should re-start DSP only for patchers where is was previously on. So we would need to iterate over *all* patchers, to properly handle the DSP state. 

Stopping the DSP from inside an external (2)