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.
