Using Program Changes to select Performances

TransSynth · Post by **TransSynth** » Mon Feb 06, 2023 12:03 pm

I use my Modwave with Cubase DAW and I'm unsure how to use program change messages to remember a Performance inside a song. Using Cubase's own Bank/Program selector seems to produce only the Init Performance, no matter which bank or program is transmitted. Perhaps someone will advise me.

HardSync · Post by **HardSync** » Mon Feb 06, 2023 1:57 pm

I haven't yet tried sending program changes to mine, but the MIDI implementation chart shows that it receives only program change numbers 0 thru 63 and that it "Select Slots in the current Set List."

I take that to mean that you'll want to create a custom set list for the Cubase song(s) you're creating. That should simplify things greatly and avoid the INIT Performance patch. In the user guide, under the set list section, it says:

Set Lists let you group and order Performances for gigs or projects. A Set List has 64 Slots, arranged into four banks A-
D, corresponding to MIDI Program Change messages 1-64.

This means that you don't need to send a bank command -- only a program change command. The banks are used to access the performances from the Modwave itself.

What I don't know is whether you can send a Set List change command as well. I'm unsure if Korg released a full MIDI implementation spec for the Modwave. One thing you can try though is recording Set List Changes and Performance Changes from the Modwave to Cubase to see what the MW transmits and then send those back to the Modwave on playback to see what happens...

Derek Cook · Post by **Derek Cook** » Mon Feb 06, 2023 6:11 pm

Hi,

If it is anything like the Wavestate, and looking at the manual it looks like it is, then it will not respond to Bank Select CCs. On the Wavestate you have to first select your set list, and the program changes 0-63 will select slots 1-64 in the set list. So that at last should work

Given the memory architecture in the Wavestate (and I assume the Modwave), then I understand why Korg have gone for this approach, but I would prefer it if you could have some way of mapping Bank Select to different set lists. I may suggest that to them!

I have used Cubase to select patches on the Wavestate (in the current setlist), so not sure why you are having a problem.

TransSynth · Post by **TransSynth** » Tue Feb 07, 2023 8:29 am

HardSync wrote:unsure if Korg released a full MIDI implementation spec for the Modwave. One thing you can try though is recording Set List Changes and Performance Changes from the Modwave to Cubase to see what the MW transmits and then send those back to the Modwave on playback to see what happens...

Thanks, I'll try your suggestions.

HardSync · Post by **HardSync** » Tue Feb 07, 2023 9:29 pm

Both the Wavestate and Modwave have software editors. Do these use Sysex or some other protocol? If the former, then I presume it's possible to send sysex from Cubase to the MW. Korg really ought to release a full midi spec on these things, not just the simplified chart at the end of the manual.

Edit: I'm going to have to hook up my MW to my PC and see what it transmits...

pulsepsycle · Post by **pulsepsycle** » Sun Mar 12, 2023 5:16 am

HardSync wrote:Both the Wavestate and Modwave have software editors. Do these use Sysex or some other protocol? If the former, then I presume it's possible to send sysex from Cubase to the MW. Korg really ought to release a full midi spec on these things, not just the simplified chart at the end of the manual.

I fully agree on this one!

Edit: I'm going to have to hook up my MW to my PC and see what it transmits...

I tried MidiOX to see what is transmitted when changing banks or set lists: nothing.

If you stay within the same set list you have 64 performances available though by Program Change command.