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
392
Working with System Exclusive messages
Transmitting a bulk dump back to a device
1. Make sure the MIDI track with the System Exclusive
data is routed to the device.
You may want to check your device’s documentation to find details about
which MIDI channel should be used, etc.
2. Solo the track.
This might not be necessary, but it is a good safety measure.
3. Make sure the device is set up to receive SysEx mes-
sages (often, receiving SysEx is turned off by default).
4. If necessary, put the device in “Standby to Receive
System Exclusive” mode.
5. Play back the data.
Some advice
• Don't transmit more data than you need. If all you want is a sin-
gle program, don't send them all, it will only make it harder to
find the one you want. Usually, you can specify exactly what
you want to send.
• If you want the sequencer to dump the pertinent sounds to
your instrument each time you load a project, put the SysEx
data in a silent “count-in” before the project itself starts.
• If the dump is very short (for instance, a single sound) you can
put it in the middle of the project to re-program a device on the
fly. However, you can achieve the same effect by using Program
Change. This is definitely preferable, since less MIDI data is
sent and recorded. Some devices may be set up to dump the
settings for a sound as soon as you select it on the front panel.
• If you create parts with useful “SysEx dumps”, you can put
these on a special muted track. When you want to use one of
them, drag it to an empty unmuted track and play it back from
there.
• Do not transmit several SysEx dumps to several instruments at
the same time.
• Make a note of the current device ID setting of the instrument.
If you change this, the instrument may refuse to load the dump
later.
Recording System Exclusive
parameter changes
Often you can use SysEx to remotely change individual
settings in a device, e.g. open a filter, select a waveform,
change the decay of the reverb etc. Many devices are also
capable of transmitting changes made on the front panel
as SysEx messages. These can be recorded in Cubase,
and thus incorporated into a regular MIDI recording.
Here's how it works: let's say you open up a filter while
playing some notes. In that case, you will record both the
notes and the SysEx messages generated when you
opened of the filter. When you play it back, the sound
changes exactly like it did when you recorded it.
1. Open the Preferences dialog from the File menu, se-
lect the MIDI–MIDI Filter page and make sure that SysEx is
recorded, i.e. the Sysex checkbox in the Record section is
deactivated.
2. Make sure the instrument is actually set to transmit
changes of front panel controls as SysEx messages.
3. Record normally.
When you’re done, you can check that the events were recorded pro-
perly in the List Editor.