If I connect a MIDI footswitch to a patchbay connector and use it to control a module element in latching mode, the latch state is carried through when I change to a new patch. Say I have patch A which has a footswitch on CC1 in the patchbay connected to the on/off button on the Sustainer module in latching mode. Patch B has the same CC1 connector attached to the on/off button on the Transposer module, If I load patch A and then press and release the footswitch, the Sustainer module is activated, which is what I’d expect. However if I then load patch B, the Transposer module is immediately activated, ie the latching state from the previous patch hasn’t been cleared. Possibly this is intentional, but is a problem for me as I usually always have any footswitch elements off to start with, then bring them in as required.
I’m running MG3 3.0.62 standalone on a MacBook Pro with Sequoia 15.3.2 for live performance.
Did you save Patch B with the “Expressive” setting (in the envelope editor) rather than the “Latched”?
I tried this and have no problems swithing between patches with “Latched” and “Expressive”(standard). Functionality is saved to patches correctly.
Thanks @LoFiLeiF - I should’ve explained more clearly, but I need the CC in patch B to be latching as well. I’m sure it wouldn’t be a problem for controllers in Expressive mode since I imagine they have no way to access latching states as they don’t need to, by definition. I assume it’s only an issue where you have 2 or more latching controllers, as I do.
Yeah, this won’t change in 3.0.63. I guess you are asking for either
a) a localized (non-global) latch state to be able to be saved to CCs in patches, or perhaps
b) a simple latch-state reset when switching patches.
If this is an isolated issue (involving just these patches A and B) you can of course set patch B to both LATCH&INVERT and you can switch between these from Patch A latch/on to Patch B latch/off.
You’d rather use a expression pedal since that is keeping the current output even when you change patches. A momentary footswitch is not giving a “new” signal when you changed the patch, I guess this is the problem you are facing.
Yes, pretty much. We had three choises in the old position: Standard (-), Latch or Invert.
But now, as it moved you get a choice between Expressive (standard) and Latch (as you described it) but with the addition of being able to also invert these.
Expressive is of course the one to use with any Expression pedal sweeps. You can still use that to turn stuff on/off too, but you can’t use a latch function for gradual incremental changes. It is just an on/off function.
The situation in this topic seems like it might be the same situation I described over here:
In that topic, I think the totality of my description of the use-case may have swamped the core observation, which is that MG3 UI items (eg. mix levels, chain on/off, etc.) which are tied to a CC in the Patchbay cannot be relied upon to retake upon patch reload the state they had when last the patch was saved.
It is correct to say that there is no auto saving any last state any patch was in, in MG3 at this point. You need to manually save any changes you want to have in the patches. Any position your pedal is in at the moment you recall a patch will be reflected.
To clarify, I’m only discussing manual patch saving, not any sort of “auto-saving”.
This is getting to the point, I think. However, unless I’m mistaken, MG3 cannot poll the quiescent status of my hardware expression pedals or switches. Only after they are moved is data generated to provide values to reference. IOW, immediately after reloading a saved patch, if I do not subsequently operate my hardware expression pedals or switches then there should be no values present for MG3 to instantiate. So why don’t the MG3 UI items set themselves to the state the patch was saved in? (rather than 0, or anything else)
Merely being tied to a CC knob should not affect the setting of a UI object in the absence of data actually coming in from that CC - I mean, logically, right?
Thanks for your helpful comments everyone, sounds like trying out 3.0.63 when it’s released is the way to go. In the meantime I have a workaround which is effectively the same as @LoFiLeiF’s option b), but option a) would definitely be my preference. I guess my point about the use case I described is that it seems to break the basic principle that a saved patch should always be recalled with the settings it was (manually) saved in - with the sensible exception of the expression pedal, as has been pointed out. In my situation the persistent latch state basically overrides the saved setting, which is not desirable…
