blurk
12-17-2009, 03:03 AM
In the same project as for my question about play modes (http://five12.net/showthread.php?t=668), I'm observing some strange behaviour connecting up CV signals. I'm trying to set up a master stack containing GateSeqs that will trigger sequencers in other stacks. So I have a stack with 3 GateSeqs and each GateSeq in that stack has its Gate Out connected to a different CV out for the stack (i.e. 3 GateSeqs going to the 3 CV busses).
Then in another stack, I have 3 different DrumSeqs, so I connect one of the CV bus inputs to the Trigger Ins of each of the 3 DrumSeqs, i.e. one CV connecting to 3 different Trigger Ins. However, playback is only triggered for one of the DrumSeqs, not all 3 (yes, I have checked that I've set the play mode correctly in all 3). It's the lowest DrumSeq in the stack. I'd expect (since this is a fully modular system that allows me to make such connections) that the CV would get distributed to all 3 sequencers, not just the bottom one. Is my expectation incorrect or am I otherwise doing something wrong?
Anyway, to see if it's always only the bottommost seq that receives the CV signal, I thought I'd disconnect the connection from the CV bus to the 3rd DrumSeq by right-clicking on the destination, but the wire connecting them is still drawn. I right-click again, and no longer see the option to disconnect that connection, I only see "Disconnect All". I try that and the wire is still there. I try brute force and right-click at the source and it still lists all 3 connections (plus "Disconnect All"). I try to disconnect the specific connection then disconnect all, and all connections still remain.
I just checked again, however, and none of the DrumSeqs are now playing, so I guess internally the connections have been disconnected and it's only the GUI that's confused.
Odd.
Sigh. Here's the inevitable post edit due to investigating further after first posting. It appears that the connection made last is the one that sticks, not always the bottommost connection. Also, I have found a workaround by simply adding a CV Mixer to the top of the stack, connecting the CV bus to one of the CV Mixer inputs and connecting the CV Mixer's CV Out to the 3 DrumSeqs. So there is an inconsistency: sometimes you can connect a CV source to multiple destinations, sometimes not.
Then in another stack, I have 3 different DrumSeqs, so I connect one of the CV bus inputs to the Trigger Ins of each of the 3 DrumSeqs, i.e. one CV connecting to 3 different Trigger Ins. However, playback is only triggered for one of the DrumSeqs, not all 3 (yes, I have checked that I've set the play mode correctly in all 3). It's the lowest DrumSeq in the stack. I'd expect (since this is a fully modular system that allows me to make such connections) that the CV would get distributed to all 3 sequencers, not just the bottom one. Is my expectation incorrect or am I otherwise doing something wrong?
Anyway, to see if it's always only the bottommost seq that receives the CV signal, I thought I'd disconnect the connection from the CV bus to the 3rd DrumSeq by right-clicking on the destination, but the wire connecting them is still drawn. I right-click again, and no longer see the option to disconnect that connection, I only see "Disconnect All". I try that and the wire is still there. I try brute force and right-click at the source and it still lists all 3 connections (plus "Disconnect All"). I try to disconnect the specific connection then disconnect all, and all connections still remain.
I just checked again, however, and none of the DrumSeqs are now playing, so I guess internally the connections have been disconnected and it's only the GUI that's confused.
Odd.
Sigh. Here's the inevitable post edit due to investigating further after first posting. It appears that the connection made last is the one that sticks, not always the bottommost connection. Also, I have found a workaround by simply adding a CV Mixer to the top of the stack, connecting the CV bus to one of the CV Mixer inputs and connecting the CV Mixer's CV Out to the 3 DrumSeqs. So there is an inconsistency: sometimes you can connect a CV source to multiple destinations, sometimes not.