6.0
Table Of Contents
- Table of Contents
- Part I: Getting into the details
- About this manual
- Setting up your system
- VST Connections
- The Project window
- Working with projects
- Creating new projects
- Opening projects
- Closing projects
- Saving projects
- The Archive and Backup functions
- Startup Options
- The Project Setup dialog
- Zoom and view options
- Audio handling
- Auditioning audio parts and events
- Scrubbing audio
- Editing parts and events
- Range editing
- Region operations
- The Edit History dialog
- The Preferences dialog
- Working with tracks and lanes
- Playback and the Transport panel
- Recording
- Quantizing MIDI and audio
- Fades, crossfades and envelopes
- The arranger track
- The transpose functions
- Using markers
- The Mixer
- Control Room (Cubase only)
- Audio effects
- VST instruments and instrument tracks
- Surround sound (Cubase only)
- Automation
- Audio processing and functions
- The Sample Editor
- The Audio Part Editor
- The Pool
- The MediaBay
- Introduction
- Working with the MediaBay
- The Define Locations section
- The Locations section
- The Results list
- Previewing files
- The Filters section
- The Attribute Inspector
- The Loop Browser, Sound Browser, and Mini Browser windows
- Preferences
- Key commands
- Working with MediaBay-related windows
- Working with Volume databases
- Working with track presets
- Track Quick Controls
- Remote controlling Cubase
- MIDI realtime parameters and effects
- Using MIDI devices
- MIDI processing
- The MIDI editors
- Introduction
- Opening a MIDI editor
- The Key Editor – Overview
- Key Editor operations
- The In-Place Editor
- The Drum Editor – Overview
- Drum Editor operations
- Working with drum maps
- Using drum name lists
- The List Editor – Overview
- List Editor operations
- Working with SysEx messages
- Recording SysEx parameter changes
- Editing SysEx messages
- The basic Score Editor – Overview
- Score Editor operations
- Expression maps (Cubase only)
- Note Expression (Cubase only)
- The Logical Editor, Transformer, and Input Transformer
- The Project Logical Editor (Cubase only)
- Editing tempo and signature
- The Project Browser (Cubase only)
- Export Audio Mixdown
- Synchronization
- Video
- ReWire
- File handling
- Customizing
- Key commands
- Part II: Score layout and printing (Cubase only)
- How the Score Editor works
- The basics
- About this chapter
- Preparations
- Opening the Score Editor
- The project cursor
- Playing back and recording
- 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 clef, key, and time signature
- Transposing instruments
- Printing from the Score Editor
- Exporting pages as image files
- Working order
- Force update
- Transcribing MIDI recordings
- 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
- Tips and Tricks
- Index
458
The Project Logical Editor (Cubase only)
• If two condition lines are combined with a boolean Or,
one of the conditions (or both) must be fulfilled for an ele-
ment to be found.
The Project Logical Editor will find all parts or events that match exactly
the cycle.
Using brackets
The bracket (parenthesis) columns let you enclose two or
more condition lines, dividing the conditional expression
into smaller units. This is only relevant when you have
three or more condition lines and want to use the boolean
Or operator.
You add brackets by clicking in the bracket columns and
selecting an option. Up to triple brackets can be selected.
• Without brackets, the conditional expressions are eval-
uated according to their order in the list.
Here, the Project Logical Editor will find all audio parts and events
whose name contains perc as well as other parts and events (e. g. MIDI
parts) whose name contains drums.
Maybe you want to find all audio parts and events that ei-
ther had the name perc or the name drums (but no other
parts or events named drums)? Then you need to add
some brackets:
Here, all audio parts or events will be found whose name contains perc
or drums.
Ö Expressions within brackets are evaluated first.
If there are several layers of brackets, these are evaluated “from the inside
out”, starting with the innermost brackets.
Specifying actions
The lower list in the Project Logical Editor window is the
action list. This is where you specify any changes that are
made to the found elements, relevant for the function type
Transform.
You can perform two different kinds of actions: track-
based actions (such as Track Operation, Name) and
event-based actions (such as Position, Length, Name).
There are also actions that only take effect on automation
data (Trim).
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 “+” button, and fill out the
columns as required. To remove a superfluous action line,
select it and click the “-” button.
Action Target
This is where you select the property that is changed. The
Operations determine what to do with the Action Target.
Below, all available operations are listed:
Position
Adjusting this value will move the elements. This parameter
is interpreted via the time base setting in the Bar Range/
Time Base column, with the exception of the Random set-
ting, which uses the time base of the affected events:
!
When you add a new condition line, the boolean set-
ting defaults to And. Therefore, if all you want to do is
set up two or more conditions that all must be met
for an element to be found, you do not have to think
about the boolean column – just add the required
lines and make the usual filter settings.
Operation Description
Add Adds the value specified in the Parameter 1 column to the
Position.
Subtract Subtracts the value specified in the Parameter 1 column
from the Position.
Multiply by Multiplies the Position value with the value specified in the
Parameter 1 column.
Divide by Divides the Position value by the value specified in the Para-
meter 1 column.
Round by This “rounds” the Position value using the value specified in
the Parameter 1 column. In other words, the Position value is
changed to the closest value that can be divided by the Pa
-
rameter 1 value.
For example, if the Position value is 17 and Parameter 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 is actually possible to use it for
this, by specifying a quantize value with Parameter 1 (in ticks,
with 480 ticks per quarter note).