Propellerhead Reason - 4.0 Manual de operaciones descargar pdf (Pagina 68)

THE SEQUENCER

About performance controller automation on multiple lanes

If you have several active (unmuted) note clips with performance controller automa-

tion on different lanes of the same track, and these note clips overlap position-wise,

the following rule applies:

D Performance controllers in the top lane clip overrides any performance

controllers of the same type in other overlapping clips on lanes below.

The clip on the upper lane has pitch bend down automation, and the clip on the lower lane has

pitch bend up automation and note events. The pitch bend affecting the notes will follow the

automation curve of the upper clip for its duration. As soon as the upper clip ends, the notes will be

affected by the pitch bend up automation in the lower lane.

About the “Automation As Performance Control” option

You can also chose to record any type of parameter automation as performance pa-

rameter automation, i.e. the automation will be contained in note clips on a note lane

as opposed to being recorded on separate automation lanes.

D This is activated by the “Automation As Perf Ctrl” button below the

transport controls on the transport panel.

When this is activated, any parameter you tweak on the device connected to the

track while recording will be recorded as performance automation in a note clip,

and no automation lanes will be created.

While this method is perfect for making a clip self-contained, there are some trade-

offs. If you use this method to record device parameters, you won’t have the same

overview as with track parameter automation. You also won’t be able to later mute the

separate automation edit lanes, or move them independently.

Recording track parameter automation

Track parameter automation is the standard way to automate device parameters.

Each parameter that is automated for a device will get a separate automation lane on

the track. There are no separate Record Enable buttons for automation lanes, only a

global Automation Record Enable button for the whole track.

The Automation Record Enable button.

Before you record automation

Before you start recording automation of a parameter or manually create a parameter

automation track (see below), you may want to set it to a suitable “static value”. By

this, we mean the value the parameter should have whenever it isn’t automated in the

song. Here is why:

D When you first create an automation lane for a parameter either manu-

ally or automatically, its original value will be inserted a a static value

throughout the rest of the song wherever there isn’t an automation clip

with events present on the lane.

Let’s say you want to create a fade-out by recording a fader movement in the Mixer.

Then it’s a good idea to first set the fader to the correct static value (i.e. the value the

fader should be set to before you start the fade-out).

The same thing is true if you want to create a filter sweep for a synthesizer, some-

where within the song: First set the filter frequency to the value it should have else-

where in the song, then record the filter sweep.

This makes it possible to set up a static mix first, and then add some automated pa-

rameter changes anywhere in the song while maintaining the static values elsewhere

in the song.

D The static value can later be manually changed for an automation lane in

Edit mode without overriding any automation.

See “Editing automation”.

Basic procedure

1. Make sure there is a sequencer track for the device.

For devices that can receive note data, a sequencer track is automatically created

together with the device. For a mixer or effect device, you need to add a track man-

ually before you can start recording parameter automation.

1 2 ... 63 64 65 66 67 68 69 70 71 72 73 ... 401 402

Comentarios a estos manuales

Sin comentarios

Propellerhead Reason - 4.0 Manual de operaciones Pagina 68

Comentarios a estos manuales

Relacionado con productos y manuales para Software Propellerhead Reason - 4.0