Steinberg Cubase SX/SL 3 Operation Manual

							CUBASE SX/SLFile handling32 – 741
Exporting and importing tracks (Cubase SX only)
You can export Cubase SX tracks (of any type) for later import into 
other Cubase SX projects (or Nuendo projects). Everything associ-
ated with the tracks will be exported (mixer channel settings, automa-
tion subtracks, parts and events etc.) and a separate “media” folder 
will be created, containing copies of all referenced audio files.
Project specific settings such as tempo are not part of the exported 
track files.
Exporting tracks
1.Select the tracks that you wish to export.
2.Pull down the File menu and open the Export submenu. 
3.On the submenu, select “Selected Tracks...”.
A file dialog appears allowing you to select or create (and name) an empty destination 
folder for the exported tracks.
4.Click OK.
The tracks will be saved in the specified folder, and will contain two 
items; a XML file named after the enclosing folder and a subfolder 
named “Media” which will contain any associated audio or video files.
Importing tracks
The Import Track Archive function lets you import track exported from 
another Cubase SX (or Nuendo) project.
•Note that the sample rate used in the project you import tracks to has 
to match the sample rate in the original project!
If not, audio files will play back at the wrong speed.
1.Pull down the File menu and open the Import submenu.
2.On the submenu, select “Track Archive...”.
3.In the file dialog that appears, locate the XML file, select it and click 
Open.
The “Copy files to Project Folder?” dialog appears just like when importing audio files. 
4.Click Yes to copy the files into your current project or No to leave 
them in their current location.
The tracks are imported, complete with all contents and settings. 
						

							CUBASE SX/SL32 – 742 File handling
Exporting and importing OMF files (Cubase SX only)
Open Media Framework Interchange (OMFI) is a platform independent 
file format intended for transfer of digital media between different appli-
cations. Cubase SX can import and export OMF files (file extension 
“.omf”), allowing you to use Cubase SX in conjunction with other audio 
and video applications.
Exporting OMF files
1.Pull down the File menu and open the Export submenu. 
2.On the submenu, select “OMF...”.
The OMF Export Setup dialog appears.
3.Use the track list to the left to select which tracks should be included 
in the exported file.
To select all tracks, click the “Select All” button. Normally, the whole project is included - 
to export the range between the locators only, activate “From Left to Right Locator”.
4.Select “1.0 File” or “2.0 File” depending on which OMFI version is 
supported by the application in which you plan to import the file.
5.Select whether you want to include all audio data in the OMF file (“Ex-
port All to One File”) or use references only (“Export Media File Refer-
ences”).
If you choose “Export All to One File”, the OMF file will be totally “self-contained”, but 
possibly very large. If you choose “Export Media File References”, the file will be small, 
but the referenced audio files must be available for the receiving application.
6.If you selected the “2.0 File” option above you can choose whether to 
include the volume settings and fades for the events (as set up with 
the event volume and fade handles) as well as the clip names – to in-
clude these in the OMF file, activate “Export Clip Based Volume”, 
“Use Fade Curves” and/or “Export Clip Names” respectively.
7.Specify a sample size (resolution) and sample rate for the exported 
files (or use the current project settings).
8.If you activate “Quantize Events to Frames”, the event positions in the 
exported file will be moved to exact frames.
9.Click OK, and specify a name and location in the file dialog that 
appears. 
						

							CUBASE SX/SLFile handling32 – 743
The exported OMF file will contain (or make reference to) all audio files 
that are played in the project (including fade and edit files). It will not in-
clude unused audio files referenced in the Pool, or any MIDI data. Video 
files are not included, but Cubase SX stores the start positions of 
Video Events in the OMF file, allowing you to manually import video files 
in the other OMF application (see below).
Importing OMF files
1.Pull down the File menu and open the Import submenu.
2.On the submenu, select “OMF...”.
3.In the file dialog that appears, locate the OMF file and click Open.
A project file dialog appears, allowing you to specify a folder for the new project.
4.Select an existing project folder or create a new one by typing its 
name in the dialog.
5.If the OMF file contains Video Event information, you are asked whether 
you want to create Markers at the start position of the Video Events.
This allows you to manually import the video files, using the Markers as position references.
A new, untitled project is created, containing the Audio Events of the 
imported OMF file. 
						

							CUBASE SX/SL32 – 744 File handling
