User manual
Table Of Contents
- Table of Contents
- Part I: Getting into the details
- About this manual
- VST Connections: Setting up input and output busses
- The Project window
- Playback and the Transport panel
- Recording
- Fades, crossfades and envelopes
- The Arranger track
- Folder tracks
- Using markers
- The Transpose functions
- The mixer
- Control Room (Cubase only)
- Audio effects
- VST Instruments and Instrument tracks
- Introduction
- VST Instrument channels vs. instrument tracks
- VST Instrument channels
- Instrument tracks
- Comparison
- Automation considerations
- What do I need? Instrument channel or Instrument track?
- Instrument Freeze
- VST instruments and processor load
- Using presets for VSTi configuration
- About latency
- External instruments (Cubase only)
- Surround sound (Cubase only)
- Audio processing and functions
- The Sample Editor
- The Audio Part Editor
- The Pool
- VST Sound
- The MediaBay
- Track Presets
- Track Quick Controls
- Automation
- MIDI realtime parameters and effects
- MIDI processing and quantizing
- The MIDI editors
- The Logical Editor, Transformer and Input Transformer
- The Project Logical Editor
- Working with System Exclusive messages
- Working with the Tempo track
- The Project Browser
- Export Audio Mixdown
- Synchronization
- Video
- ReWire
- File handling
- Customizing
- Key commands
- Part II: Score layout and printing
- How the Score Editor works
- The basics
- About this chapter
- Preparations
- Opening the Score Editor
- The project cursor
- Page Mode
- Changing the Zoom factor
- The active staff
- Making page setup settings
- Designing your work space
- About the Score Editor context menus
- About dialogs in the Score Editor
- Setting key, clef and time signature
- Transposing instruments
- Working order
- Force update
- Transcribing MIDI recordings
- About this chapter
- About transcription
- Getting the parts ready
- Strategies: Preparing parts for score printout
- Staff settings
- The Main tab
- The Options tab
- The Polyphonic tab
- The Tablature tab
- Situations which require additional techniques
- Inserting display quantize changes
- Strategies: Adding display quantize changes
- The Explode function
- Using “Scores Notes To MIDI”
- Entering and editing notes
- About this chapter
- Score settings
- Note values and positions
- Adding and editing notes
- Selecting notes
- Moving notes
- Duplicating notes
- Cut, copy and paste
- Editing pitches of individual notes
- Changing the length of notes
- Splitting a note in two
- Working with the Display Quantize tool
- Split (piano) staves
- Strategies: Multiple staves
- Inserting and editing clefs, keys or time signatures
- Deleting notes
- Staff settings
- Polyphonic voicing
- About this chapter
- Background: Polyphonic voicing
- Setting up the voices
- Strategies: How many voices do I need?
- Entering notes into voices
- Checking which voice a note belongs to
- Moving notes between voices
- Handling rests
- Voices and display quantize
- Creating crossed voicings
- Automatic polyphonic voicing - Merge All Staves
- Converting voices to tracks - Extract Voices
- Additional note and rest formatting
- Working with symbols
- Working with chords
- Working with text
- Working with layouts
- Working with MusicXML
- Designing your score: additional techniques
- Scoring for drums
- Creating tablature
- The score and MIDI playback
- Printing and exporting pages
- Frequently asked questions
- Tips and Tricks
- Index
376
The Logical Editor, Transformer and Input Transformer
Set Relative Random Values between
This will add a random value to the current Action Target
value. The added random value will be within the range
specified with Parameter 1 and 2. Note that these can be
set to negative values.
For example, if you set Parameter 1 to -20 and Parameter
2 to +20, the original Action Target value will get a ran-
dom variation, never exceeding ±20.
Set to fixed value
This sets the Action Target to the value specified in the
Parameter 1 column.
Add Length
This is only available when Action Target is set to Position.
Furthermore, it is only valid if the found events are notes
(and thus have a length). When Add Length is selected,
the length of each note event will be added to the Position
value. This can be used for creating new events (using the
Insert function) positioned relative to the end positions of
the original notes.
Transpose to Scale
This is only available when Action Target is set to Value 1,
and when the filter conditions are specifically set up to
find notes (a “Type = Note” filter condition line has been
added). When “Transpose to Scale” is selected, you can
specify a musical scale using the Parameter 1 and 2 col-
umns. Parameter 1 is the key (C, C#, D, etc.) while Pa-
rameter 2 is the type of scale (major, melodic or harmonic
minor, etc.).
Each note will be transposed to the closest note in the se-
lected scale.
Use Value 2
This is only available when Action Target is set to Value 1.
If this option is selected, the Value 2 setting in each event
will be copied to the Value 1 setting.
For example, this would be useful if you are transforming
all Modulation controllers to Aftertouch events (since con-
trollers use Value 2 for their amount, while Aftertouch uses
Value 1 – see “Searching for Value 1 or Value 2” on page
371).
Use Value 1
This is only available when Action Target is set to Value 2.
If this option is selected, the Value 1 setting in each event
will be copied to the Value 2 setting.
Mirror
This is only available when Action Target is set to Value 1
or Value 2. When this option is selected, the values will be
“mirrored” or “flipped” around the value set in the Parame-
ter 1 column.
In the case of notes, this will invert the scale, with the key
set in the Parameter 1 column as “center point”.
Linear Change in Loop Range
This will affect events within the loop range (between the
left and right locators) only. It will create a linear “ramp” of
values (replacing the original values) starting at the value
in the Parameter 1 column and ending at the Parameter 2
value.
This can be used for creating linear controller sweeps, ve-
locity ramps, etc.
Relative Change in Loop Range
As with the previous option, this will create a ramp of val-
ues, affecting events in the cycle loop range only. How-
ever, here the changes are “relative”, meaning that values
will be added to the existing values.
In other words, you set up a value ramp starting at Para-
meter 1 and ending at Parameter 2 (note that the Parame-
ter values can be negative). The resulting value ramp is
then added to the existing values for the events within the
cycle loop range.
For example, if you apply this to note velocities with Param-
eter 1 set to 0 and Parameter 2 set to -100, you create a
velocity fade-out, keeping the original velocity relations: