Reason Remote Mapping Tutorial

A walkthrough on how to remote map your controller to new Rack Extensions in Propellerheads Reason

[@bobbryce8674]

Hi Fretless: This was inspirational, so thank you for that. Since the date that you published this piece of work, Reason has opened up the model to VST instruments and I was keen to work out how to remote map these in Reason for my M-Audio Oxygen 25 keyboard. Your 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 was that there was a Oxygen 25 remotemap file in the expected location as provided during the Reason installation, however as explained in your video, while the instruments, effects and utilities that form part of the main Reason software were present, there was no in-built support for remote mapping of any Rack Extensions or VST instruments (after all there must be a huge number available on the market). For anyone that wants to follow in my footsteps, the process in the video is still good, but getting at the data required for the new instrument/effects entries 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. NOTES: 1. The Propellerheads Authoriser is no longer a source for the company and instrument names, since VST devices are clearly not Rack Extensions as defined by Propellerheads. For these purposes I found that a viable solution was to get this 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\\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 will not even see the 'AppData' folder. In case anyone got lost in that description (it is a bit wordy), then I've included a working example for the SERUM Synth from Xfer Records. This mapping gives me automatic control across all patches for the key parameters of both the A and B Oscillators, 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 Remember it's 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). Good luck.

[@els1f]

You're a bad muhfucka man! 🙌🤣 Thank you for this!

[@lpinnch]

Thank you for this! i use Reason myself and there is not that many video tutorials covering this subject. Mapping your MIDI cont. to the Devices can be really rewarding. Just got a Panorama P1 and there is some RE's that i am hoping to successfully map. Thanks again for this video i am sure i am not alone with the interest on Remote mapping In Reason.

[@erichkriebel]

This was immensely helpful, thank you! I used this technique to map my Minilab mk2 controller to Analog Lab 4 VST plugin with Reason 10. Something that should have been working out of the box, but you know how it goes...

[@TheFesta01]

Really struggling to hear what your saying mate. Your background music is too loud.

[@aleccovey7731]

Thanks for the tutorial, very informative and very useful!

[@BasilBoatsMusic]

Thanks for the wonderful video! Please make a video on mapping the ssl mixer!

[@dreamgoodmusic]

Great tutorial. Thank you for sharing this info. Do you know if this method works for 'scale' mapping or how its done?

[@dontmakeaself2418]

The propellerhead forums are now closed. is there anywhere else I can get those mapping templates?

[@weststarr2046]

Awesome...this is very wellcome!

[@seemsas]

Well done! Did you ever get the scale option to work? Sometimes, I would like to limit the value range of the BCR-2000 rotaries but I never got it.

[@stewartrobson7753]

This is very interesting and I'm still as confused as ever unfortunately - I have Reason 10, Windows 10 and as I'm looking at the file you are editing, I see in the device info listed, a lot of parameters are mapped to knob 1 for example, so that would seem that as long as you are mapping knob 1 to a different instrument, that you should be able to do that. That is not the way it is working for me, I get conflict messages all the time if I try and map a knob to more than one device...[I never map said knob to the same device more than once. I just can't see what I'm doing so differently.

[@SjN7HETIK]

same problem here and i really cant understand why Propellerhead (usually simple and friendly) is at version 10 but still not EASY AND CLEAR how the f***k assign the same kb knob to different knobs of other instruments without the 'conflict' message. Further, every time a create an instance of a instrument previously mapped, it is NOT ALREADY MAPPED! EVERY time a open a new device it needs to be REMAPPED. WTF stupid Propellerhead is it really that hard to make a sort of 'mapping template?' In that way i have to set the mapping JUST ONE TIME for every Reason istruments and... That's it! u ok for years. Never again wasting time on mapping ALWAYS THE SAME THING!... Simply i want to control ONLY the selected (in focus) instrument in that moment and obviously without modify other instrument's knobs just because are sharing the same knob. But only one is selected!, as the simplest logic suggests...

[@rodrigonoales]

Great tutorial, thanks. I have an MPK61, I've already set all main controllers of the MPK to work great with the SSL mixer (it's my main interest), the problem I find is that If I lock the MPK to the SSL I will control all faders (1-8) by default and I would like to control the single track in the mixer I focus on. I can't find a way to do that unless I manually click on "Edit Automation" on the channel, then it works ... but it's a pain... I would like to change the focus channel and control that only channel strip. Do you know if it's possible to achieve that ? Thanks

[@fretlessfingers7550]

Yes and no. You should have some controls when doing audio channels as they have there own mix channel auto produce a control track. As for instruments you would need to create a track for them to do what you want but I cannot recall if there is mapping setup for it. I would suggest if your looking for proper control of the SSL you get yourself a fader centric controller like the BCF2000 (what I have) or something better like the Mackie universal control.

[@rodrigonoales]

Thanks I will, just want to make sure I wasn't miss some trick that could do the work. Thanks again for your answer

[@TheCabinneighbors]

will the same work to map 3rd party vst in reason?

[@TheOblivionMemeGuy]

How can you map the controller to the ssl console? Im using an X Touch as a mackie control device and nothing will move the faders in the ssl, unless of course I manually assign it. But then of course I don't have any banks, and I lose the preset's functions.

[@daysaway3360]

Have you gotten an answer for this? I'm planning on getting an X Touch but I want to figure this out before I get one

[@taylordguitar]

hi i have a problem with overide mapping. when i edit overide to put sounds from the redrum into my mpk pads for some reason the new edits i have made will not record in the sequencer. do you know what could be wrong?

[@eeecchhoo]

Hi. Great tutorial! Can you map self made instruments that been made using combinator or is it just the combinator itself you can map? It would be nice to have different maps for different combinators, depending on what you put in it.. Is there any way to do this? Any one?

[@eeecchhoo]

Sure you can override, but it's just not the same.

[@visheshl]

How to change keyboard control group ?

[@farfymcdoogle3461]

OK. What about for PC?

[@aleccovey7731]

It would be the same process, only instead of Finder, you would use My Computer>Your Reason Destination. You would have to know where that is of course. For my setup, my Reason docs are saved in a folder on my desktop so I would do Desktop > Reason 8 > and so on.

[@aleccovey7731]

Also on a propellerhead blog: www.propellerheads.se/blog/control-remote

[@fretlessfingers7550]

Farfy McDoogle Sorry for the very late reply. Checkout this video for PC users kzbin.info/www/bejne/b4nPh5akn8yLiNk

[@McC4rthy]

Why would you put music in a video like this? Are we supposed to hear what you say?

[@johnsexton8082]

Any objection to sharing this video on www.reasonremoter.uk? Please get in touch and let us know.

[@monsieur_zy]

The music is too loud.

[@gkillmaster]

Super helpful. Thanks so much! Do you need to be exact on the lines that start with "//"? Or are the lines that begin with "Scope" the only important ones to get exactly right? I was thinking the script doesn't do anything with lines that start with "//"