Exporting and importing MIDI files
Cubase SX/SL can import and export Standard MIDI Files, which 
makes it possible to transfer MIDI material to and from virtually any 
MIDI application, on any platform. When you import and export MIDI 
files, you can also specify whether certain settings associated with the 
tracks should be included in the files (automation subtracks, volume 
and pan settings 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 Export submenu. A regular file 
dialog appears, 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”. At this point, the Export Options dialog appears, 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 descriptions of the 
options).
The Export Options dialog.
You will also find these settings in the Preferences dialog (MIDI-MIDI 
File page). If you set these up once and for all in the Preferences, you 
only need to click OK in the Export Options dialog to proceed.
The dialog contains the following options:  
						

							CUBASE SX/SLFile handling32 – 745
• The MIDI File will include the Tempo track.
Option Description
Export Inspector 
PatchIf this is checked, the MIDI patch settings in the Inspector – Bank 
Select and Program Select (used for selecting sounds in the con-
nected MIDI instrument) are included as MIDI Bank Select and 
Program Change events in the MIDI file.
Export Inspector 
Volume/PanIf this is checked, 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 checked, recorded automation (see page 318) is con-
verted to MIDI controller events and included in the MIDI file. This 
also includes automation recorded with the MIDIControl plug-in. 
This is described in the “MIDI effects” chapter in the separate MIDI 
Devices and Features pdf.
Export Inserts If this is checked and you are using any MIDI plug-ins as insert ef-
fects, 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 additional, “echoing” notes at rhythmic intervals – 
these notes will be included in the MIDI file if the option is activated.
Export Sends If this is checked and you are using any MIDI plug-ins as send ef-
fects, 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 checked, any markers you have added (see page 167) will 
be included in the MIDI file as Standard MIDI File Marker events.
Export as Type 0 If this is checked, the MIDI file will be of Type 0 (all data on a single 
track, but on different MIDI channels). If you don’t check this op-
tion, 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 – 960 for the MIDI 
file. The resolution is the number of pulses, or ticks, per quarter 
note (PPQ) and determines the precision 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 application or sequencer with which the MIDI file should be 
used though, since certain applications and sequencers may not 
be able to handle certain resolutions. 
						

							CUBASE SX/SL32 – 746 File handling
• Inspector settings (other than patch, volume, pan and effects – see 
above) 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 
page 508.
Importing MIDI Files
To import a MIDI file from disk, proceed as follows:
1.Select “MIDI File...” from the Import submenu on the File menu.
2.In the dialog that appears, select whether a new project should be 
created for the file or not.
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 appears, and click 
Open.
4.If you choose to have a new project created, you are asked to specify 
a project folder for the new project.
Select an existing project folder or create a new one by selecting a location for it and 
typing its name in the dialog. 
						

							CUBASE SX/SLFile handling32 – 747
The MIDI file is imported. The result depends on the contents of the 
MIDI file and the Import Options settings in the Preferences dialog – 
MIDI-MIDI File page. The Import Options are as follows:
As mentioned on page 745, the result also depends on what type of 
MIDI file it is – Type 0 or Type 1:
• If the MIDI file is of Type 0 (all data on a single track), only one MIDI track will 
be created.
This track will be set to MIDI Channel “Any”, allowing all MIDI events to play back on their 
original channels. You can use the Dissolve Part function on the MIDI menu to distribute 
the events onto different tracks with different MIDI Channels (see page 530).
• If the MIDI file is of Type 1 (data on several tracks) a number of new MIDI 
tracks and parts will be created.
In both cases, the Tempo track is adjusted according to the Tempo 
track in the MIDI file.
Option Description
Extract First Patch If this is checked, 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 checked, the first MIDI Volume and Pan events for 
each track are converted to Inspector settings for the track.
Import Controller as Au-
tomationtrackIf this is checked, MIDI controller events in the MIDI file will 
be converted to automation data for the MIDI tracks.
Import to Left Locator If this is checked, 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.
Import Marker If this is checked, Standard MIDI File Markers in the file will 
be imported and converted to Cubase SX/SL markers.
Import dropped File as 
single PartIf this is activated and you drag and drop a MIDI file into the 
project, the whole file will be placed on a single track.
Ignore Mastertrack 
Events on MergeIf this is activated and you import a MIDI file into the current 
project, tempo track data in the MIDI file is ignored. The im-
ported MIDI file will play according to the current Tempo 
track in the project. 
						

							CUBASE SX/SL32 – 748 File handling
