H90 Midi – Cue a program without loading

[tessier.mathieu]

As title says, how to cue a specific program without loading it yet ?

In the midi implementation I only see increment and decrement cue, but can’t jump to a specific one.

thanks ! I love my H90 so far !

[joecozzi]

Hi tessier.mathieu,

It is not possible to cue up a non-sequential Program. I recommend organizing your list such that if you want to cue up a program without using the onboard controls, but rather, using MIDI, then assigning CC# to increment and decrement commands is the only way. 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.

[joecozzi]

When using a MIDI controller for Program Changes, we can think of each sound as cued up until you press a switch that executes a program change that goes directly to another sound and activates it. Maybe I’m misinterpreting what you’re trying to do but what’s the benefit of cueing up a sound as opposed to going directly to it with a button press, a program change. That’s the power of MIDI.

[tessier.mathieu]

I’m trying to figure out how to use my morningstar MC6 with my H90, that would work for me. I really like the bank mode on the H90. So I’m trying to jump from one bank to another with my MC6, instead of increment and decrement to the desired bank. (I don’t want to tap dance 10 time to get to bank 10)

Once I got to my bank, I thought I could chose the right program I’m looking for at that moment. Hence the bank cue or program cue questions.

Right now the best I can do is a PC change to one of the program of a bank.

 

Since the H90 have a nice bank mode, nice program name and nice screen, I don’t want to replicate all of those bank name and program name in my MC6.

But maybe I’m not having the right approach for using the two together.

 

thanks for the quick response !

[joecozzi]

tessier.mathieu wrote:

So I’m trying to jump from one bank to another with my MC6, instead of increment and decrement to the desired bank. (I don’t want to tap dance 10 time to get to bank 10)

The only way around this is to set up PC changes that correspond to the first Program in a Bank. So, to access Bank 3 you would send PC#4. To access Bank 10 you would send PC#28. Keep in mind this is going to load the sound, but if you’re doing this between songs, that’s okay. Otherwise, you could save those Programs in bypass mode to start, so when they are recalled they are in bypass mode until you activate.

tessier.mathieu wrote:

Once I got to my bank, I thought I could chose the right program I’m looking for at that moment. Hence the bank cue or program cue questions.

Using the method outlined still works because if you recall the first program in a bank, you will see all three Programs on the pedal.

[SepticMaiden]

joecozzi wrote:

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.

[Author]

Posts