Cubase receives the program change data, but it doesn’t do anything with it. The patchname selector

Cubase
1

Cubase 11 receives the program change data, but it doesn’t do anything with it. The patchname selector in the midi track inspector still remains the same, it doesn’t change like it used to in MicroLogic.

Guess I’ll just have to live with it not working, which means I am saving no time by using a board, I could just use VSTs at that point.

I am using an FA06 with MacOS 15.x.x and Windows 11, but I’ve tried Logic, Cubase Pro 14, Cubase Elements 11, Cubase Artist, Emagics MicroLogic AV, Reason, Pro Tools and the only one that was able to do anything with the PC data was MicroLogic AV from the 90s, how ever I really doubt my MacOS9, will even work with the FA06 or VSTs properly, so running legacy software is not an option, but I wish it was at this point.

I think Windows 10 used to work, but I am positive on this.

What do I change in Cubase 14 pro, so that it interprets the data and changes the patchname in the midi tractor inspector panel?

Help please?
Thanks

2

Hi and welcome to the forum,

The Patch Name selector is not dynamic. It doesn’t reflect the incoming MIDI data. The sound should change.

3

Ok, thanks. It used to be in Micrologic AV that the DAW could receive program changes and change them in the patchlist inspector, and I’ve seen it work in the past with older versions of Cubase.

Also can you answer this question: https://forums.steinberg.net/t/alt-k-onscreen-keyboard-does-not-work-anymore/987955

This used to work to out of the box too, but apparently there is a “script” or “setting” for everything now days.

4

Hi,

In Cubase, you can see the very 1sr value only, which you can either insert directly to Inspector, or Cubase gets it by importing MIDI file.

5

I’m talking about receiving program changes here iirc.

Cubase and even MicroLogic AV used to receive program changes, when you would send a program change from your board and have your patchname/preset list installed. It would reflect in the inspector of the track.

Cubase sees the data but does nothing with it anymore. Not sure if they are teaching college students that these programs can’t receive program changes anymore, but that is 100% not right; as it used to work in the 90s.

I was told you have to write a custom script for this to work anymore, standard patchlist.txt won’t work now days.

6

Hi,

Cubase receives the data (including Program Change data) and sends it out. It depends on the synthesizer, how it interprets the data.

Btw, in Cubase, you can see the data in the Key Editor or in the List Editor.

7

I am aware. Was told now days you have to write a custom script to interpret the data in the DAW to get the DAW to do something with it. Ugh.

Though on another note,
I think I figured out the midithru problem.

I can bind ctrt+shift+f7 or something in Cubase to toggle Midi Active Thru using Edit>Key Commands in Cubase.
Then I can use Bome Midi Translator Pro to send ctrl+shift+f7 when the Daw Control button on FA-06 is pressed – I think, I am not 100% sure.

If not with the DAW control button, then maybe I can bind another FA-06 button to send CTRL+Shift+F7? I’ve not tried it yet, but it seems like a workable solution. I would just need to create a script to show whether or not it is toggled on or off like a capslock indicator.

Thanks for the help,
FG

8

It did not work, the Bome thing did not know how to let cubase handle the delay, so I just remapped the right alt key to ctrl+shift+f7, which is not great, but it works for now. :S

9

Jo,

If the hardware button sends MIDI Message, you can use MIDI Remote Mapping Assistant to assign the function in Cubase.

1 Like
10

I’ll try ty, dunno if it does or what