6.0

333
File handling
The dialog contains the following options: Ö The MIDI file will include the tempo information of the
project (i. e. it will include the tempo and time signature
events of the Tempo Track Editor or, if the tempo track is
deactivated on the Transport panel, the current tempo and
time signature).
Ö Inspector settings other than those specified in the
Export options are not included in the MIDI file! To include
these, you need to convert the settings to “real” MIDI events
and properties by using the Merge MIDI in Loop function for
each track, see
“Merge MIDI in Loop” on page 246.
Importing MIDI files
To import a MIDI file from disk, proceed as follows:
1. Select “MIDI File…” from the Import submenu of the
File menu.
2. If there is already an open project, a dialog opens in
which you can select whether a new project is created for
the file.
If you select “No”, the MIDI file will be imported into the current project.
3. Locate and select the MIDI file in the file dialog that
opens and click Open.
• If you choose to create a new project, select the project
folder.
Select an existing project folder or create a new one.
The MIDI file is imported. The result depends on the con-
tents of the MIDI file and the Import Options settings in the
Preferences dialog (MIDI–MIDI File page). The Import Op
-
tions are as follows:
Option Description
Export
Inspector
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
Inspector
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 156. Cubase Elements only: This also includes au-
tomation recorded with the MIDI Control plug-in (see the
separate PDF document “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 but-
ton is activated, no Continuous Controllers are exported.
If the Read button is deactivated, the Controller data of
the MIDI part are exported (these will now be handled like
“regular” part data).
In most cases it is recommended to activate this option.
Export Inserts If this is activated, any MIDI modifiers that you have
added will be included in the MIDI file.
Export Markers If this is activated, any markers you have added (see “Us-
ing markers” on page 108) 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 depends 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.
Choose the resolution depending on the application or
sequencer with which the MIDI file will be used, though,
since certain applications and sequencers may not be
able to handle certain resolutions.
Export Locator
Range
If this is activated, only the range between the locators
will be exported.
Export
includes Delay
If this is activated, the delay of the MIDI track will be in-
cluded in the MIDI file. For more information about the
Delay option, see
“Basic track settings” on page 234.
Song name for
Type 0
You can use this text field to change the name of the MIDI
file as displayed when loading this file in a keyboard.
Option Description
Extract First
Patch
If this is activated, the first Program Change and Bank
Select events for each track are converted to Inspector
settings for the track.
Extract First
Volume/Pan
If this is activated, the first MIDI Volume and Pan events
for each track are converted to Inspector settings for the
track.
Import Con-
troller as Auto-
mation Tracks
If this is activated, MIDI controller events in the MIDI file
will be converted to automation data for the MIDI tracks. If
this is deactivated, controller data for the MIDI Parts will
be imported.
Import to Left
Locator
If this is activated, the imported MIDI file will be placed so
that it starts at the position of the left locator – otherwise
it will start at the beginning of the project. Note that if you
choose to have a new project created automatically, the
MIDI file will always start at the beginning of the project.