New Cubasis user here, was excited to get started and learn.
Bought M-Vave SMK-25 MIDI controller/keyboard. Video for doing MIDI Learn seemed easy enough, until I tried connecting the Play, Stop, and Rec buttons to Cubasis controls.
None work. (everything else does; keyboard, knobs).
After wasting hours thinking I must be doing something wrong, it seems these controls/commands are blocked or not recognized by Cubasis. Is this correct?
In using MIDI Wrench app to capture if/what the SMK25 is sending, I see it sending SysEx commands. (see screenshot)
With your Midi keyboard connected to Cubasis, tap SETUP top right of Cubasis screen, select MIDI and turn on MIDI Learn, now tap LEARN, the transport controls should now be orange, tap the on screen PLAY button, now tap PLAY on your keyboard, do this for all remaining transport controls, (your Keyboard may have a STOP button, but Cubasis will not respond to it), when complete, tap Exit MIDI Learn.
Hope this helps.
Mike
I forgot to mention Cubasis does not respond to SysEx messages. When you tap the play button on your SMK25 you should see a Midi CC number, if you are only seeing SysEx code in Midi Wrench that is because you need to set your keyboard to send MIDI CC instead of MMC data.
For more details on MIDI Learn, tap Help/Set Up and scroll down to MIDI Learn, it covers everything you need to know.
If you intend using the eight external 360° rotary controllers for volume faders inside Cubasis, please read below:
Catch-Up Mode is only available for volume and pan. Imagine that you select a track that has its volume at 0dB in Cubasis, but your hardware MIDI controller’s fader is currently at its min position. When you start moving the fader up, the track’s volume will immediately jump to a very low volume value like -100dB. To prevent this, enable catch-up mode before assigning the mapping. This means that the track’s volume won’t change until the hardware fader’s value will match (or catch up to) the track’s volume, which is 0dB in our case. This will result in a smooth volume change from the moment your hardware fader reaches its 0dB position.
“I forgot to mention Cubasis does not respond to SysEx messages.”
Ahh, finally, the real answer - kind of. It’s obvious that Cubasis is not responding to SysEx commands in Midi Learn. This seems like a bug or oversight to me.
I see other threads asking for more complete MIDI Learn functionality. This is not just me. Others seem to be having issues w/MIDI Learn as well.
There is NO official documentation I can find that states that SysEx is not supported. Instead, the documentation and help files simply state that pressing appropriate controls (including record, play, etc) during Midi Learn DO map into Cubasis, when in fact they do not, apparently because Cubasis somehow missed that some controllers use SysEx for this? My point is that the SW should be clear about which MIDI protocols are or are not supported. Is that so hard? Would have saved me hours of time if this detail had been included in the help file. (BTW, appreciate that Steinberg even provides in-app Help! So few do these days.)
For the record, I DO appreciate all the great functionality of Cubasis. My intent is to support and encourage those asking for better MIDI Learn functionality and add my voice in hopes this will get attention in an upcoming update.
I am sorry but I have to disagree with you there, I and many others have enjoyed Midi Learn in Cubasis.
I have looked through different forums concerning the M-Vave SMK-25v2 keyboard and it is clear that you are not alone with your quest to use Midi Learn especially the transport controls. I have 6 Midi keyboards but only my last two have transport controls, I specifically searched for keyboards that were compatible by first reading their online manuals, if there was any doubt then I would not choose that particular keyboard.
I am a user like yourself (for 11years) and SysEx was something I also wanted to use, I wanted to use my external sound modules with Cubasis that required SysEx data to change many different parameters, but I was informed by @LSlowak who is the Cubasis project manager that SysEx is not supported and there are no plans for it being supported.
I found this on a forum and it offers help for your particular situation, I hope it is of use to you:
“All I wanted was to link the play, stop and rec buttons of this generic midi controller and boy oh boy what a rabbit hole it’s been… But I’ve finally figured it out and thought I’d share.”
Just another quick thought, when you enabled MIDI Learn in Cubasis, the transport controls turn orange, when you press one of them the outline of that control turns white with a small “x” next to it, did you tap on this “x” to clear the existing CC number before attempting to assign a new CC number from your external keyboard if your keyboard IS compatible, then it could be something simple that is preventing you firm applying new midi CC numbers.
Mike
MIDI learn ONLY works within Cubasis intneral instruments, transport and faders etc
It DOESNT work with third party AUV3, except for the RARe app that includes midi mapping which are few and far between
Please check that thread or ask Robert ! He knows better than I do
But midi learn only works for intneral Cubasis, whcih I don’t really mind since I use halion and Neo fm. But it shouldn’t be restricting 3rd parrrt auv3 paramaters from being mapped
This has nothing to do with an AUv3 plugin. This is mapping a bluetooth MIDI keyboard that has Play, Stop and Record buttons, to the Cubasis transport controls.
OK, whew, the things we learn … found an IOS app for the SMK-25 called “CubeSuite” that allows changing the midi commands being sent. I changed the SysEx command default for “Play”, to:
CC Channel=1, Controller=94, Value=1
In Cubasis, I tap Midi Learn,
Tap the Play button, it turns from green to orange (waiting for input),
I press the Play button on the keyboard, verify it sent the CC command by watching it in the Midi Wrench app, and verify the Play button in Cubasis shows CC94,
I press the “Exit Midi Learn” button in Cubasis to save the mapping …
then I press the Play button on the keyboard expecting Play to trigger in Cubasis,
and … nothing.
Are there typical CC mappings (Channel, Controller, Value) for transport controls?
I wonder if I’m using a combo not allowed/recognized by Cubasis?
These are the standard CC numbers that already assigned to Cubasis transport, but you can delete those numbers and assign your own keyboard transport numbers, I swap between keyboards depending on where I’m sitting whilst using Cubasis, the transport parameters in my photo are standard and work with my Nektar Impact LX25, but my Ovation Impulse 61 uses different parameter numbers for the transport, thankfully in the Midi Learn box in Settings there is a tab called PRESETS, both my keyboards and other devices are stored as presets so I just select a device and everything is set up.
You should not have to define a Midi Channel to sent Midi CC transport numbers, these are direct commands that are handled differently to Midi Channel parameters. You mentioned Bluetooth, are you communicating with Cubasis using this method?
@fixitmania53, thanks for hanging in there with me! Your screenshot and that post gave me the breadcrumb I needed. Here’s the solution: It’s not so much the CC, (which Cubasis shows), but the VALUE sent within that CC (which Cubasis does NOT show and is critical).
You mentioned the Nektar Impact LX25. I asked CoPilot (Bing AI):
“What is the midi control sequence sent from the Nektar Impact LX25 when the Play button is pressed?”
It responded " When the Play button on the Nektar Impact LX25 is pressed, it typically sends a MIDI Control Change (CC) message. Specifically, it sends a MIDI CC 117 message with a value of 127 to indicate the button press."
Ding, ding, ding! I had tried gobs of CC and value options, but never values above 67. Looks like Cubasis needs 127. Here’s the M-Vave CubeSuite configuration that WORKS!
Why is this simple fact not documented somewhere by Steinberg?
Anyway, moving on. Similar mappings work fine for the other transport controls.
Thanks again @fixitmania53 !
Neither of my Nektar or Novation keyboards have this information to hand, but the transport/octave and transpose functions fall under Global Control and can’t be controlled using MIDI CC numbers, that’s as much as I can tell you, but I am glad you are now sorted and I would not have given up until you were
Mike
if your keyboard IS compatible, then it could be something simple that is preventing you firm applying new midi CC numbers.
