User manual

Table Of Contents
464
File handling
Exporting and importing standard
MIDI files
Cubase can import and export Standard MIDI Files, which
makes it possible to transfer MIDI material to and from vir-
tually any MIDI application on any platform. When you im-
port and export MIDI files, you can also specify whether
certain settings associated with the tracks should be in-
cluded in the files (automation tracks, volume and pan set-
tings, etc.).
Exporting MIDI files
To export your MIDI tracks as a standard MIDI file, pull
down the File menu and select “MIDI File…” from the Ex-
port submenu. A regular file dialog opens, allowing you to
specify a location and name for the file.
When you have specified a location and a name for the file,
click “Save”. The Export Options dialog opens, allowing you
to specify a number of options for the file – what should be
included in the file, its type and its resolution (see below for
a description of the options).
The Export Options dialog
You will also find these settings in the Preferences (MIDI–
MIDI File page). If you set these up in the Preferences, you
only need to click OK in the Export Options dialog to
proceed.
The dialog contains the following options:
Option Description
Export Inspec-
tor Patch
If this is activated, the MIDI patch settings in the Inspec-
tor – Bank Select and Program Select (used for selecting
sounds in the connected MIDI instrument) are included
as MIDI Bank Select and Program Change events in the
MIDI file.
Export Inspec-
tor Volume/
Pan
If this is activated, Volume and Pan settings made in the
Inspector are included as MIDI Volume and Pan events in
the MIDI file.
Export
Automation
If this is activated, the automation data (as heard during
playback) are converted to MIDI controller events and in-
cluded in the MIDI file, see the chapter “Automation” on
page 188. This also includes automation recorded with
the MIDI Control plug-in (see the separate PDF docu-
ment “Plug-in Reference”).
Note that if a continuous controller (e.g. CC7) has been
recorded but the Read button is deactivated for the auto-
mation track (i.e. the automation is effectively switched
off for this parameter), only the part data for this controller
will be exported.
If this option is deactivated and the Automation Read
button is activated, no Continuous Controllers are ex-
ported. If the Read button is deactivated, the Controller
data of the MIDI part are exported (these will now be han-
dled like “regular” part data).
In most cases, you would probably activate this option.
Export Inserts If this is activated and you are using any MIDI plug-ins as
insert effects, the modifications to the original MIDI notes
that occur as a result of the effect(s) will be included in
the MIDI file. A MIDI delay, for example, will produce a
number of repeats to a MIDI note by actually adding addi-
tional, “echoing” notes at rhythmic intervals – these notes
will be included in the MIDI file if the option is activated.
Export Sends If this is activated and you are using any MIDI plug-ins as
send effects, the modifications to the original MIDI notes
that occur as a result of the effect(s) will be included in
the MIDI file.
Export Marker If this is activated, any markers you have added (see
“Markers” on page 54) will be included in the MIDI file as
standard MIDI file marker events.
Export as
Type 0
If this is activated, the MIDI file will be of type 0 (all data
on a single track, but on different MIDI channels). If you
do not activate this option, the MIDI file will be of Type 1
(data on separate tracks). Which type to choose de-
pends on what you want to do with the MIDI file (in which
application or sequencer it should be used, etc.).
Export
Resolution
You can specify a MIDI resolution between 24 and 960
for the MIDI file. The resolution is the number of pulses, or
ticks, per quarter note (PPQ) and determines the preci-
sion with which you will be able to view and edit the MIDI
data. The higher the resolution, the higher the precision.
The resolution should be chosen depending on the appli-
cation or sequencer with which the MIDI file will be used
though, since certain applications and sequencers may
not be able to handle certain resolutions.