Propellerhead Reason - 4.0 Betriebshandbuch Seite 66

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 402
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 65
THE SEQUENCER
64
Selecting/moving note lanes
Note lanes are not selectable items in the same way that tracks are. Tracks (when se-
lected) will adhere to track/device specific operations on the Edit menu for example.
Individual lanes do not have any comparable edit-related functions.
However, a note lane is selectable in the following circumstances:
D In Edit mode, data for one note lane of a track is shown at a time.
By clicking on a lane you switch the view to the lane you select. See “Editing
Notes”.
D A note lane has a “handle” and can be moved vertically together with all
clips on the lane.
To move a note lane to another position in the list on the same track, click on the
track handle (the leftmost area of the lane) so that it goes dark and drag the track
up or down. Just like when moving tracks, a red insertion line is shown indicating
where the lane will be placed when releasing the mouse.
D Note that it is possible to move note lanes between tracks - this is de-
scribed on page 64.
Merging note lanes
Note lanes on a track can be merged into a single note lane:
D Select the track with the note lanes you wish to merge and then select
“Merge Note Lanes on Tracks” from the Edit menu or the track context
menu.
The note clips on all note lanes will be merged to the top lane.
A percussion track with separate note lanes, one for each drum sound.
The same track after merging.
D Muted lanes or clips on the track will not be included in the merge.
D If there are gaps between the clips on the lanes, several clips will be cre-
ated.
! Note that if there is any performance controller data (e.g. pitch bend) in
several note clips at the same position, only the performance data from
the top lane will be included in the merged clip. See “Recording perfor-
mance controller automation” for details.
Recording automation
In Reason, you can automate virtually all device parameters, creating completely auto-
mated mixes if you like. This is done by recording (or drawing) controller events in the
sequencer.
Performance controller vs. track parameter
automation
Recording automation can be done in two different ways; either as performance con-
troller automation or as track parameter automation.
D Performance controller automation is automatically recorded in note
clips on note lanes.
Any standard MIDI performance controllers that you apply when playing (Pitch
Bend etc.) will be recorded as performance automation in the note clip. A clip on
a note lane can contain any combination of note events, performance automation
events and parameter automation events.
Performance automation is shown as curves in the clip.
D Track parameter automation creates separate automation lanes on a
track, one for each automated parameter.
Automation lanes are shown in the lane area of the track list and can be created
manually or automatically (by tweaking parameters on the device connected to the
track while recording). See “Editing automation”.
An automation lane in the track list.
Which method you should use depends on how you prefer to work and the situation
at hand. The main differences to take into account are the following:
D If you are planning to record automation on several tracks at the same
time using a control surface device, you have to use track parameter au-
tomation.
Track parameter automation has separate, independent record-enable buttons for
automation recording. These can be activated for any number of tracks simulta-
neously, unlike the record-enable buttons for note lanes. (See “Recording automa-
tion on multiple tracks”).
D Performance parameter automation allows you to contain the automa-
tion data in a note clip together with note events.
Standard MIDI performance controllers will always be recorded as performance
parameter automation. See below for more details.
! Note that a parameter may be assigned to both performance parameter
and track parameter automation. See page 87 for details.
Seitenansicht 65
1 2 ... 61 62 63 64 65 66 67 68 69 70 71 ... 401 402

Kommentare zu diesen Handbüchern

Keine Kommentare