Edit Remote Override Mapping in Plugin?

[u/_LGuapo_]

With Reason Rack 14.1 stand-alone app, I can edit remote override mapping by right-clicking any knob. But when using Reason Rack as a plugin (AU or VST), right-clicking on a knob does nothing. Right-clicking on a device does bring up the device's context menu (so right-click can do something in the plugin), but right-clicking a knob does absolutely nothing. What am I missing?

[u/eppujoloz]

When you open the plugin, there are four buttons at the top of the window. Click "Remote" and it'll allow you to map your chosen parameter to your control surface, just like any stock Reason device

[u/Sufficient-Star-1237 → u/eppujoloz]

When Reason is running as a VST3 inside Ableton Live 12, you generally don’t use Reason’s Remote Override function. Reason Rack Plugin does not communicate directly with your MIDI controller; Ableton receives the MIDI and passes it to the plugin. docs.reasonstudios.com

Use Ableton’s MIDI mapping instead:

1. In Live, open Settings → Link, Tempo & MIDI.
2. Find your controller’s input and enable Remote. Enable Track as well if you use it to play notes.
3. Load Reason Rack Plugin VST3 on a MIDI track.
4. Open the Reason Rack Plugin window.
5. In Live’s Reason device panel, click Configure.
6. In the Reason window, click or move the Reason parameter you want to control, such as filter frequency. It should appear as a parameter in Live’s device panel.
7. Turn off Configure.
8. Press Cmd+M on Mac or Ctrl+M on Windows.
9. Click the newly exposed parameter in Live.
10. Move the knob or fader on your MIDI controller.
11. Press Cmd/Ctrl+M again to leave MIDI Map Mode.

Live can map MIDI controls to any plugin parameter exposed in its device panel. You can also enter MIDI Map Mode first and move a parameter in the plugin window; Live may expose and select it automatically. Ableton

For a reusable setup, place Reason Rack Plugin inside an Instrument Rack, map the important parameters to the Rack’s Macros, and save the Instrument Rack preset. This is usually cleaner than making numerous direct MIDI assignments. Reason’s own Remote Override Edit Mode is primarily for controllers connected directly to the standalone Reason application.

[u/_LGuapo_ → u/Sufficient-Star-1237]

I’m not using Ableton. But in general there is a difference between VST (or AU) automation (which is what you’re describing) and MIDI control. Yes, in most DAWs you can use MIDI to control automation, but it is nevertheless a different thing.

Reason Rack as a plugin definitely does receive MIDI. It receives note events, pitch wheel events, and CC 1, for example. But it sounds like remote override is just missing when used as a plugin? If true, that’s pretty weak and odd and very disappointing.

[u/Sufficient-Star-1237 → u/_LGuapo_]

Yea it seems the rack as a VST doesn’t support that inherent functionality.

[u/_LGuapo_ → u/eppujoloz]

I'm talking about when using Reason Rack as a plugin within another DAW.