The KeyLab was set up right. Cubase was listening on the wrong port.
A composer got in touch about his Arturia KeyLab 49 mkII and Cubase 14 on Windows 11. He’d followed Arturia’s tutorials and thought he had it set up correctly, but the keyboard did strange things in Cubase. Moving a fader would play a note. Playing a note would move a fader.
Starting again, step by step
We connected on AnyDesk. I went through what he’d done so far against Arturia’s own instructions, then we started the setup again:
- Checked the keyboard was installed properly in Arturia’s MIDI Control Center, and that Windows Device Manager could see it.
- On the keyboard’s front panel, set the mode to DAW control for Cubase.
- In Cubase’s Studio Setup, used Add Device (top left) to add it as a remote device, Mackie Control, rather than setting it up as a control surface.
- Chose the MIDI input and output ports for that device.
What was wrong
That last step was where it had gone wrong. The KeyLab shows up twice in the list, and he’d most likely been using the first one.
It needed the second port.
I think the first port is the MIDI In socket on the back of the keyboard. With the second port selected, we loaded one of his projects and tested everything. The keys played sounds, play and stop worked, the transport controls worked, and the faders moved what they should.
He’d done everything right apart from that one last step. The whole thing took about 45 minutes.
If your KeyLab’s faders are playing notes in Cubase, check which of its two ports Cubase is listening to.
Not sure it’s the same problem? Ask a question first
