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?
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.
1 Like
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.
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!
Hello Reco29,
My Keystation 88 is probably an older version. I tryed a reset on the keyboard, but it’s not working.
Hi,
Does it mean, it doesn’t send any MIDI Messages? Or what kind of message does it send?
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
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.
I took the plunge and bought a Nectar Impact GXP88 on Amazon. Maybe it’ll be worth it.
Hi,
You can use the MIDI Monitor to see, what MIDI Message does Cubase receive.
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.
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.
I’ve had the nektar IMPACT LX88+ now for about a month, and for me it was worth the cost to replace the M-Audio Keystation 88.
The only problem that I’ve experienced with the nektar (and it’s associated Cubase files) was not knowing how to properly make certain alterations in the default Studio Setup in Cubase. I’ve included two screen captures showing what nektar technical support recommended should be done.
Without disabling Smart Switch Delay (as the photo indicates), I could not get the record or loop buttons to work, so thanks to nektar technical support for their advice.
Maybe this will help anyone that’s experiencing the same issue.
Failed midi connection results. Too complicated to install. 
I also have an M-Audio Key Station Pro 88 that my new PC with Win 11 will not dance with. My PC tech is a computer tech for my home state in the US. We’ve both tried every possible connection and spent a couple hundred $ on new cables and a Mackie Onyx Producer 2+2 Sound card still with no success. It grieves me that I should pay Steinberg the $500+ for Cubase 14 Pro and still need to purchase a new weighted action keyboard controller in hopes I’ll have the connectivity success I need to keep producing projects with Steinberg’s Cubase with.
But I’m grateful I downloaded the 60 trial version of C 14 Pro just in case I ran into such issues… 
1 Like
I’ve been using a Nektar LX88+ for a couple years and the Cubase integration is excellent.
1 Like
Through the years, Cubase has gotten extremely sophisticated. Beyond the simple processes necessary for ‘me’ to produce the music I like to produce. Steinberg has come a long way in their support for producers and engineering techs. providing them with technical tools and systems that far exceed the simpler aspects of music compositions, and the tools immediately available to the musician/composer. Which IMO, translates to a smoother workflow especially in the MIDI camp where most of my music is produced.
That said, is it possible to download earlier programs of Cubase Pro such as C-6.5? Keeping the process simpler would certainly make my work flow smoother and faster W/out searching through layers of procedure, screen changes and sequential protocol which, each consecutive iteration of Cubase demands and requires.
It just seems as though Steinberg’s Cubase has left the simplicity of creating music behind for their competitive edge in the marketing arena. Again, it’s just my opinion.
Hi,
you can download any old Cubase version from the Steinberg download website.
Here’s C6.5
You will need a physical USB licenser to run it and you must install the latest eLicenser Control Center.
Enjoy!
Thanks a million! Just hope my old M-Audio and C-6.5 will dance together again! Thanks from the bottom of my heart!
1 Like
I have an old original dongle licensor. Will it work with a fresh C-6.5 download? Thanks. I will probably need to repurchase Halion Sonic and Groove Agent 4 that got lost on my pc collapse last month as well. That said, I would have been interested in downloading Cubase 14 Artist if my M-Audio Key station Pro 88 was guaranteed to work together. I’m presently having serious issues getting the key station to dance with the 60 day trial version of C-14 Pro. Thanks.
Hi,
please have a look at your MySteinberg account. You should see all registered licenses, including Groove Agent 4. No need to buy it again. You can run it with Cubase 14, too, if you download the eLicenserControlCenter and GA4 with the dongle plugged in. Halion SE is a free version and a free Halion player will be installed with Cubase 6.5 (it might have a different name like Halion Sonic - go with that one).
Which Cubase version do you own? If it’s a Pro version then you can’t downgrade to an Artist version.
The M-Audio 88 model’s essential functions like transpose, modwheel, pitchwheel, and of course the keys run well with every iteration of Cubase. The transport functions might work with older Cubase versions but are they really that important to you? Of course, that’s up to you. I have never needed them.