I’m on MacBook Air M2 and using Reason 12.6.2.d48. MiniLab 3 seems to integrate with Reason properly: I can switch tracks and presets, see their names on the OLED screen, manipulate Reason instruments’ parameters with encoders and faders, etc. However, when trying to operate Analog Lab Intro instrument in VST3 mode, when I switch my MiniLab to “Arturia” mode (Shift-Prog), all that happens is the preset name gets displayed on the screen but no other functionality works: I cannot browse presets, any encoder and fader actions have no effect, etc. Switching presets in the plugin using mouse causes the displayed name to update but moving other controls (knobs, faders) with a mouse doesn’t result in anything being displayed on the controller.
I have tried both the Reason’s built-in integration scripts and the Arturia-provided ones without any difference in behavior.
…More specifically: I can manually assign any of the KeyLab88 Mk2’s knobs and faders to anything in Reason 13 (including 3rd-party plugin parameters like what is in Analog Lab) when the KeyLab Mk2 is in DAW mode with LIVE as the specified DAW. However when I switch the KeyLab88 to Analog Lab mode then it’s like Reason doesn’t see any of the MIDI being sent from the knob/faders. I’ve tried to create two separate MIDI controller paths for Reason in Reason’s preferences but so far that isn’t working. It’s like Reason is somehow filtering out the KeyLab’s all MIDI or control data when in Analog Lab mode. None of the Arturia synths respond to the KeyLab knobs/faders when in Analog Lab mode when using Reason.
Sadly, the problem exists since years, and Arturia still hasn’t fixed it although users have been pointing it out long ago.
Reason talks to MIDI controllers via scripts where parameters are named Fader1, Knob1, etc. But each preset in Analog Lab has a specific name for each parameter : Cutoff, Brightness, etc. Therefore, if you move knob #1 on your controller and it’s assigned to “Cutoff” in Analog Lab, Reason sends values from control “Knob1” although Analog Lab awaits (and will respond to) values from control “Cutoff”…
Arturia should really talk to the Reason Studios team and fix this issue…
Somewhat similar to Bitwig. In DAW mode, no problem. But in AL mode, the KeyLab can’t control the plugin. I had even read somewhere that the KeyLab would shift automatically from DAW to AL and vice-versa when you select a track with the AL plugin and then select a different track without it. But none of this works.
_Need help ?
When you can't find the answer online or in the product manual, the Technical Support Team is here!.
_Stay tuned
Follow us for the hottest sounds, fresh content, exclusive offers and Arturia news as it happens.
