If you simply clicked Next/OK on the installation, the folder paths should be the default ones, so you need to point Ableton to them. So you installed Analog Lab on a Mac or Windows PC?ĭid you see in what path the VSTs (the plug-in. If the Analog Lab name shows up in the left-side Plug-In Devices browser (you have to click the little Plug icon on the left tab list), then you're set. Try on Ableton Live's Options, Preferences, File Folder side-tab and in the Plug-in Sources section, click the "Rescan" button and wait a little bit. I've made a screen capture of this behaviour to try and demonstrate what I'm talking about.First, you can try the quickest easiest way. The weird thing is that the "rogue" knob still acts weird (affecting another unrelated knob on the software) while all the other knobs and faders stopped working, as exoected when disconnecting the midi interface on the software level. I tried disconnecting the interface on Logic's environment, and connecting it to a midi monitor, to see what happens. I contacted Arturia's support, and they kindly guided me through resetting the definitions on the Kelyab and on the plugins.Īt the end of the process, i.e following Arturia's suggestions, I still get one knob not working properly. In Logic however, some of the knobs stopped controlling the corresponding knobs on screen. It's very intuitive and a lot of fun to control the Arturia plugs with the Keylab Essential, and especially the meta-plugin, the Analog Lab.Įverything was working perfect for me with Analog Lab 4, but recently, after Arturia released the new version of the V Collection, with Analog Lab V (5) included, I started experiencing problems.īefore explaining things further, it should be noted that when launching Analog Lab V as a standalone, or either as an AU or a VST inside Ableton Live, everything still works fine. I have Arturia's V Collection and also the Keylab 61 Essential. This one is a bit complicated to explain, but I'll try.
0 kommentar(er)
