Steinberg Cubase 7 User Manual

							691
File handlingExporting and importing OMF files (Cubase only)
3.If you want to create copies of all the media files, choose the “Copy Media” option.
By default, the copied audio files are placed in a subdirectory in the export 
destination folder. To specify a different location for the copied files, use the 
“Media Destination Path” field.
4.If you want to copy only the portions of audio files that are used in the project, 
activate “Consolidate Events”. 
You can also define handle lengths in milliseconds to include audio outside each 
event boundary for later fine tuning. If you do not have any handles when 
consolidating audio files, you will not be able to adjust fades or edit points when 
the project is imported in another application.
5.Select “1.0 File” or “2.0 File”, depending on which OMF version is supported by 
the application in which you plan to import the file.
•Select whether you want to include all audio data in the OMF file (“Export All to 
One File”) or use references only (“Export Media File References”).
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 include these in the OMF file, activate 
“Export Clip Based Volume”, “Use Fade Curves” and/or “Export Clip Names”.
7.Specify a sample size (resolution) 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 opens.
The exported OMF file will contain (or reference) all audio files that are played in the 
project (including fade and edit files). It will not include unused audio files referenced 
in the Pool, or any MIDI data. Video files are not included.
Importing OMF files
1.Open the File menu, open the Import submenu and select “OMF…”.
2.In the file dialog that opens, locate the OMF file and click Open.
•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 OMF file will be imported into the current project.
3.If you choose to create a new project, a file dialog opens in which you can select 
the project folder.
Select an existing project folder or create a new one.
4.The Import Options dialog opens, allowing you to choose a track for the import.
•Activating the “Import all media files” option allows you to import media that is not 
referenced by events.
•Activating the “Import Clip Gain as Automation” option imports volume automation 
and envelopes of the Volume Automation Track of each track. 
						

							692
File handlingExporting and importing standard MIDI files
•“Import at Timecode Position” will insert the elements contained in the OMF file at 
their original timecode positions.
This is useful when you want to position every imported element at its exact 
timecode position, i.
 e. as it was saved in the OMF file. This way, the elements will 
end up at their correct time positions even when Cubase uses a different frame 
rate than the OMF file. This is usually required in a picture-related context.
•“Import at Absolute Time” will insert the elements contained in the OMF file 
starting at the timecode position saved in the file and keeping the relative 
distances between the elements.
This is required when the relative positioning of the elements inside the OMF file 
needs to be maintained after importing it into the Cubase timeline (even if Cubase 
is set to a different frame rate than the OMF file). This is usually required in music 
contexts, where the timing between objects has highest priority.
•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 (or tracks are added to the existing project), 
containing the audio events of the imported OMF file.
 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 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 are included in the files (automation tracks, volume and pan settings, 
etc.). 
Exporting MIDI files
To export your MIDI tracks as a standard MIDI file, open the File menu and select 
“MIDI File…” from the Export 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, e.
 g. 
what is included in the file, its type and its resolution (see below for a description of 
the options).
You will also find most of these settings in the Preferences dialog (MIDI–MIDI File 
page). If you set these up in the Preferences dialog, you only need to click OK in the 
Export Options dialog to proceed. 
						

							693
File handlingExporting and importing standard MIDI files
The dialog contains the following options:
OptionDescription
Export Inspector 
PatchIf this is activated, the MIDI patch settings in the Inspector – 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/PanIf this is activated, Volume and Pan settings made in the Inspector are 
included as MIDI Volume and Pan events in the MIDI file.
Export AutomationIf this is activated, the automation data (as heard during playback) are 
converted to MIDI controller events and included in the MIDI file, see 
the chapter 
“Automation” on page 279. This also includes automation 
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 automation 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 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 InsertsIf this is activated and you are using MIDI modifiers or 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 additional, “echoing” notes at rhythmic 
intervals – these notes will be included in the MIDI file if the option is 
activated. 
Export SendsIf 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 MarkersIf this is activated, any markers you have added (see “Using markers” 
on page 169) will be included in the MIDI file as standard MIDI file 
marker events.
Export as Type 0If 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 ResolutionYou 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 precision 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 
RangeIf this is activated, only the range between the locators will be 
exported.  
						

							694
File handlingExporting and importing standard MIDI files
Ö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 473. 
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 contents of the MIDI file and the 
Import Options settings in the Preferences dialog (MIDI–MIDI File page). The Import 
Options are as follows:
Export includes 
DelayIf this is activated, the delay of the MIDI track will be included in the 
MIDI file. For more information about the Delay option, see 
“Basic 
track settings” on page 450.
Song name for 
Type 0You can use this text field to change the name of the MIDI file as 
displayed when loading this file in a keyboard.
Option Description
OptionDescription
Extract First PatchIf 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/PanIf this is activated, the first MIDI Volume and Pan events for each track 
are converted to Inspector settings for the track.
Import Controller 
as Automation 
TracksIf 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 
LocatorIf 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.
Import MarkersIf this is activated, standard MIDI file markers in the file will be 
imported and converted to Cubase 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 Master 
Track Events on 
MergeIf this is activated and you import a MIDI file into the current project, 
tempo and signature track data in the MIDI file are ignored. The 
imported MIDI file will play according to the current tempo and 
signature tracks in the project.
If this option is deactivated, the Tempo Track Editor will be adjusted 
according to the tempo information in the MIDI file. 
						

							695
