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
386
The Project Logical Editor
Combining multiple condition lines
As described above, you can add condition lines by click-
ing the Add Line button to the right of the list. The result of
combining condition lines depends on the boolean And/
Or operators and the brackets.
The bool column
By clicking in the “bool” column to the right in the list, you
can select a boolean operator: “And” or “Or”. A boolean
operator combines two condition lines and determines the
result in the following way:
Ö If two condition lines are combined with a boolean And,
both conditions must be fulfilled for an element to be found.
The Project Logical Editor will only find MIDI Tracks.
Ö 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. This is how it works:
Ö Without brackets, the conditional expressions are
evaluated 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 wanted to find all Audio parts and events that
either 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. The rule behind this is:
Ö 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.
You add brackets by clicking in the bracket columns and
selecting an option. Up to triple brackets can be selected.
Editing filter conditions as text
You can also edit filter conditions as text. This works just
like in the Logical Editor for MIDI, see “Editing filter condi-
tions as text” on page 374.
!
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 don’t have to think
about the boolean column – just add the required
lines and make the usual filter settings.