MIDI Track Program Selector Not sending Correct Program Change Message to External Synth

Nickeldome · October 18, 2019, 7:40am

chikitin:

Nickeldome:

The midi program selector in the Inspector is nice for browsing sounds but unfortunately is doesn’t send the program change at startup of the project. As far as I know there are two ways of doing this within Cubase?

Create a program change entry in the list editor at the beginning of the track or where you want the program change to take place and edit the values so it will send the correct value.

Most synths can be manipulated to send the complete patch data in SYSEX format. Sometimes by just pressing the next patch button on the synth? Record this at the beginning of the track. As you start to play the project it will automatically send the patch data to you synth. Just make sure you have sysex on ‘chase events’ disabled. Otherwise it will send this information every time you start/stop playback. And you probably don’t want that to happen?

Thank you so much. I guess I did record the next patch event into cubase. Then I wrote a LE preset to push it back to the very start of the project and merged my first round of MIDI recording with that. It works. Thank you very much!

PS. The weird this is that when I change the patches in the program selector, it does not change back to the original. So the program change messages do not communicate with program selector in the inspector. I guess they should!

Maybe the change in the program selector is overruled by the event(s) you recorded on the track? You could test this by temporarily disabling the Chase events ‘program change’ option under preferences > midi.

Martin.Jirsak · October 20, 2019, 6:47pm

Hi,

Yes, I use an app to an external monitor, to be 100% sure what is going out from Cubase. On Mac I’m using MIDI Monitor app, on Windows you can use MIDI-OX.

Martin.Jirsak · October 20, 2019, 6:49pm

Yes, if any data is in the track, the data is sent at the position (even if it’s at the very beginning, Cubase sends the data at 1.1.1.0), which is always the data from Inspector.