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

Which controls to include depends on your control surface (i.e. which control surface

items are defined in the .midicodec file). It could look like this for example:

Scope Propellerheads Master Keyboard

// Control Surface Item Key Remotable Item Scale Mode

Map Keyboard Keyboard

Map Pitch Bend Pitch Bend

Map Modulation Mod Wheel

Map Sustain Pedal Damper Pedal

D Make sure that the names in the Control Surface Item column are exactly

the same as in the .midicodec file, and that the remotable items are cor-

rect.

5. To map controls for a specific Reason device, add map lines under the corre-

sponding Scope heading, like this:

Scope Propellerheads SubTractor Analog Synthesizer

// Control Surface Item Key Remotable Item Scale Mode

Map Knob 1 Filter Freq

Map Knob 2 Filter Res

etc.

6. If your control surface has a keyboard, you can map a specific key to a pa-

rameter or function in Reason, like this:

Map Keyboard C0 Filter2 On/Off

Note that this means that you can't play the Reason device with this key (C0 in this ex-

ample) - pressing it will only control the parameter, not make any sound.

7. If there are lots of parameters on the device and few control surface items,

you can create Keyboard Shortcut Variations.

Check out some of the existing remotemaps to see how this is done.

8. Finally, you can map controls to functions under the Reason Document

scope heading.

This is where you map transport functions, target track selection, Undo, etc.

Here's how this could look:

Scope Propellerheads Reason Document

// Control Surface Item Key Remotable Item Scale Mode

Map Button 1 Stop

Map Button 2 Play

Map Button 3 Record

Map Button 7 Target Previous Track

Map Button 8 Target Next Track

D You don't have to make mappings for every function or every device.

In fact, you can use a remotemap file that only contains the headers (as in the tem-

plate), with the correct manufacturer and model name inserted. Then there will be

no automatic mapping of controls to parameters, but you can still use Remote

Override.

9. When you have made all mappings you want, save the file as "xxx.re-

motemap" where "xxx" is the name of the control surface.

Remotemap files should be saved in the following folder:

Mac OS X:

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

mote:Maps:<manufacturer name>

Windows:

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

ware\Remote\Maps\<manufacturer name>

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

to create a folder called “Maps” and then a subfolder with the name of

the control surface manufacturer (as specified in the midicodec file).

Testing

1. Re-launch Reason.

2. Open the Preferences dialog and go to the Control Surfaces and Keyboards

page.

3. Click the Add button and select the model/manufacturer of the control sur-

face in the Add dialog.

If the control surface doesn't appear on the menus, this means that there is some-

thing wrong with the midicodec file - check that the header is correct!

D If you edit the midicodec file, you need to re-launch Reason for the

changes to take effect.

4. Select the correct MIDI input port and click OK.

5. Now the control surface should be added to the list on the Control Surfaces

and Keyboards page.

6. If there's a red X next to the surface in the list, this means there's something

wrong with the remotemap. Click the X to get an error report - this can often

help you find what's wrong.

If you need to edit the remotemap, you don't have to restart Reason - just save the

changes in the file, and turn the "Use with Reason" checkbox for the control sur-

face off and on again on the Control Surfaces and Keyboards page.

7. When the control surface is shown with a green check mark, this means that

the midicodec and remotemap files are OK.

You can try out the mapping in the program using the standard Remote proce-

dures.

D If you have mapped a control to a parameter in Reason and this doesn't

work (even though the control surface gets a green check mark) this

could be because you have used the wrong name for the remotable item

(or misspelled it).

Check the tool tip for the parameter in Reason - the item in the remotemap file

should have the exact same name as shown in the tool tip.

1 2 ... 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 25

Comentarios a estos manuales