Default Remote Mapping for VST instruments/effects

Discuss VST stuff here!
User avatar
Posts: 100
Joined: 14 Apr 2017

Post 11 Aug 2018

Hoping this might be helpful to other users that would like to enhance their workflow and who are using more than just a basic midi controller.

If you have a keyboard or other type of midi controller with a few knobs/buttons, you may have noticed that Propellerheads has already mapped several controls for you - try opening a NNXT for example and you will see that the six rotaries on the panel are mapped to the first six rotaries on your keyboard or controller. This is achieved by use of a 'remotemap' file that came as part of the installation.

However potential problems can arise in any of the following scenarios:-
a) your controller type has not been included by Propellerheads
b) the parameters mapped are not the ones you wanted
c) you might want to map a Rack Extension, or
d) you might want to map a VST instrument or effect (as in my case).

Stand on the shoulders of giants they say, so my first port of call was a video from three years ago produced by Fretless Fingers (see link below).

This video addresses scenarios a, b & c, but does not address d.

Since the date of this video, Propellerheads has opened up Reason to include VST instruments and I was keen to work out how to remote map these in Reason for my M-Audio Oxygen 25 keyboard. This video gave me enough of the groundwork to allow me to do that. I just completed my first mapping which was to add Serum onto Reason - and with only minor problems I managed to complete that!

The good news in my case was that there was already a Oxygen 25 remotemap file in the expected location (as provided during the Reason installation). Had there not been, you might want to consider copying and renaming the file from a similar instrument.
However, while the instruments, effects and utilities that form part of the core Reason product were present, there was no in-built support for remote mapping of any Rack Extensions or VST instruments.

So, assuming that you have now watched the video and are comfortable with the basics......

The process in the video is still good, but getting at the data required for VST instruments or effects requires accessing some different files in different file locations. Note - I can only speak here for Windows 10 users (sorry iOS people) but hopefully those using other OS can figure out their own locations.

1. The Propellerheads Authorizer is no longer a relevant source for the company and instrument names, since VST device licences are not held here. For the purpose of adding VST mappings I found that a viable solution was to get the data required from inside Reason - go to the 'Window' tab and then to 'Manage Plugins'. Use the company name and instrument name that you find here. This data is needed for line 1 of the instrument header for Instrument Name, and for line 2 of the header for Company name.
2. You also need to go to a different location to find the device name (for adding to the end of the 'Scope' line of the instrument header). On my PC, this was found in the folder at 'C:\Users\<YourName>\AppData\Local\Propellerhead Software\Reason'. In that location you should find a 'device' file and possibly a 'browser' file as well - it's the device file name you need. Note that you will need to enable access to hidden system folders, otherwise you may not even see the 'AppData' folder.
3. The VST instrument parameter names are found through using the pop-up tooltips, or if this technique does not work on a particular instrument, you can set up a remote edit and copy the control name from the form that appears.

In case anyone got lost in the above description (it is a bit wordy), I've included a working example for the SERUM Synth from Xfer Records. This mapping gives me default control across all patches for the key parameters that I find most useful (Wavetable position, level of unison, detuning extent of unison and volume for each of the A and B Oscillators, plus the main filter cutoff and the master instrument volume).

//Remote Map template for Instruments Serum_x64
Scope Xfer Records vst.XfsX.Serum_x64_device
// Control Surface Item Key Remotable Item Scale Mode

Map Knob 1 A WTPos
Map Knob 2 A Unison
Map Knob 3 A UniDet
Map Knob 4 A Vol
Map Knob 5 B WTPos
Map Knob 6 B Unison
Map Knob 7 B UniDet
Map Knob 8 B Vol
Map Fader 9 MasterVol
Map Modulation Fil Cutoff

PS The above example is not formatted on this page very well. Remember to use one tab after the 'Map' but two tabs after the control - e.g. 'Knob 1'.
Also, I had a bit of trouble mapping the mod wheel, but I discovered that. at the top of the remote map file, the name of some of the controls is defined, so that Modulation Wheel becomes 'Modulation' (at least in Reason 10.5).

