Propellerhead Reason - 3.0 - Control Surface Details Uživatelská příručka stáhnout pdf (Strana 22)

Advanced: Creating your

own remote maps

If you have a control surface for which there is no native support in Reason, it's possi-

ble to create remote support for this yourself. It’s a bit complicated, but you don’t

need any programming skills.

! Note: It is only possible to create support for standard MIDI control sur-

faces with one-way communication - support for advanced devices with

two-way communication (LEDs, motor faders, signal meters or dynamic

displays) cannot be added by a user.

How Remote works

For Reason to support a control surface, it needs two files:

D The midicodec file lists all controls on the control surface (knobs, sliders,

keyboard etc.), gives them names and defines which MIDI message cor-

responds to which control.

Basically, the midicodec file tells Reason that "if MIDI message xxx is received, this

means that control yyy is being used".

D The remotemap file connects (maps) each control to a parameter or func-

tion in Reason.

This is done separately for the different Reason devices.

This means that if your control surface is connected to a Subtractor device in Reason,

the remotemap may tell Reason that "turning Knob 1 should change the filter fre-

quency parameter". When the target is a Mixer device instead, the remotemap may

tell Reason that "turning Knob 1 should change the level fader for channel 1".

So, to create support for a control surface in Reason, you need to write a midicodec

file and a remotemap file for it.

What you need

To create a .midicodec file and a .remotemap file, you need the following:

•A text editor application. Its convenient if the text editor has functions for showing

or searching for line numbers - this makes troubleshooting a remotemap easier.

Apart from that, just make sure the application can open and save unformatted

plain text files.

• The documentation for the control surface can be useful.

•A MIDI monitor application can also be very useful - this allows you to check what

MIDI messages are sent out by the different controls on the control surface.

There are lots of MIDI monitor applications available for download or purchase on

the web.

•A clear head.

How to create a .midicodec file

1. Set up the control surface the way you want to use it with Reason.

For example, you may want to select a certain program or template that you will al-

ways use with Reason. You should not change the settings in this program/tem-

plate after you have created the .midicodec file.

2. Make a note of which MIDI message is sent by each control on the control

surface.

This is where a MIDI monitor application comes in handy.

3. In the Reason program folder, open the folder "Template Documents" and

then open the subfolder "Remote Files".

4. Open the file "Template.midicodec" in a text editor.

This document starts with the following lines:

Universal MIDI Codec Control Surface Definition File

File Format Version 1.0.0

Control Surface Manufacturer <manufacturer name>

Control Surface Model <model name>

5. Replace <manufacturer name> with the brand name of the control surface

and <model name> with the name of this control surface model.

6. Below the Item Header line, list all the control surface items (the controls on

the control surface).

Here are some examples of how different items are defined:

Item <name of the control> value 0 127

The above could be a slider or a knob. You replace <name of the control> with a

name of your choice – e.g. Knob 1 or Fader A. All control surface items must have dif-

ferent names.

Item <name of the control> button 0 1

The above is how a button is defined. You replace <name of the control> with a name

of your choice – e.g. Button 1.

Item keyboard keyboard 0 127

The above is how you define a keyboard, if your control surface has one. You could

name the keyboard (in the Name column, as with the other controls), but typically you

just call it keyboard as above.

Item pitch bend value 0 16383

If your control surface has a pitch bend control, it is typically defined with a range from

0 to 16383 as above. Again, you could give the control another name than pitch bend

if you like.

When you have listed all control surface items as described above, you need to define

which MIDI message corresponds to each control surface item. This is how Remote

knows that you are using a certain knob, slider or button on your control surface – by

receiving a MIDI message from the control surface and comparing it to this list. These

definitions are added under the Map Header line.

1 2 ... 17 18 19 20 21 22 23 24 25 26

Komentáře k této Příručce

Žádné komentáře

Propellerhead Reason - 3.0 - Control Surface Details Uživatelská příručka Strana 22

Komentáře k této Příručce