File handlingExporting and importing MIDI loops
•It is also possible to import a MIDI file from disk by dragging and dropping it from 
the Windows Explorer or the Mac OS Finder into the Project window. The Import 
Options apply as well.
Support for the Yamaha XF data format
Cubase supports the Yamaha XF format. XF is an extension of the standard MIDI file 
format that allows you to save song-specific data with a MIDI file of type 0.
When importing a MIDI file containing XF data, this data is placed in parts on separate 
tracks called “XF Data”, “Chord Data”, or “SysEx Data”. You can edit such a part in 
the List Editor (e.
 g. to add or change lyrics).
Cubase can also export XF data as part of a MIDI file of type 0. If you do not want to 
export the XF data together with the MIDI data, mute or delete the tracks containing 
the XF data.
Exporting and importing MIDI loops
Cubase allows you to import MIDI loops (file extension “.midiloop”) and to save 
instrument parts as MIDI loops. MIDI loops are handy, as they contain not only MIDI 
notes and controllers, but also the associated VST instrument and instrument track 
preset settings.
How to import and export MIDI loops is described in detail in the chapter “VST 
instruments and instrument tracks” on page 252.
Auto Dissolve 
Format
 0
If this is activated and you import a MIDI file of type 0 into the project, 
the file will automatically be “dissolved”: For each embedded MIDI 
channel in the file, a separate track will be inserted in the Project 
window.
If this is deactivated, 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 also use the “Dissolve Part” 
function on the MIDI menu to distribute the events onto different 
tracks with different MIDI Channels at a later stage.
DestinationHere, you can specify what happens when you drag a MIDI file into 
the project:
- If you select the “MIDI Tracks” option, MIDI tracks are created for 
the imported file.
- If you select the “Instrument Tracks” option, instrument tracks are 
created for each MIDI channel in the MIDI file. Furthermore, the 
program automatically loads appropriate presets.
- If you select the “HALion Sonic SE multi-timbral” option, several MIDI 
tracks are created, each routed to a separate instance of HALion Sonic 
SE in the VST Instruments window and the appropriate presets are 
loaded.
Option Description
!Do not change the order of events within the XF data or the event data itself, unless 
you have a lot of experience with XF data. 
						

							696
File handlingExporting and importing track archives (Cubase only)
Exporting and importing track archives (Cubase only)
You can export Cubase tracks (audio, FX, group, instrument, MIDI, and video) as track 
archives for import into other Cubase (or Nuendo) projects. All the information 
associated with the tracks will be exported (channel settings, automation tracks, parts 
and events, etc.). If you select the “Copy” option (see below), 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 archives.
ÖFor creating track presets from tracks, see “Working with track presets” on page 422.
Exporting tracks as track archives
1.Select the tracks you wish to export.
2.Open the File menu, open the Export submenu and choose “Selected Tracks…”.
3.When exporting audio or video tracks, you are prompted to choose between two 
options:
•Click Copy to include copies of the media files in the export.
A file dialog opens in which you can choose an existing empty folder or create a 
new folder for saving the track archive (as XML file) and its media subfolder, which 
will contain any associated audio or video files. Click OK to save the track archive.
•Click Reference to include merely a reference to the files in the export.
A file dialog opens in which you can choose an existing folder for saving the track 
archive (as single XML file).
4.Enter a name for the track archive and click Save.
Importing tracks from a track archive
The Import Track Archive function lets you import tracks exported from another 
Cubase (or Nuendo) project.
ÖNote that the sample rates of the active project and the track archive have to match. If 
necessary, you have to convert the sample rate, see below. 
1.Open the File menu, open the Import submenu and select “Track Archive…”.
2.In the file dialog that opens, select the XML file and click Open.
The Import Options dialog opens.
In the Project Settings area, you can see a comparison between the settings of the track 
archive and the active project. 
						

							697
File handlingExporting and importing track archives (Cubase only)
3.Click in the Import column on the left to select the desired track(s) or click “Select 
All Tracks”.
A checkmark is shown for all selected tracks.
4.Choose which media files to use. 
•Select “Use Media Files From Archive” if you want to import the track without 
copying the media files into your project folder.
•Select “Copy Media To Project Folder” if you want to import the media files into 
your project folder.
For the “Perform Sample Rate Conversion” option, see below.
5.Click OK.
The tracks are imported, complete with all contents and settings.
Sample rate conversion on track archive import
A track archive may contain media files with a sample rate that is different from the 
sample rate of your currently active project. You can see the sample rate difference in 
the Project Settings area.
•To convert the sample rate of a track archive to the sample rate used in the active 
project on import, select the “Copy Media To Project Folder” option and then 
“Perform Sample Rate Conversion”.
ÖUnconverted files with another sample rate than the one used in the project will play 
back at the wrong speed and pitch. 
						

							698
