How do I integrate an M-Audio Keystation 88 with Cubase 14?

Cubase
1

I would like to be able to control the basic transport functions of Cubase Pro 14 using my M-Audio Keystation 88, but I haven’t got the technical know-how. Can someone explain how to do this is in a clear cut, step by step manner?

2

Hi,

  • In the Lower Zone open the MIDI Remote tab.
  • Click the + button to Add MIDI Controller Surface.
  • Select Vendor, Model, Script Creator and set the MIDI Input and Port ports. Click the + button.
  • Add a Button object. On the hardware, one by one press the buttons, you want to use to control Cubase.
  • Once all buttons are learned, add the device.
  • Open Mapping Assistant.
  • One by one select the control and make the assignment. From the right panel (Function Browser), select Transport > Start, Stop, etc.
3

Thanks Martin,

For some reason my M-Audio Keystation 88’s transport and directional buttons aren’t registering with this midi controller setup in Cubase. I might just go ahead a get a more current controller like the ones offered by Nektar. They seem to be more Cubase friendly.

4

Hi,

this is a known issue with older MAudio keystation 88s - you probably have a mk1 or mk2, right?
TBH, I use one of these, too, as a simple MIDI keyboard for my 2nd setup. Anyways, I never really bothered to put much energy into solving this problem because I simply don’t need these bottoms…
Out of the top of my head: You could try to do a factory reset and choose the factory preset for Cubase/Nuendo and check if the transport buttons are now reflected in your MIDI remote. I would not hang my hopes up too high, though. I think they were built back in the days of Cubase SX…

Good luck!

5

Hello Reco29,

My Keystation 88 is probably an older version. I tryed a reset on the keyboard, but it’s not working.

6

Hi,

Does it mean, it doesn’t send any MIDI Messages? Or what kind of message does it send?

7

Sorry to hear that.
As I said, I didn’t bother because the rest of the M-Audio keystation works just fine. The transport buttons didn’t make a difference to me because I needed addition MIDI controls either way. My solution was to keep the M-Audio as an 88 keyboard and to buy an additional streamlined MIDI remote device.
Maybe this is an option worth considering for you as well?

Addendum: If you find a way how to get these transport buttons to be recognized in Cubase please share. It might not make any difference to me since I can’t even physically reach them (under my desk) but others might still be interested in a solution. Cheers!

1 Like
8

Martin,

My Cubase 14 Pro indicates that it’s receiving midi information via the transport and direction buttons on my Keystation 88, but the midi remote assistant isn’t recognising it.

9

I took the plunge and bought a Nectar Impact GXP88 on Amazon. Maybe it’ll be worth it.

10

Hi,

You can use the MIDI Monitor to see, what MIDI Message does Cubase receive.

11

Martin,

I don’t know how to determine exactly what midi information is being received by my Cubase 14 Pro, only to say that the remote midi assistant isn’t recognizing the transport and direction buttons, while the volume and modulation wheels are being recognized.
This is really too much bother for me but thanks for your advice.

12

I don’t think there is a direct solution to the problem.
I own an M-Audio Oxygen Pro and there are 2 modes with different midi ports. One is DAW via Mackie and the other is a kind of midi/performance mode.
The buttons you mentioned don’t work in midi mode. These buttons are also not listed in the Oxygen software editor in this mode.
But they do exist in DAW mode.
If you integrate the DAW mode into Cubase via Mackie, these buttons work even if you are in Midi mode and integrated via Cubase Midi Remote.

Unfortunately this solution does not work stable in Cubase.
That’s why I only use the midi mode in Cubase without the transport functions.
It would be possible to assign the functions to the existing pads or other existing buttons, but I have assigned them differently.

For transport functions, solo, mute, metronome etc. I use a Korg nanoKey Studio, which still fits perfectly on my desk. I find it very convenient after a certain familiarisation period.