Home › Forums › Products › Stompboxes › H90 Midi – Cue a program without loading › Reply To: H90 Midi – Cue a program without loading

MIDI, as far as I’m aware, does not have a CUE UP equivalent to a PC command. By the very nature of how Program Changes work in MIDI, whenever one is executed it automatically loads the program.
This is true insofar as there isn’t a sperate command type that just cues a preset as opposed to cueing and engaging simultaneously, but some pedal manufacturers do separate the two behaviors (those being ‘switching to a present’, and ‘toggling on’) to PC commands for queueing, and CC commands for togging engage/disengage.
<span style=”font-size: inherit;”>For example, my Strymon Mobius (it’s the only one I own, but I assume there is some consistency across their product line) changes preset corresponding to the PC number received, but the pedal stays bypassed until it receives CC 102 (Value 127). </span>
The simple workaround in most cases, if a pedal doesn’t separate the two behaviors in question, is to send a PC command followed by a disengage command. This is the case for my Source Audio pedals- I send a PC command to cue the preset I want, and a disengage CC command to keep the pedal off.
As for the potential use case(s) for this, in my instance it looks lik this:
I have all my MIDI pedals chained together controlled by a Morningstar MC6 Pro connected to a 12 button AUX switch, with many of the AUX switches acting as master on/off toggles for each of my pedals. If I’m playing a song that I know is going to use a certain set of patches, but that maybe only starts with one or no pedals engaged, I can set a button on my MC6 to cue all of the effects that I want to use later in the song, so that I can just press my master on/off switch for a given pedal, and know that the preset I want is already cued.
The H90 doesn’t separate cuing presets and engaging when receiving a PC message as discussed in this thread- and it seems to me that it also won’t bypass the pedal, if a single button press on a midi controller is programmed to change a preset, then immediately disengage- the pedal stays engaged anyway. I’d love to be wrong about this or be mistaken in my methodology somehow, so please let me know if that may be the case!
Anyway, this has turned into quite the novel and my time may have been better spent finding a creative solution to my creatively created problem, but I felt like it was worth it to respond regarding the innate qualities of PC messages- it’s more about the pedal and the choices made by the maker regarding how it responds, than something intrinsic to PC messages.