On 2018-06-18 16:30, Jean-Marie Adrien wrote: > … i think i did > just a question : is it possible to chain in a cascade : throw~ > -> catch~ -> throw~ -> catch~ ?? > hum, is chained indeed in the patch
your question is lacking details. since throw/catch is a N-to-1 connection, you cannot have more than one [catch~] of any given name. so the following patch is illegal and will print an error on the console: [osc~ 440] | [throw~ foo] [catch~ foo] | [throw~ foo] [catch~ foo] | [env~] (it will give you an error "warning: foo: multiply defined") however, you can easily and without problems chain up throw/catchs with different names: [osc~ 440] | [throw~ foo] [catch~ foo] | [throw~ bar] [catch~ bar] | [env~] using [throw~] and [catch~] without any explicit name (as in your question), will use an empty symbol "" (without the quotes) as the label. so to answer your question: not it's not possible to chain it up like that, as you are having multiple [catch~] objects with the same name. fgmasdr IOhannes side note for confusion: when chaining up multiple catch~/throw~ or s~/r~ objects, the order of execution may vary. so the output of the last [catch~] object might be delayed by one or more sample blocks (as compared to input of the first [throw~]). but the signal will come through nicely (just delayed slightly). PPS: have you checked phase cancellation?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
