Duplexing: Multiple instances of a subpatcher produce multiple responses
Project: Interface with a Yamaha Motif Rack synth.
Issue: Output duplexing.
Description:
At the core of the interface is a subpatcher “ParamRequest” which queries the synthesizer and outputs the response. Input (request) and output (response) are routed by send/receive objects.
The input is prefixed with a UID of the requesting routine so that ParamRequest knows where to send the response.
After the umptieth rebuild, the output duplexed inexplicably, until I discovered there were 2 instances of ParamRequest open, so that every send caused 2 responses.
Duh.
The question:
Is there a way to ensure that only a single instance of a subpatcher is open?
open ? You mean exist in a patcher ?
No, but it is esay to debug.
You use send/receive, so collect all send request IDs and check for duplicates.
By the way it would simplify things if you use a single object that requests/receives
parameters instead of subpatches.
Midi data has to be qued anyway.
send request, get data, forward parameter, go to next request
in case of a list of requests.
for individual requests,
like 20 buttons that execute it, you can anyway mouse only one at a time.
something like [onecopy] but for loading/still closed? no.
but you could block the output of any further instance of a patcher by giving them a serial number or by solo'ing an open gate before its outputs/sends.
