Hi,
Just bought a Arturia keylab 61 mkII for integrations with my cubase pro 11.
Alle midi seams to work ok, vst are shown in cubase, learning cc works but when hitting the transport buttons on the arturia a sound is triggerd instead of de transport functions.
Does anybody know this issue? operating system windows 10. Tried several remode devices (mackie control, mackie hui) but I presumed integration between arturia and cubase shoul be plug and play?
perhaps these screenshots will give you some clues.
In the āMidi Port Setupā section of āStudio Setupā, is there a separate entry for the transport buttons of the Arturia, such that you can choose to uncheck the box āIn All Midiā.
Those transport buttons have to be removed from the āall MIDIāā¦ and then setup to control the transport (see how Iāve done it for my M-Audio Axiom in the second pic.)
Hi, so you had to manually assign the controller within cubase?
I will try that to figure out how it works, in mean while also waiting for arturia support, because normally thereās a already made protocol wich should work immediately without manually putting it within studio setup.
Thanks so far
Iām curious to see what you find out. I feel like whatever Arturia offers, itās probably something to do with configuring these same settingsā¦ automatically, I presume.
Iām interested in upgrading my controller myself, and I see the key lab has some nice features.
Well, they say look at KeyLab MkII - Tips & Tricks KeyLab mkII FAQ (arturia.com)
But for cubase you have to select the mackie hui I think, but has only 2 buttons available ?
Second picture i followed you hint.
on the arturia I preselected in DAW mode the Cubase template, but transports wonāt work.
Yes, I Bought this one because alle the contollers, but itās my first time experience with a midi controller (and only 5 months with cubase)
The Arturia instructions say to select Mackie Controlā¦ not Mackie HUIā¦
In the second pic, you donāt want to deselect BOTH of them. You want the KeyLab to play MIDI notes using the keyboard, but NOT using the transport controls. But I donāt know if deselecting one of those will fix the problem.
BUTā¦ maybe you donāt need to do any of the above and just follow the Arturia instructions closely regarding the āMackie Controlā, and that will fix everything.
Tadaaaaā¦ grinning:
Ok Shagazulu, Thanks!
By first attempt I did select the Machie Control, but it didnāt work, maybe because the in All MIDI was selected. I immideately started searching Forum and read that Cubase uses the Machie HUI instead, so started tryin everything with this settingā¦didnāt work.
Now I did selct the MAckie Control again and Itās working, transportbuttons, faders, knobs I think you would like this Midi controller to! I go playing wiht it and will brief you about my experiences If youād like?
thatād be great. Iām interested to see how you get on with it.
So, you have deselected BOTH of those āin All MIDIā checkboxes that relate to your Arturia? It seems like you might only need to deselect one.
If you go to your MIDI track, or your instrument track, whichever youāre using, and you go to the area where it says to select your Midi Inputā¦ did you select Arturia Keylab there? Because thatās what you will always have to do UNLESS you allow the Arturia to be āIn ALL MIDIā by checking at least one of those checkboxes.
youāre right, thes are my current settings. So I unchecked only the MIDIN2 because that one is used by the Mackie control.
I wired both the USB and the 5-pin DIN midiās. USB to computer directly Ad 5-PIN DIN in/out Steinberg UR22mkII. Donāt know both are necesarely, but its working!
1 Like
Both arenāt necessary, and thatās probably why you were getting the transport to play midi notes, Iām guessing.
If you detach the MIDI cable and just use USB, does the āMIDIIN2 (KeyLab mkII 61)ā entry go away completely, and therefore its āIn ALL MIDIā checkbox doesnāt need to be unchecked?
Still functioning, also with the cables unplugged.
Arturia support did advise me to reset preferences within Cubase also and put the global controls in manually as suggested on their site. Functioning very well. Now starting to discover al possibillities. First impression? Faders and transport controls are ver time saving.
1 Like
very cool.
Iāve used controllers in the past, and i found I just ended up using the mouse and computer keyboard still, mostly. I do have little Steinberg device that I use to control monitor switching in the Control Room, and source switching But the transport buttons I programmed on there, I donāt use. I donāt even use them on my keyboard controller in front of me since I have to reach for it. The computer keyboard is just too handy. So, placement is key to getting the most out of your new toy. Enjoy!
So hereās an update. Iām now using the keylab mkII61 controller for aproximatly 6-7 months. Still exploring new featurs to combine with cubase. The features of cubase are huge and I think I need 48 hours each day to explore them all, so you can imaging how much it will take to combine it with the midi controler 
But Iām getting used working with the controller. Especially playing the vst instruments within Cubase for example Halion. It works very easy to us the 16 drumpads and assign them. I find myself using a combination of keyshortcuts and the midicontroller to have a nice workflow in Cubase. The faders and knobs are very usefull to do some tweaking.
Thatās it for now. Thanks again for helping me starting with it primarily.
2 Likes
Oh, great. Thanks for the update.
keylab MKIIā¦ Iām still interested. My old MAudio Axiom might soon need to be sidelined., so I appreciate the feedback.
Best.
And happy new year!
Mike
This is an excellent thread. I have a Keylab Essentials 61 and am considering Cubase after having a nightmare of a time setting it up in both Reaper and Cakewalk. Itās good to know it works well in Cubase (which one would expect). One question I have though is this: I assume you have your faders controlling track volume by default, and knobs Pan, and your transport controls work as expected. Now, the question is, can you also use a Learn function in your Plugins to, say, temporarily assign a fader to control an FX parameter (like Cutoff), and use that for writing automation (at the same time as everything else working as it did before the Learn?). In Reaper, I can either have the faders control the track volume, or set them up so that I can use Learn to control the FX params, but not both at the same time. In Bitwig, this process is extremely EASY and seamless, and works like a charm, but it lacks a lot of functionality I need.
Thanks for posting the update. It will be useful in the future. Cheers.
Hi, Iām using the Keylab for 1,5 year and must say still exploring all possibilities. Not only for the keylab but also for Cubase, beacause you can use it āsmallā but when you dig into it, the sky is the limit
Within cubase 12 Pro there is a new feature called midi remote control. The keylab essential is pre-programmed and ready for use.
Then depending on what is selected (Halion, Padshop, Retrologue or other VST, there are quick controls pre-programmed or you can use the ālearn ccā.
There you can use the write automation when recording this specific track.
So this is where the fun begins. Assigning the buttons means youāre ready to tweak you plugin synthesizers and create youre own unique sounds.
Cheers
1 Like
YES!! Three days ago, I downloaded the 60 day trial and have been exploring it. The new MIDI Remote panel is pretty incredible. It recognized my Keylab Essential 61 upon launch and all the transport functions worked perfectly. This is because Steinberg created a Javascript script that maps the keyboard and binds the CCs for the MIDI Remote panel. It looks like pretty straightforward code, which should make it easy for manufacturers to build one for each of their products. Apparently, they didnāt notify Arturia that they were doing this, so there are no other scripts available at the moment (guess we got lucky here). I would think the API would have been published way before the V12 launch. Not sure that Steinbergās thinking is here.
At any rate, yes the mapping is easily achieved, and the QCs are a really nice feature.
FINALLY somebody it taking the lead in making some sense out of the MIDI interface nightmare. Fingerās crossed. 
