Propellerhead Reason - 3.0 - Control Surface Details Guía de usuario descargar pdf (Pagina 24)

10.Define the keyboard, if your control surface has one.

Pressing a key on a keyboard sends out a MIDI message like this:

90 20 40

This means that a key is played, on MIDI channel 1, with note number 32 (20 in hex)

and velocity 64 (40 in hex).

Releasing the same key may either send out (depending on the keyboard model):

90 20 00

80 20 30

The first case is most common - it means that the keyboard sends a note-on message

with velocity 0 when you release the key.

The second case means that the keyboard sends a dedicated note-off message. The

last byte in the second example is the release velocity (how fast you release the key -

in this example the release velocity is 30hex). Only some keyboards send out a vari-

able release velocity - this is ignored by Reason anyway.

You could check your MIDI monitor application to see which type of note-off message

your keyboard sends, or you could simply add the following to the .midicodec file:

Map 9? xx 00 Keyboard 0 x 64

Map 8? xx yy Keyboard 0 x y

Map 9? xx yy Keyboard 1 x y

This covers all types of note on/off messages, on all MIDI channels.

11.When you have defined all controls, save the file as "xxx.midicodec" where

"xxx" is the name of the control surface.

Midicodec files that you have created yourself should be saved in the following folder:

Mac OS X:

<your home folder>:Library:Application Support:Propellerhead Software:Remote:Co-

decs:MIDI Codecs

Windows:

C:\Documents and Settings\<username>\Application Data\Propellerhead Soft-

ware\Remote\Codecs\MIDI Codecs

D Initially, the Remote folder (in the path above) will be empty - you need

to create a folder called “Codecs” and then a subfolder called “MIDI Co-

decs”.

D A new midicodec file won't be recognized by Reason until you restart the

program, but you need a mapping file anyway, so read on...

How to create a .remotemap file

1. In the Reason/Template Documents/Remote Files folder, open the file

"Template.remotemap" in a text editor.

This document starts with the following lines:

Propellerhead Remote Mapping File

File Format Version 1.0.0

Control Surface Manufacturer <manufacturer name>

Control Surface Model <model name>

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

and <model name> with the name of this control surface model, as in the

.midicodec file.

The rest of this template document lists a number of scopes, one for each Reason de-

vice, one for the Master Keyboard and one for the Reason Document. Under each

scope heading, you define how controls on your control surface should be mapped to

parameters and functions in Reason. A basic mapping looks like this:

Map <control surface item> <remotable item>

<control surface item> is the name of a control on your control surface, as defined in

the .midicodec file. <remotable item> is the name as a parameter or function in Rea-

son.

Note that there are two tabs between <control surface item> and <remotable item>.

3. Tip: It's a good idea to open an existing remotemap file and check how

things are mapped there.

This will help you get the correct names of remotable items in Reason, and give

you hints on how to create a good mapping.

The remotemaps that were installed with Reason can be found in:

Library:Application Support:Propellerhead Software:Remote:Maps (Mac OS X)

C:\Documents and Settings\All Users\Application Data\Propellerhead Software\Re-

mote\Maps (Windows)

4. If your control surface has a keyboard, you need to map the performance

controls under the "Master Keyboard" scope heading.

Reason supports the following performance controls:

Keyboard

Pitch Bend

Mod Wheel

Damper Pedal

Expression

Channel Pressure

Breath

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

Comentarios a estos manuales

Sin comentarios

Propellerhead Reason - 3.0 - Control Surface Details Guía de usuario Pagina 24

Comentarios a estos manuales