It is also possible to import a MIDI file from disk by dragging and drop-
ping it from the Windows Explorer or the Mac OS Finder into the Cubase 
SX/SL Project window. The Import Options apply if you use this method 
as well.
Importing Cubase VST files
As described on page 734, the regular Open function can open 
projects made in Cubase SX/SL or Nuendo. It is also possible to im-
port files created in older versions of Cubase. There are three options 
for this on the File – Import submenu:
Import Cubase Song
This will open a Song file (Windows file extension “.all”) created in Cu-
base 5.0 or later and convert it to a Cubase SX/SL project. When im-
porting a Song, you will be asked to specify a folder for the new project, 
as usual.
• Cubase Songs can contain more than one Arrangement (containing in-
dependent part and event data). If this is the case, you will be asked 
which one of these Arrangements to import.
To import all Arrangements in a Cubase Song, simply repeat this for all Arrangements, 
and save each as a separate project. 
						

							CUBASE SX/SLFile handling32 – 749
The conversion has the following limitations:
Data Conversion result
MIDI output setting 
for MIDI tracksIf the output information stored in the original Song 
doesn’t match the current outputs, a “Pending Connec-
tions” dialog will appear, allowing you to remap each MIDI 
output in the Song to a new output.
MIDI track play parameters 
(Inspector settings)Only the volume and transpose settings are included; the 
other parameters (velocity, compression, length and pan) 
are ignored.
MIDI part play parameters 
(Inspector settings)All settings are included, except transpose.
Group tracks Removed.
Style tracks Removed.
Chord tracks Removed.
Drum tracks Converted to MIDI tracks with drum maps. MIDI output 
settings for individual drum sounds will be ignored.
Solo/Mute status of tracks Ignored.
MIDI “effect” devices, such 
as the arpeggiator and IPSRemoved.
Window layouts Ignored.
Key command settings Ignored.
Grooves Ignored.
MIDI Mixermaps Removed.
Dynamic events in audio 
parts (including M-points)Ignored.
Automation The VST channel automation is included, but limited to 
volume, pan and EQ data. Plug-in automation and auto-
mation for DSP Factory settings are ignored.
Left/right locator positions 
and cycle statusIgnored.
Sync settings and status Ignored.
Master track hitpoints Removed.
VST Group channels Removed. 
						

							CUBASE SX/SL32 – 750 File handling
• It’s also possible to import Songs created in version 3.7x of Cubase for 
Windows.
However, this will only include the basic audio and MIDI data, ignoring most of the set-
tings.
Import Cubase Arrangement
As mentioned above, a Song in previous versions of Cubase could 
contain one or several Arrangements. These contained all the part and 
event data along with file references, but without mixer settings and 
similar, which were global to all Arrangements in the Song. Arrange-
ments could be saved as separate files, with the extension “.arr”.
When you import a Cubase Arrangement into Cubase SX/SL, it will be 
converted to a project, just as when importing a Song. The same limita-
tions apply.
Import Cubase Part
Just as in Cubase SX/SL, previous Cubase versions used parts as 
containers for MIDI or audio events. These could be saved as separate 
files with the extension “.prt”. When you import a part file, the following 
happens:
• A new track is created, with the name of the part.
That is, the name of the part when it was saved in Cubase, not (necessarily) the file 
name.
• The part appears as a Cubase SX/SL part, at the left locator position.
• If the imported part was an audio part, the necessary clips and file references 
are added to the Pool.
Note that none of these file formats contain any actual audio data. Just 
as with Cubase SX/SL projects, the files only contain references to au-
dio files. This means that you need access to the referenced audio files 
as well, to properly import Songs, Arrangements or Parts with audio.
Multiple audio tracks routed 
to the same audio channelWill be replaced by separate audio tracks (with separate 
channels in the mixer). This is because in Cubase SX/SL 
there is always one channel per track.
Solo/Mute status of VST 
channelsIgnored. Data Conversion result