For some reason, the pads only work correctly when explicitly set to channel 10. click on the "ALL" next to the midi dropdown and select channel 10. Click on the "gear" icon and set the input port to the one that MiniLab is listening on (aka input port 0)ħ. VST3 has some rendering issues, so just pick the VST2 (32 bit or 64 bit is up to you, this works on both)Ħ. Load Bank #2 with shift-pad2 (pad 2 should stay solid if you hold down shift button again)ĥ. Under midi settings, tell Arturia MINILAB to listen on a specific port (I chose port 0).Ĥ. Second, load the "analog lab mapping" file and send it to mem #2.ģ. First, load the "absolute mapping" file and send it to mem #1. If you care about your current settings, be sure to make backup copies. Attached are the map files I have that finally work. I spent a ton of time screwing around with various programming settings in MMCC. I updated everything to the latest version (Analog Lab 1.0.5, MMCC 1.1, Firmware 2.1.0.2)Ģ. If you want to actually do any programming of the controller beyond updating the firmware I strongly recommend contacting Arturia support and asking for access to their beta MCC.ġ. UPDATE: Arturia gave me beta access their new MIDI Control Center that works with multiple Arturia really is a night-and-day difference.tons better than the MiniLab MCC. Since I've spent two days on this, I hope I can save others some time.the MiniLab controller is pretty awesome and Analog Lab sounds amazing. However, it's a bit of a pain to get it to play nicely with Analog Lab VST.it *does* work, it just isn't as convenient as it ought to be and setting up the VST isn't all that intuitive. The MiniLab seems to work great in FL as a generic controller.
0 Comments
Leave a Reply. |