Customizing
Background
The user can customize the appearance and functionality of Cubase in various ways.
User configurable items described in this chapter are:
•Workspaces
By storing different window combinations as workspaces, you can quickly switch 
between different working modes, see 
“Workspaces” on page 698.
•Setup dialogs
Several parts of the user interface (toolbars, Transport panel, Inspector, info lines 
and Channel Settings windows) provide a Setup dialog, where you can configure 
which items of the respective window area or panel are to be shown or hidden and 
where they are located, see 
“Using the Setup options” on page 700.
•Track list
The controls shown in the track list can be set for each track type, see 
“Customizing track controls” on page 702.
•Appearance
The general look of the program can be adjusted, see “Appearance” on page 704.
•Track and event colors
You can adjust which colors are used, see “Applying colors in the Project window” 
on page 706.
This chapter also contains a section describing where your preferences and settings 
are stored to help you transfer your customized settings to another computer, see 
“Where are the settings stored?” on page 709).
Workspaces
A configuration of Cubase windows is called a “workspace”. A workspace stores the 
size, position and content of all windows, allowing you to quickly switch between 
different working modes via the menu or by using key commands. For example, you 
may want as large a Project window as possible when you are editing, whereas you 
may want the MixConsole and effect windows open during mixdown. Workspaces are 
listed and managed on the Workspaces submenu of the Window menu. 
						

							699
CustomizingWo r k s p a c e s
Editing the active workspace
There is always one workspace active, even if you have not saved any. To make 
changes to the active workspace, you simply set up the windows as desired – 
including opening, closing, moving and sizing windows, and adjusting zoom and track 
height. The changes are automatically stored for the active workspace.
•To keep a workspace from being accidentally changed, select “Lock Active 
Workspace” from the Workspaces submenu.
A locked workspace will keep its original window settings. You may change the 
current window layout on the screen, but the next time you select the workspace 
again, the originally stored layout is recalled.
Creating a new workspace
1.Open the Window menu and open the Workspaces submenu.
2.Select “New Workspace”.
3.In the dialog that opens, enter a name for the workspace.
4.Click OK.
The workspace is stored and will appear on the submenu. It is now the active 
workspace.
5.Set up the windows you want to include in the new workspace.
This may include opening, moving and sizing windows, and adjusting zoom and 
track height.
ÖThe number of workspaces you can add is not limited. 
Activating a workspace
1.Open the Window menu and open the Workspaces submenu.
2.Select a workspace from the list on the submenu.
The windows are closed, opened, moved and/or resized according to the stored 
workspace.
•You can also activate workspaces by using the corresponding key commands, see 
“Key commands” on page 711. 
Organizing workspaces and presets
If you select “Organize…” from the Workspaces submenu, the Organize Workspaces 
dialog opens. 
						

							700
CustomizingUsing the Setup options
The list to the left shows the workspaces in the active project, while the list to the right 
shows the workspace presets. While workspaces are stored with each project, 
workspace presets can be stored globally, allowing you to set up a number of 
workspaces for use in any project. Workspace presets save the position and size of 
the main windows only – project-specific windows are not included.
•In the Workspaces list to the left, you can rename workspaces (by double-clicking 
and typing) and lock or unlock them.
•The arrow buttons between the two lists allow you to copy the selected workspace 
to a workspace preset, or vice versa.
•The buttons below each list let you add, remove, or activate workspaces or presets.
You can also activate a workspace or a preset by double-clicking in its number 
column.
•Normally, when you use key commands to activate workspaces, they relate to the 
order in the workspace list, e.
 g. the key command for “Workspace 1” selects the 
first workspace on the list and so on. However, if you activate the Use IDs 
checkbox, you can enter a number in the ID column for each workspace. 
This number will be used as reference when you are using key commands, so that 
the key command for “Workspace 1” recalls the workspace with ID 1.
•Workspace presets are not only saved globally, but also included in the project. If 
you open a project on a different system, by default the global presets stored on 
this system are shown in the list to the right. To see the presets included in your 
project, activate the “Show Project Presets” option.
•Activate the “Auto Instantiate Presets” option to convert all global workspace 
presets automatically into workspaces when you create a new project or open a 
project.
•To close the dialog, click the OK button.
Note that you can continue working in other windows with the Organize 
Workspaces dialog open.
Using the Setup options
You can customize the appearance of the following elements:
- Transport panel
- Info line
-Toolbars 
- Inspector
The setup context menus
If you right-click the Transport panel, the toolbars, the info lines, or the Inspector, the 
respective setup context menu opens.
The following general options are available on the setup context menus:
•“Show All” makes all items visible.
•“Default” resets the interface to the default setting.
•“Setup…” opens the Setup dialog, see below.