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
244
The Sample Editor
A new clip is created and added to the Pool, and another
Sample Editor window will open with the new clip. The
new clip will refer to the same audio file as the original clip,
but will only contain the audio corresponding to the selec-
tion range.
Working with regions
Regions are sections within a clip. One of the main uses for
regions is Cycle recording, in which the different “takes”
are stored as regions (see “Recording audio in cycle mode”
on page 75). You can also use this feature for marking im-
portant sections in the audio clip. Regions can be dragged
into the Project window from the Editor or the Pool to cre-
ate new audio events. You can also export a region to disk
as a new audio file, from the Pool.
Regions are best created, edited and managed in the
Sample Editor.
Creating a region
1. Select the range you want to convert into a region.
2. Click the “Show Regions” button on the toolbar, or ac-
tivate the “Regions” option on the Elements submenu on
the Quick menu.
The regions list is displayed to the right in the Sample Editor window.
3. Click the Add region button above the Regions list (or
select “Event or Range as Region” from the Advanced
submenu of the Audio menu).
A region is created, corresponding to the selected range.
4. To name the region, double-click on it in the list and
enter a new name.
Regions can be renamed at any time, using this procedure.
• When a region is selected in the Regions list, it is in-
stantly displayed and selected in the Sample Editor.
Creating regions from Hitpoints
If your audio event contains calculated hitpoints, you can
choose to automatically create regions from hitpoints. This
can be useful to isolate recorded sounds. For further infor-
mation on hitpoints, see “Working with hitpoints and sli-
ces” on page 252.
Editing regions
The region selected in the list is displayed in gray in the
waveform display and thumbnail.
There are two ways to edit the start and end position of a
region:
• Click and drag its start and end handles in the waveform
display (with any tool).
When you move the pointer over the handles, it will automatically change
to an arrow pointer to indicate that you can drag the handles.
• Edit the Start and End positions numerically in the Re-
gions list.
The positions are shown in the display format selected for the ruler and
info line, but are relative to the start of the audio clip, rather than the
project timeline.
Auditioning regions
You can listen to a region by selecting it in the list and
clicking the Play Region button (above the list). The region
will play back once or repeatedly, depending on whether
the Loop icon on the toolbar is activated or not.