Remote is a protocol for handling communication between control surfaces (MIDI keyboards, remote control devices, etc.) and software applications (e.g. Reason). It handles everything from delivering MIDI note data from a keyboard to the application to using knobs, faders and buttons on a control surface for tweaking synth parameters in the application, controlling transport, etc. Remote also supports two-way communication, in order to make use of motor faders, dynamic displays and LED indicators.
The Remote protocol was introduced with Reason 3.0, which provides Remote support for a large number of control surfaces. Support for new control surfaces can be added at any time, in many cases by the control surface manufacturers or even by users.
Tighter integration between software and hardware
While software audio applications can be immensely powerful, there’s no doubt that physical hands-on control of parameters, transport and other functions is superior to clicking and dragging with a mouse. One of the goals of Remote is to provide a very tight integration between the control surface and the application — the control surface should feel like a natural part of the application rather than a separate, external device.
Ease of use
Historically, control surfaces have required quite complicated setup procedures — the user needed to program the control surface so that the knobs and faders sent the correct MIDI messages, switch between different templates on a control surface or set up manually which parameters should be controlled in the application.
If you use a Remote-supported control surface with Reason, all you need to do is connect the control surface and set it up once and for all, typically by selecting a single factory preset — no programming or understanding of MIDI messages is required. In many cases, the Remote system can even identify the control surface and set things up automatically.
After that, the control surface is ready for use. All knobs and sliders will automatically and dynamically be mapped to sensible parameters in Reason; the user never needs to switch presets or re-program controls on the surface.
As described above, all control surface items will automatically be mapped to control sensible parameters in the application. However, you can also choose to override these mappings for individual parameters, to tailor your setup for the project or situation. For example, you could have one slider always control the master level of the main mixer, assign some keys to transport control, have the foot pedal step through patch changes, and so on.
Use several control surfaces
With Remote, you can have any number of control surfaces connected. You can choose whether they should control the same device or different devices.
Make use of advanced control surface features
Remote supports two-way communication, for motor faders, dynamic displays, indicators, etc. For example, a control surface with dynamic displays can show which devices and parameters are controlled at the moment, along with the parameter values. This makes the integration between the hardware and the software even tighter — with the right control surface you can play a live gig with Reason without needing to look at the computer screen at all!
If there’s a Remote map for your control surface installed (either by you or built into Reason), you can use the “Auto-Detect” feature in Reason’s preference to automatically set up your control surface. See the matrix below for the full list of control surfaces.
Please note that even if your control surface isn’t listed here, or if it doesn’t have a Remote map, you can still set it up with Reason. Simply add it as a generic control surface in the Reason preferences by clicking Add and selecting <Other> as the manufacturer.
The following control surfaces are supported by Remote in Reason. If a control surface is not listed here, we recommend contacting the manufacturer asking about Reason Remote support.
Please note that if your control surface is not listed here, you can still set it up as a generic controller or keyboard in Reason’s preferences.
|Manufacturer||Model||Note||Auto-detect||Display/LED feedback||Motor fader support|
|Kenton||Control Freak Live|
|Control Freadk SE|
|nanoKEY / nanoKEY 2||x|
|nanoKONTROL / nanoKONTROL 2||x|
|nanoPAD / nanoPAD 2||x|
|TRITON taktile 25/49||x|
|FBV Express MkII||x|
|FBV Shortboard MkII||x|
|Mobile Keys 25/49||x|
|Axiom Pro 25/49/61||x||x|
|Oxygen 49/61 3rd Generation||x||x|
|Native Instruments||Audio Kontrol 1|
|Nektar||Panorama series||Remote support files included with hardware||x||x||x|
|Impact series||Remote support files included with hardware||x||x|
|Novation Automap Control||Supports all Novation Automap control surfaces||x||if applicable|
|Novation Automap Keyboard||Supports all Novation Automap keyboards||x||if applicable|
|Wave Idea||Bitstream 3X||Download the Remote files here||x|
All product names are registered trademarks, owned respectively by the manufacturing companies.
If you are a control surface manufacturer and would like to add your Remote-compatible control surface or keyboard to the list above, please contact us.
Propellerhead Software will issue licenses to companies in the audio or music industry or individuals interested in creating codecs for controllers.
There are no costs involved. Propellerhead Software will administer the authorization, copyrights, logos and trademarks. The company will also provide the licensee with technical support, free of charge, if you are a company.
Simply visit the Propellerhead developer pages, where you will find detailed information and forms for applying for licenses.