Hey, so i can play the keyboard fine, but none of the transport controls, like play or pause, record etc work. When i press the button there is midi data being sent i think, but the functions just dont work. I can only use it to play the instruments via the keyboard but i want to fully use all the functions this keyboard has to offer. I am not very technical with this stuff, as this was a keyboard i could always just plug and play. Any ideas why its not working fully and how to fix it? I have gone into the midi controller page, selected it, tried all the different midi/inputs and outputs for the keylab essential mk3 and none of them work.
Hi, if you open Studio->MIDI Remote Manager, does it show your Keylab connected? If so, which ports do you see assigned?
If you cannot see it connected, go to the next tab Scripts, scroll down to your model and see if itās deactivated. If it is, select it and then click on Enable Controller Script.
Hi Yes,
It shows as being connected .
Donāt see anything about ports connected unless I click on the Midi In and Midi out where I have all my devices and I can select a few for the Arturia . I have tried them all and none get the controller to work. Thereās like Midi, Mididin Midithru.
Whatās even stranger is when I go into the controller settings , I have tried mapping g the buttons manually and it does reckognise what buttons are being pressed but it doesnāt do anything .
Only thing that works is the Piano itās really frustrating as Iām very hands on and hate having to click on play / Pause / record etc
Can you please post a screenshot of the tab MIDI Controllers by going to Studio->MIDI Remote Manager, and selecting the Keylab? It should show in the bottom section the ports in use.
When I click the buttons on the transport it registers them , when I press the buttons on the controller nothing happens . Itās really frustrating clicking the play button and seeing the play button light up on the midi remote editor but then nothing happening when I press the actual button on the controller.
Itās like something is blocking the buttons being pressed from actually controlling the program even tho it is registering them. Maybe itās just impossible and I need to change daws cos I canāt work like this 
Hi,
The same topic seems to be here.
Found the fix , in the midi centre of Arturia I selected daw mode both, so Mackie and HUI. Then in cubase I selected the HUI for the midi input and output .
Thank god for that lol thanks for the help
1 Like
I honestly got confused and didnāt even know to which thread I was answering 
Sounds like a tricky situation. Sometimes, keyboards and software donāt talk too well at first. Have you checked if the keyboardās firmware is up-to-date? Also, there might be a setting in Cubase you gotta tweak for it to jive with your KeyLab. Iād say, check for any software updates for both the keyboard and Cubase. If that doesnāt cut it, maybe reaching out to Arturiaās support could lend a hand. They might have a quick fix or two up their sleeve!
I have fixed it now.
Had to select the correct midi ports and in the Arturia midi software select ābothā under where it says daw mode . Both referring to Mackie Control and HUI.
In cubase the midi Port you want for the in and out is the HUI one.
You can also choose to exclude the Mackie/HUI from āall midi inputsā in the midi section of steinberg menu
That will help you not to here the sound of the plug-in when youāre pressing the transport buttons on your keylab
That way you can always have the default āall midi inputā in every channel you haveā¦
I donāt know if it is still an issue, but I experienced the same problem.
Iāve downloaded āKeyLab Essential 61 mk3 Cubase DAW Integration Script Feb 20, 2024 11.36 MB 1.3.1ā from Arturia, imported the script into Cubase 13.30 and disabled all the Steinberg scripts for Arturia products. And this did the trick for meā¦
The script on the Aturia-Site can only be seen if you click on āshow archiveā
1 Like
For anyone else here using KeyLab Essentials (Iāve got KeyLAb Essentials 61), tip from pro84 worked for me. Was getting mismapped keys using Steinberg scripts with Cubase 13 or wherever they came from (might be residual from previous Cubase versions as I have upgraded in place for years) - grabbed Feb 20 2024 Cubase integration script from Arturia under Archives - disabled Steinberg scripts, imported Arturia one - works great now. Keyboard responds and also pots are responding in MassiveX though mapping to other VSTi like PhasePlant is going to need some work. But I am only using KeyLab for capturing performance and mod and pitchbend wheel primarily, rest I can edit using other more reliable inputs (Akai MPKmini is solid as a rock).
I really donāt know how people put up with all the screwing around getting these MIDI devices to work with more than the basics. Amount of time I spend poking around in settings getting things to just work as compared to actually playing and recording is just ridiculous.
1 Like
Worked for me, Thank you!!