Moog Music Forum

Hello, I currently have a workflow situation that I could use some help with.

I play live. My core is https://zaqaudio.com/ 4 channel midi sequncer as master -> Clock out to all channels -> TR-8, Moog sub 37 (midi ch 5), Blofeld (midi CH 4) etc etc

Within each channel I can store a program change to switch patches per sequence. This works fine I understand the 0-127 x2 for selecting all the patches on the Sub37. I have this working for my Blofeld as well and other devices that allow this.

ISSUE: When I specify a patch in the midi cc, it changes the patch, great, however when I start manipulating the controls and when the sequenced pattern comes around again it RELOADS the patch, wiping out my changes made over the last cycle of the pattern ie last 2 bars etc.

This means that I cannot save patches within my sequence as they will be reset each time and not allow me to perform on the Sub37, meaning I have to switch patches on the sub37 manually being cumbersome remembering which sequence stored is relative to which patch and or have the sub37 suequnce stored within the sub37 itself thuis making my 4 channel sequencer redundant aside from clock source. I don't want to do that.

I took this behavior overriding locally as normal as I can specify the patch I like on my Blofeld, it will allow me to make changes and not reset the patch unless I save or trigger a NEW patch. This allows me to perform with the Blofeld manipulating the controls ad infinitum even though each loop of the sequence is sending the program change for the current patch. Its friendly like that. the Sub37 seems to be absolute resetting each time.

QUESTION:
How can I mimic this behaviour of the SUB 37 so that I can trigger a program change which selects the right patch then allows me to modulate manually ad infinitum until I change patch again or save over the top of the patch and thus perform live with it.

WHAT I HAVE DONE SO FAR:
Reset init setting to make sure I did not stuff it up somehow, Toggled local control on off, tried all the different pot modes ABS, REL an THRU


Any help or setting I have missed that can facilitate this, thanks community hoping you gots the know how =)

If I understand correctly, you want the Sub37 to essentially ignore a patch change message if it's already on the requested patch. If so, I can't think of a way to make it do that.

I'm not quite clear on the workflow you're describing, however. I think you're saying you have a sequence stored on the Zaquencer, and that sequence starts with a patch change, so every time it loops, that patch change gets sent and the Sub37 reloads the patch, wiping out your local knob adjustments.

Would it be possible to rearrange your Zaquencer sequences so that the patch change is sent outside of the looping section of a sequence, or as a separate, non-looping sequence that runs just before the looping one?

For example, if the intent is to have a 1 bar looping sequence, make it a 2 bar sequence with the patch change in the first bar, and make it loop over only the 2nd bar. I'm not familiar with the Zaquencer, so I don't know if you can set an explicit loop point in a sequence. Alternatively, make a 1 bar sequence with the patch change that doesn't loop, followed by a looping 1 bar sequence that's identical except for the patch change.

In any case, I think the answer to your problem lies outside the Sub37.

Good luck!

--
Moose

Hi Thanks for your prompt reply. Yes I think you have understood my dilemma. It seems that other synths do this by default. My Blofeld for one. I will have to look at other options unless this setting can be implemented into firmware.

if (PatchChangeRecievedMidi == CurrentPatch ) {
Allow only local pot, switch control
}

I realise that with this kind of behaviour you end up having to switch to another patch then back if you want a true reset of the patch. Again this happens on my blofeld and I'm cool with that as with playing live it's fine.

I see your advice with looping after the cc change and not retriggering. I'll look into that and try.

Again I appreciate your thoughts on this. I might post my solutions when implemented...Cheers.