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
375
The Logical Editor, Transformer and Input Transformer
Specifying actions
The lower list in the Logical Editor window is the action
list. This is where you specify any changes that should be
made to the found events (relevant for all function types
except Delete and Select).
The handling of the action list is similar to the filter condi-
tion list, but without the brackets and booleans. You sim-
ply add lines by clicking the Add Line button to the right,
and fill out the columns as required. To remove a superflu-
ous action line, select it and click the Delete Line button.
Action Target
This is where you select the property that should be
changed in the events:
Operation
This setting determines what to do with the Action Target.
The options on this pop-up menu are different depending
on the selected Action Target. Below, all available opera-
tions are listed:
Add
Adds the value specified in the Parameter 1 column to the
Action Target.
Subtract
Subtracts the value specified in the Parameter 1 column
from the Action Target.
Multiply by
Multiplies the Action Target value with the value specified
in the Parameter 1 column.
Divide by
Divides the Action Target value by the value specified in
the Parameter 1 column.
Round by
This “rounds” the Action Target value using the value
specified in the Parameter 1 column. In other words, the
Action Target value is changed to the closest value that
can be divided by the Parameter 1 value.
For example, if the Action Target value is 17 and Parame-
ter 1 is 5, the result of rounding will be 15 (the closest
value that can be divided by 5). Another word for this type
of operation would be “quantizing”, and it’s actually possi-
ble to use it for this, by setting the Action Target to “Posi-
tion” and specifying a quantize value with Parameter 1 (in
ticks, with 480 ticks per quarter note).
Set Random Values between
This will set the Action Target value to a random value
within the range specified with Parameter 1 and 2.
Option Description
Position Adjusting this value will move the events.
Length Lets you resize the events (notes only).
Value 1 This adjusts value 1 in the events. As described in the
section “Searching for Value 1 or Value 2” on page 371,
the meaning of value 1 depends on the event type. For
notes, value 1 is the pitch.
Value 2 This adjusts value 2 in the events. As described in the
section “Searching for Value 1 or Value 2” on page 371,
the meaning of value 2 depends on the event type. For
notes, value 2 is the velocity value.
Channel Allows you to change the MIDI channel setting. See
“Searching for MIDI channels” on page 372.
Type Allows you to change an event from one type to another,
e.g. transform aftertouch events to modulation events.
Value 3 This adjusts value 3 in the events, which is used for han-
dling of Noteoff-velocity when searching for properties.
See “Searching for properties” on page 372.