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
389
The Project Logical Editor
Working with presets
The Presets section in the bottom right section of the win-
dow allows you to load, store and manage Project Logical
Editor presets. A preset contains all settings in the window,
which means you can simply load a preset and click Do It.
Ö To load a preset, select it from the Presets menu.
Storing your own settings as a preset
If you have made Project Logical Editor settings that you
want to use again, you can store them as a preset:
1. You can enter some explanatory text in the Comment
field.
An extra description of the preset can be useful, especially if the settings
are complex.
2. Click the Store button in the Presets section.
A dialog for specifying a name for the new preset is displayed.
3. Enter a name for the preset and click OK.
The preset is stored.
Ö To remove a preset, load it and click the Remove but-
ton.
Organizing and sharing presets
The Project Logical Editor presets are stored within the ap-
plication folder in the Presets\Logical Edit Project subfolder
(see also “Where are the settings stored?” on page 473).
While these files cannot be edited manually, you can reor-
ganize them (e.g. putting them in subfolders) like any files.
This also makes it easy to share presets with other Cu-
base users, by transferring the individual preset files.
Ö The list of presets is read each time the Project Logi-
cal Editor is opened.
Setting up key commands for your presets
If you have stored Project Logical Editor presets, you can
set up key commands for them:
1. Pull down the File menu and select “Key Commands…”.
The Key Commands dialog appears.
2. Use the list in the Commands column to navigate to
the category “Process Project Logical Editor” and click
the plus-sign to display the items in the folder.
3. In the list, select the item to which you wish to assign a
key command, click in the “Type in Key” field and enter a
new key command.
4. Click the Assign button above the field.
The new key command appears in the Keys List.
5. Click OK to exit the dialog.
For more information on Key Commands, see the chapter
“Key commands” on page 475.