In practice, this has worked very well for me. Putting in place this mapping has significantly reduced the time it takes me to tweak parameters in getting to the sound I need for a particular project because I'm tweaking the knobs on the keyboard rather than continually leaving the keyboard and grabbing for the mouse. It's also helping me in moving from project to project as I'm starting from a better baseline each time, with the parameters most used already mapped in familiar positions on my keyboard.

Hope you found this helpful, and good luck.

User avatar
Posts: 16
Joined: 31 Jan 2015

Post 28 Oct 2019

Hi congratulation for your stuff,
i'm trying to control a VST via a PCR-50 (the remote codec already exists in Reason, it's the PCR-Series...)
i can control combinator and other Reason's instruments without any pb
but i can't manage to control a RE or a VST by modifying the *.remotemap ?
I modified the file "PCR.remotemap" like this :

Code: Select all

Scope	Propellerhead Software	se.propellerheads.Europa
//	Control Surface Item	Key	Remotable Item	Scale	Mode
Map	Knob R1		Master Volume
Map	Knob R2		Master Volume
Map	Knob R3		Master Volume
Map	Knob R4		Master Volume
Map	Knob R5		Master Volume
Map	Knob R6		Master Volume
Map	Knob R7		Master Volume
Map	Knob R8		Master Volume
Map	Slider S1		Master Volume

Scope	Propellerheads	Combinator
//	Control Surface Item	Key	Remotable Item	Scale	Mode
Map	Button B3		Select Previous Patch
Map	Button B4		Select Next Patch

Map	Knob R1		Rotary 1
Map	Knob R2		Rotary 2
Map	Knob R3		Rotary 3
Map	Knob R4		Rotary 4
Map	Knob R5		Button 1
Map	Knob R6		Button 2
Map	Knob R7		Button 3
Map	Knob R8		Button 4
Do i miss something ?
Thanks for your help

Posts: 130
Joined: 28 Sep 2018

Post 29 Oct 2019

If you want to control the vst-device and not the combinator, you have to add an extra section for this vst device. To create this section correctly you need the vendor id and the name of the vst device. You also need the names of the parameters in the vst device you want to control. All these information can be exported from the file menu in Reason. The option is call "Export device remote information" or something like that.

You might want to read through this thread, because not long ago I did that for many of my vst devices. Works very well :-)

viewtopic.php?f=4&t=7514395&p=471047&hi ... te#p471047


Posts: 1
Joined: 18 Apr 2020

Post 09 May 2020


I'm trying to hack a VST effect remote map for the korg nanokontrol2 which is not working :(

The VST manufacturer is Vengeance and I think the VST device is vst.VpCM.VPS philta (CM edition)_x64 but copying in the data from the VST info file here:

Manufacturer Model
Vengeance vst.VpCM.VPS philta (CM edition)_x64
Note: Will match scope definitions for vst.VpCM.VPS philta (CM edition)_x64 or vst.VpCM

The hack I have added to the korg remote map is copied here:

Scope Vengeance vst.VpCM.VPS philta (CM edition)_x64
// Control Surface Item Key Remotable Item Scale Mode
Map Knob 1 LowPass.Freq.
Map Knob 2 HighPass.Freq.


Any idea what I am doing wrong? Am using 1 tab after Map and 2 tab after Control surface item. I did check the app data name which is a bit different: vst.VpCM.VPS philta (CM edition)_x64_device but this doesn't work either when I use it as the effect name.

Loving the forum and would really appreciate any advice.


Posts: 3
Joined: 28 Apr 2020

Post 12 May 2023

Thanks, that was really helpful. I've got an old Novation Launch Control (v1, not XL) box mapped to Reason devices (eg. Subtractor) & VST2 instruments (Serum & others) now.
Has anyone tried using a .remotemap file to control a VST3 instrument yet? I'm getting no joy at all for Serum VST3.
Have just logged a support request with Propellerheads/Reason Studios so hopefully it's still possible with VST3 plugins. In the meantime I can click the Remote button at the top of the plugin window to map a knob temporarily, that still works.

  • Information
  • Who is online

    Users browsing this forum: CommonCrawl [Bot], Google [Bot] and 2 guests