Hi,
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.
Regards,
Zbig
Hi @SpaceFaringShrimp welcome to our Sound Explorers community!
Sorry to read this, in order to help you better please log in to your account to contact our support team that will help you to fix this situation.
Best 
Any update or solution on this? I’m having the exact same issue in Reason 13 with Analog Lab mode with my KeyLab88 Mk2.
…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.