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
380
The Project Logical Editor
Introduction
On the Edit menu you will find the function “Project Logi-
cal Editor…” that opens a Project Logical Editor for the
entire project. It works similar to the Logical Editor on the
MIDI menu, see “The Logical Editor, Transformer and In-
put Transformer” on page 367. The most important differ-
ence is that the Logical Editor for MIDI works at the event
level, whereas the Project Logical Editor works at the
project level and is therefore a very powerful tool for
“search and replace” functions in your project.
Ö The MIDI events in the MIDI parts will not be affected
by the Project Logical Editor operations. If you want to
change MIDI notes or controller data, you have to use the
Logical Editor, see “The Logical Editor, Transformer and
Input Transformer” on page 367.
The Project Logical Editor allows you to create “macros”,
e.g. for special track type operations on tracks that are
named identically. You can use its functions to delete all
muted MIDI parts or to toggle the open state of all folder
tracks in your project, etc.
Included with the Project Logical Editor are a number of
presets that give you an impression of the great possibili-
ties that this feature offers, see “Selecting a preset” on
page 381. Many of them can also be used as starting
points when you set up your own editing operations.
The principle for the Project Logical Editor is this:
• You set up filter conditions to find certain elements.
This could be elements of a certain type, with certain attributes or values or
on certain positions, in any combination. You can combine any number of
filter conditions and make composite conditions using AND/OR operators.
• You select the basic function to be performed.
The options are Transform (changing properties of the found elements),
Delete (removing the elements) and Select (selecting the found elements).
• You set up a list of actions, which specify exactly what
should be done.
This is not necessary for all functions. For example, the Delete function
does not require any additional action specifications – it simply removes
all found elements.
By combining filter conditions, functions and the specific
actions, you can perform very powerful processing.
Opening the Project Logical Editor
1. Open the desired project.
All elements in the project will be affected, you do not have to make any
selection.
2. Select “Project Logical Editor…” from the Edit menu.
Window overview
!
The Project Logical Editor allows all kinds of settings
that may not always make sense. Experiment a bit be-
fore applying your edits to important projects. You can
undo the operations by using the Undo command on
the Edit menu.
This is where you select a function
(Transform, Delete, etc.). The field to the
right shows an additional explanation of
the selected function.
This is the filter condition
list, specifying which el-
ements to look for.
This is the action
list, specifying e.g.
how to change the
found elements.
This is where you load,
store and handle pre-
sets. See “Working with
presets” on page 389.
The “Do It” button
performs the task
you have set up.