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
74
Recording
Recording
Recording is done using any of the general recording
methods (see “Basic recording methods” on page 66).
When you finish recording, an audio file is created in the
Audio folder within the project folder. In the Pool, an audio
clip is created for the audio file, and an audio event that
plays the whole clip appears on the recording track. Fi-
nally, a waveform image is calculated for the audio event. If
the recording was very long, this may take a while.
Ö If the option “Create Audio Images During Record” is
activated in the Preferences (Record-Audio page), the
waveform image will be calculated and displayed during
the actual recording process.
This real-time calculation uses some processing power – if your proces-
sor is slow or you are working on a CPU-intensive project, you should
consider turning this option off.
Undoing recording
If you decide that you don’t like what you just recorded,
you can delete it by selecting Undo from the Edit menu.
The following will happen:
• The event(s) you just created will be removed from the Project
window.
• The audio clip(s) in the Pool will be moved to the Trash folder.
• The recorded audio file(s) will not be removed from the hard
disk.
However, since their corresponding clips are moved to
the Trash folder, you can delete the files by opening the
Pool and selecting “Empty Trash” from the Media menu,
see “Deleting from the hard disk” on page 275.
Recording overlapping events
The basic rule for audio tracks is that each track can play
back a single audio event at a time. This means that if two
or more events are overlapping, only one of them will be
heard at any given time.
What happens when you record overlapping events
(record in an area where there are already events on the
track) depends on the Linear Record Mode setting on the
Transport panel:
• In “Normal” or “Merge” mode, recording where some-
thing has already been recorded creates a new audio
event that overlaps the previous one(s).
When you record audio, there is no difference between “Normal” and
“Merge” mode – the difference only applies to MIDI recording (see
“About overlap and the Record Mode setting” on page 81).
• In “Replace” mode, existing events (or portions of
events) that are overlapped by the new recording will be
removed.
This means that if you record a section in the middle of a longer existing
recording, that original event will be cut into two events with a gap for the
new event.
Which event will be heard?
If two or more events are overlapping, you will only hear the
events (or portions of events) that are actually visible. Over-
lapped (hidden) events or sections are not played back.
• The functions “Move to Front” and “Move to Back” on
the Edit menu (see “Moving events” on page 46) are use-
ful for managing overlapping events, as is the “To Front”
function (see below).