New Keylab 49 Mk3... Issues.... Suggestions?

Today I got the 49 Mk3. I hooked things up. Got the midi control center. Updated the firmware and installed stuff (script/etc).

I already had V collection X. I use both Cubase 13 and Nuendo 13.

I can control things, but not as shown in the ‘how to’ video about how to implement Cubase for the keylab. It MOSTLY works… Sort of.

So, when I fire up a blank project (this is the case with both Cubase and Nuendo on Win 11), supposedly in DAW mode, I will be able to move through the tracks (which it DOES do), and, when on an instrument, click on the encoder and then two things should happen: The instrument should pop up on the Cubase monitor view (which works) and the screen on the Keylab should go into the Lab mode, in which you can see the instrument and get the navigation buttons and mappings on the knobs/sliders… This works on the FIRST instrument, but when I go to the second (or third, etc), the keylab doesn’t do the transition to the navigation/mapping part. the icon on the keylab screen also stays in that ‘text mode’, with just the name of the track selected. When I push down on the encoder, the instrument DOES pop up on the computer monitor. But, I have to go to ‘prog’ and choose ‘arturia’ to get the navigation. EVEN THEN, it doesn’t show the navigation buttons or map things on the keylab… The buttons do the navigation in the VSTi… I can change things. But, it just isn’t the same as Track 1…

I’m wondering if I messed something up along the way, but I’ve tried re-doing everything (even went into the Documents directory and removed the arturia stuff I found under Midi Remote…)…

I sure hope that I did a good enough job of explaining this. Ugh.

Thanks,

Dave

Hi,

I have already reported this problem to Arturia but they do not have a solution for now. The Keylab display only supports the first Arturia VSTi opened and cannot manage multiple instances.

It is always the first instrument that switches to Arturia mode that will remain displayed. I agree it is a rather annoying limitation especially since it is sometimes difficult to exit Arturia mode to return to DAW mode: sometimes the “back” button is inactive and you have to go back to the “program” key.

1 Like

Thank you for that info!

The following is just to make it known to Arturia that this is not cool…
Hopefully they’ll address the issue soon. Having only had the controller for a day now, I like it, but this is a pretty annoying ‘bug’. I looked around to see if there was any indication that Arturia will fix this any time soon, but didn’t find too much about it (saw the post on the steinberg forum that stated the info was sent to the dev folks a couple of months ago)… I got the keylab specifically for this functionality. I have a few weeks to decide if I want to return this and try a different controller. We’ll see.

Yes…the marketing videos are misleading.

The implementation in Cubase is far from perfect.

It’s a total mess if you use a mix of Arturia instruments and Analog Lab. Like the other guy said it seems to be dependent on what is the first instrument?

I’m seriously considering getting some kind of legal challenge on to Arturia on account of their misleading marketing.

1 Like

Since it has only been out a few months, I’m hoping that we’ll see a release of an update prior to my return window closes. Being this time of year, though, I’m doubting this will be the case… I agree that the marketing material was quite misleading. But, again, we’ll see…

Definitely not a bug. Just them apparently shooting themselves in the foot and releasing a product under those circumstances unfortunately. It’s insane to think this got the OK to hit the shelves.

There is a workaround, however. Not quite, but somewhat. Instead of loading individual plugins (Mini, APR 2600, etc.), you can load numerous instances of Analog Lab and you are able to open each one using the KeyLab. Not ideal but it’s all we can seem to do for now… and it would be a damn shame if these guys never fix this “issue”.

2 Likes