Yeah, this is mostly the same settings as shown in my previous workaround post. Support got back to me as well with the above solution and keeping at least the KeyLab Output ports unchecked seem to work a bit more reliable. However, depending on anyone’s setup, you may want to check other Output ports for controlling external gear.
Keeping the Output ports unchecked also have the advantage of Arturia mode still working when you close and relaunch Live.
Yet replacing one Arturia VST with another occasionaly breaks Arturia mode and KeyLab won’t show the extended mode. I guess something is still broken somewhere, be it in Live, the controller script or KeyLab’s firmware.
Your suggestions are pretty consistent with the instructions I received from Arturia’s tech support, Simon. Unfortunately, in my case, this has not resolved the issues running Arturia’s vst3 instruments on Windows 11 home with Ableton Live 12 Suite on an Asus Zenbook with 16 GB RAM. After deinstalling / reinstalling all Arturia software (Keylab 49 mk3 bundle and Midi Control Center) several times, I still can’t get Analog Lab mode working consistently with the Keylab mk3 controller. The controller works as far as navigating between tracks and playing an instantiated Arturia plugin, but no other features, including Analog Lab mode, or even basic parameter mapping (e.g. to Push2) functions properly. My latest annoyance is that no matter how many times I reinstall Midi Control Center, it crashes. I have the newest version installed. All of which only reinforces my judgment that Arturia software–particularly the Vst3 plugins–is just not stable on a Windows machine. I love the look and feel of the Keylab mk3 and think that the standalone and Analog Lab mode performance is wonderful–when it works. It’s just not at all reliable in my experience. If you or anyone here has any advice–save repeating the previously posted “fixes”–I’d be interested to hear it. Otherwise, my Keylab mk3 is about to be returned to Sweetwater…
I received my KL3 61 today and ran in the same issues (Live 12.b14).
With the Midi settings as shown in the screenshot, the first Arturia VST loaded is working as expected, all other can be controlled by the KL3, but the display only shows the first VST and no parameter values of any knob or slider are displayed when I touch them.
Quite disappointing that a product at this price is so buggy, especially concerning the bug is related to one of its most prominent features.
After reading all comments of this thread, it seems to be a problem that can easily be reproduced on any Live 11 or 12 system simply by loading more than one Arturia VST.
Hard to imagine, that they (Arturia) didn’t test this.
I don’t use Ableton Live. But should’nt the control surface setup section also contain a Keyboard midi setup beside the DAW setup? Not just in the ports section.
I think the Keyboard Midi setup only shall be connected as input device.
I just made some additional tests and found out that as long as you are using the same plugin (like Analog Lab or Pigments) on all tracks, everything works fine and you can have a number of tracks with (the same) Arturia plugin.
Any additional different plugin will not work correctly in ‘Arturia-Mode’.
Not sure why, but the manual says to just use the DAW setup.
Tried with MIDI anyways, but that doesn’t change the issue but seems to cause some other weird behavior, so I swtched back to the above.
In the video, he also uses just one single plugin at a time. That should work without any problems with the correct Midi-settings (see sceenshots in my other posting).
Same issue here. 2 or more AL’s in ABELTON will not switch focus and reflect in KL3.
Update Actually I just discovered that if you have 2+ AL’s initialized in DAW and track select between them, you simply have to hit the main encoder and it will bring up the preset you were working on the KL3 screen.
Hey Stefan, Could you confirm your operating system? I’m running Windows 11. From what I am gathering from other users, Arturia’s VST3 instruments and integrations via Analog Lab Mode on Keylab MK3 work more completely and reliably on a Mac. although the standalone and VST3 instruments sound great, I’m still stuck with limited remote control–Analog Lab Mode doesn’t work reliably–at all really–with the midi settings set to DAW in Live 12 Suite…
I’m still debating whether to hold out for a future upgrade that will hopefully resolve these issues, or just return the Keylab MK3.
Hey Bill,
yes, I am running Ableton 12.1 Beta on Windows 11.
And - Arturia is aware, that there is a problem with the window driver.
Here’s the response I got from the support team to my corresponding ticket:
The KeyLab mk3 Windows driver, are based on the Windows driver and won’t allow certain things, that are:
Combining VST2 and VST3 instances in the same session, screen integration will work only on one format (the first inserted)
Combining different instruments in the same session, only the first one have integration. For example you can have 3 Analog Lab VST3 in the same session and the screen integration will work, but you won’t be able to have the integration on a inserted Mini V4 after Analog Lab because it’s already taken by Analog Lab.
→ These limitation are known on our side. I have it logged to developers that are aware of that. I’m pushing for this to be fixed, but I’m not sure it is possible and if possible when it will happen.
So I hope they will get this sorted out soon.
But - even if a solution for this would not be possible on Windows for whatever reason (what I can not imagine), I’d never return my KL3.
I am really happy with the device and missing out on the visuals on the screen would be a shame but I’d still be able to control other VSTs via the macros in DAW mode, which is a workaround I could live with.
UPDATE: I think I found what the issue is. I tried opening one of the Arturia plugins (Pigments in this case) outside of Ableton, and it still did not show up on the Keylab’s screen, and thus could not control the VST neither on standalone mode from the keyboard.
However, I brought up the Preferences and noticed that Keylab xx mk3 MIDI and DAW, under MIDI settings, where turned off. I switched them on and the device showed up on the keyboard’s display and I could control it with the knobs and faders just fine.
After that I closed the standalone Pigments, re-opened Ableton and opened Pigments in there. This time around it worked immediately.
Had to do the same with all Arturia Plugins, opening them one by one in standalone mode, enabling the MIDI Settings for the mk3, closing and re-opening in Ableton.
Leaving this here for whoever comes across this issue. And btw my Ableton MIDI settings are as follows -
Opening more than one arturia vst in different tracks works as well.
It is so strange that this happened, but I think this is coming from Arturia’s side. I even tried Ableton 11 and had the same exact issue and outcome. Anyway, hope this solution works for whoever comes across this problem.
That’s what I thought too, but it seems that changing the settings in the standalone somehow triggered something when opened in a DAW… at least on my system.
You’re completely right when you say “The problem seems to appear when any output in the MIDI settings is chosen/checked.”
I really hope it will be fixed soon because we cannot control Arturia plugins and receive the Ableton clock for the internal arpegiator at the same time. Quite frustrating…
Just got the keylab mk3 today. Wow how ridiculous is that. Would not have purchased if I had known using two different arturia plugins breaks their integration and you can only use the arturia mode for one! What a misleading feature. Hey we developed this keyboard where one of the main selling points to be able to work with our plugins inside your daw only catch is you cant use more than one instance in your session. This info was conveniently left out of their marketing since it apparently is a known issue to their developers. What a scam.
I just bought the new version of Ableton (12.2). Seems like the integration mostly works except the display screen on the Keylab mk3 does not seem to recognize the touch encoders until you move them. IE You cannot see what you are about to change until you change it.
