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
255
The Sample Editor
3. Now you can simply point and click in any slice area
and the corresponding slice will be played back from the
beginning to the end.
Listen for “double hits” and slices that contain parts of a single sound.
If you find hitpoints that need to be removed or instances
where a hitpoint needs to be added, the first thing to try is
to change the sensitivity setting – see the following sec-
tion.
Setting the sensitivity
The loop is first analyzed to determine where hitpoints
should appear (where the individual “beats” in the loop are),
then you manually set the sensitivity with the sensitivity
slider to determine how many hitpoints there should be.
• Try raising the sensitivity to add “missing” hitpoints and
lowering it to remove unwanted hitpoints.
This may or may not work, depending on the situation, but as a general
rule you should try this first.
• Audition the slices again to determine if changing the
sensitivity has improved matters.
The “Use” pop-up menu in Hitpoints tab of the Sample
Editor Inspector affects which hitpoints are shown and is
a useful tool for removing unwanted hitpoints. The options
on the pop-up menu are:
If your main reason for slicing the loop is to change the
tempo, you generally need as many slices as you can get,
but never more than one per individual “hit” in the loop.
If you want to create a groove (see “Creating groove
quantize maps” on page 257), you should try to get ap-
proximately one slice per eighth note, sixteenth note or
whatever the loop requires.
Disabling slices
You might run into situations where there are too many
slices – a single sound may have been split into two
slices, for example. You could of course reduce the sensi-
tivity to get rid of the hitpoints you don’t want, but then
other hitpoints could disappear too, which may be unde-
sirable. What you need to do in a situation like this is to
disable an individual slice:
1. Open the Hitpoints tab in the Sample Editor Inspector
and select the Edit Hitpoints tool.
2. Press [Alt]/[Option] and move the pointer to the han-
dle (the triangle).
The pointer turns into a cross.
3. Click on the handle of the hitpoint you wish to disable.
The hitpoint handle is diminished and its line disappears to indicate that
it is disabled.
4. Now, the hitpoint won’t be taken into account when
you create slices.
5. To reactivate a disabled hitpoint, [Alt]/[Option]-click
on the hitpoint handle in Edit Hitpoints tool.
Option Description
All All hitpoints are shown (taking the sensitivity slider into
account).
1/4, 1/8,
1/16, 1/32
Only hitpoints that are close to the selected note value
positions within the loop will be shown (e.g. close to ex-
act sixteenth note positions, if the 1/16 option is se-
lected). Again, the sensitivity slider is taken into account.
Metric Bias This is like the “All” mode, but all hitpoints that are close
to even meter divisions (1/4 notes, 1/8 notes, 1/16
notes, etc.) get a “sensitivity boost” – they are visible at
lower sensitivity slider settings. This is useful if you are
working with dense or cluttered material with a lot of hit-
points, but you know that the material is based on a strict
meter. By selecting Metric Bias it will be easier to find the
hitpoints close to the meter position (although most other
hitpoints are also available, at higher sensitivity settings).
Option Description