I upgraded Analog Lab Pro to the latest version which contains several bug fixes and KeyLab MK3 integration. I currently have KeyLab MKII midi controller. It seems the MK3 integration is causing problems with MKII integration, because Analog Lab crashes if I use MKII to browse categories, browse presets, etc.
I downgraded Analog Lab and Pigments to the previous versions and now everything is working fine.
Anyone else with this issue?
Alex.
HI @aprado and welcome to the Sound Explorers Forum!!
Sorry to hear about your issue, did you check the Audio/Midi settings to see if your controller was selected? Daft question possibly, but have to ask.
You can do this by selecting the ‘hamburger’ icon at the top left hand of the GUI on the left side of the ANALOG LAB logo…
As in the pic below…
Then select Audio and Midi settings and you’ll be presented with the following, your midi ports are likekly to be different to mine, but you should see your controller listed in the circled box, so just check the box and close that window.
HTH!
Ps,
Please make sure to subscribe to our Newsletter to be the first to know about the latest from Arturia.
After I did the update, I found I had to change all Fader Modes of all synths from “Scale ”to “none”. After the update, they were all set to “Scale”.
On my set up, having the Fader Modes set to “Scale” prevented the synth from responding purposely to mapped CC events or gave unpredictable results.
I also had to reload and set all of my default MIDI configs.
I have an issue with Analog Pro where when I change patches from my Keylab 61 MKII it glitches and the patch starts flipping controllers around and seemingly reloading the patch. This renders it unplayable. This only happens in my DAW (Studio One). Standalone seems to work fine. This also started right after the latest update with the release of the MK3. Everything works fine if I use the patches via Komplete Kontrol so this sounds like an Analog Lab / MKII integration issue. I have submitted a request to support and I am waiting on a response. @aprado I will let you know if I get a response. I hope they work it out soon.
I’m having the same issue here, also using studio one.
Hi matjones.
Thanks for your response. Yes, KeyLab MK II is selected as MIDI Controller. Actually everything is working fine, but in some point of browsing and testing sounds in Analog Lab using the controller, Analog Lab crashes. It is the same with Pigments. After downgrading Pigments and Analog Lab to previous versions, everything is working fine.
Alex.
Thanks Promidi. I’ll check this, maybe I could find a solution changing some configurations like you.
Hi Jaandlu.
I sent a support request as well. I’ll let you know if I receive a response. It seems our issues are closely related.
Alex.
So, I did get a response but it did not actually address the issue in any way. He just gave me the directions for setting up the MKII in Studio One. I sent a lengthy explanation and video of what happens when Analog Lab Pro glitches. All of this was ignored and he just tried to tell me how to set up my keyboard in Studio One. I will update you if I get any useful information. So currently, the only way to get Analog Lab Pro to integrate with the MKII is by using Komplete Kontrol and you are limited to 8 of your controls at a time. Of course, you can set it up to work pretty well, but I would rather work the way it was set up to work and not have a third party plugin in controlling everything.
Hey @matjones,
Have you guys look into this bug any more? Are there any work arounds we can employ? I would love to have my setup working as it did before you updated things for the MKIII.
HI @Jaandlu
Myself and the other ‘External Moderators’ don’t actually work for Arturia, so we have limited access to information, so i cannot answer as i do not know. It has been passed on to the relevant people though.
HTH!
Hi guys.
I received a response from support with a solution that worked for me. These are the steps:
Make sure to close your DAW and the instrument’s standalone app.
Launch the Arturia Software Center.
Open the concerned Product detail panel.
Expand the bottom-right drop-down list and click on Clean Prefs.
The preferences should now be reset.
I did this for all my Arturia Prodcuts and it worked.
Hope this helps.
Alex.
I’ve had Jaandlu’s symptoms in Studio One 6 using VST 3 Analog Lab on my Keylab 88 mkii (screen flicker, partial or no browsing control from Keylab, key press results in no more than a quick glitch of preset’s sound), tried the Clean Prefs setting for all my Arturia plug-ins, and nothing improved. The AudioUnit version appears to work (and no problems inside Logic Pro or stand-alone). Still need to test with Ableton Live Lite and Reason 12.7. After 3 evenings working on this I’m very frustrated.
I tried this and it did not work. 
I verified the Keylab 88 MKii will control Analog Lab VST in Live Lite, but not in Reason 12. However, while running Reason, the Keylab’s screen doesn’t flicker, lock up or disrupt key playing of presets in Analog Lab.
my problem is that i used to sequence 2 or more instances of analog lab v with keystep pro and now can only sequence 1 instance at a time . just had enough of arturia tbh. And keystep pro is so buggy. I wish ive never bought one. Emailed support and no answer at all.
After looking at Studio One’s Midi Monitor, tonight I found the Keylab 88 MKii sending a constant stream of Aftertouch messages, mostly #1, but also #33 and #7, all without touching the keyboard or any other controls. I’m suspecting that isn’t normal. I don’t see the constant stream when using the AU plug-in version. Later in the evening the constant stream went away on the VST version, but the symptoms of no sound and screen glitching continued.
I tried my Faderport 8’s Parameter Link dial to control each of Analog Lab’s VST dial parameters by clicking them with the mouse, and the dial tried to change the values, but was being jumbled, interrupted on-screen, jumping back to the default dial setting.
I also found my Faderport 8 is sending a slower stream (one per second) of Polypressure messages, but that is something it does with the working AU plug-in, so I guess it’s normal for the Faderport 8. (I’ve never really looked at MIDI message output in detail before).
Before I gave up for the night, the Keylab’s screen stayed solid in Analog Lab mode, but couldn’t switch to DAW mode.
I’m tired.
I finally got a solution from Arturia support that works.
"I apologize for the inconvenience and for the delayed response.
We have identified some issues with the latest version of Analog Lab when used with Studio One, and our team is actively working on a fix.
In the meantime, the only solution is to revert to the previous version. You can find it here:
https://dl.arturia.net/products/analoglab-v/soft/Analog_Lab_V__5_10_2_4741.zip
Let me know if it helps.
Kind regards,
Andrés - Arturia Support"
So, if you are still experiencing issues, try this fix. But it is also nice to know they too have seen the glitch and are working on it.
I saw a new update to Analog Lab, thinking maybe it’s got the fix, installed it, and the VST completely crashed Studio One 6. Relaunched and same symptoms as before.
Follow us for the hottest sounds, fresh content, exclusive offers and Arturia news as it happens.
