Steinberg Cubase Le 4 Manual

							241
File handling
Importing compressed audio files
Cubase LE can import several common audio compres-
sion formats. The procedure is the same as when import-
ing any non-compressed audio file, with one important 
thing to note:
When you import a compressed audio file, Cubase LE 
will create a copy of the file and convert this to Wave for-
mat (Windows) or AIFF format (Mac OS X) before import-
ing it. The original compressed file will not be used in the 
project.
The imported file will be placed in the designated project 
Audio folder.
The following file types are supported:
MPEG audio files
MPEG, which stands for Moving Picture Experts Group, is 
the name of a family of standards used for coding audio-
visual information (e. g. movies, video, music) in a digital 
compressed format. 
Cubase LE can read two types of audio MPEG files: 
MPEG Layer 2 (*.mp2) and MPEG Layer 3 (*.mp3). Cur-
rently, mp3 is the most common of these formats, while 
the mp2 format is mostly used in broadcast applications.
Windows Media Audio files (Windows only)
Windows Media Audio is an audio format developed by 
Microsoft Inc. Due to advanced audio compression algo-
rithms, Windows Media Audio files can be made very 
small, maintaining good audio quality. The files have the 
extension “.wma”.
Exporting and importing MIDI files
Cubase LE 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 tracks, 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 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, allow-
ing 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 (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 Op-
tions dialog to proceed.
The dialog contains the following options:
!The resulting Wave/AIFF file will be several times 
larger than the original compressed file.
Option Description
Export Inspector 
PatchIf 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/PanIf this is activated, Volume and Pan settings made in the 
Inspector are included as MIDI Volume and Pan events in 
the MIDI file. 
						

							242
File handling
ÖThe MIDI file will include the Tempo track.
ÖInspector settings other than those specified in the Ex-
port options are not included in the MIDI file!
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.If there is already an open project, a dialog opens in 
which you can 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 
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 by clicking on Create 
and entering a name in the dialog.
The MIDI file is imported. The result depends on the con-
tents of the MIDI file and the Import Options settings in the 
Preferences (MIDI–MIDI File page). The Import Options 
are as follows:
As mentioned in “Exporting MIDI files” on page 241, 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 func-
tion on the MIDI menu to distribute the events onto different tracks with 
different MIDI Channels (see “Dissolving parts into separate channels” 
on page 160).
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.
Export 
AutomationIf this is activated, recorded automation (see “Back-
ground” on page 91) is converted to MIDI controller 
events and included in the MIDI file.
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 
don’t 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 
ResolutionYou 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 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 should 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. 
Export 
includes DelayIf this is activated, the delay of the MIDI track will be in-
cluded in the MIDI file. Option Description
Option Description
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.
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 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 cur-
rent project, tempo track data in the MIDI file is ignored. 
The imported MIDI file will play according to the current 
Tempo track in the project.
!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 Cubase LE Project 
window. The Import Options apply as well. 
						

							27
Customizing 
						

							244
Customizing
Background
The user can customize the appearance and functionality 
of Cubase LE in various ways.
User configurable items described in this chapter are:
Setup dialogs
Several parts of the user interface (toolbars, Transport panel, Inspector, 
info lines and channel settings windows) provide a Setup dialog, where 
the user can configure which items of the respective window area or 
panel are to be shown or hidden and where they should be located.
Appearance
The general look of the program can be adjusted – see “Appearance” on 
page 245.
Track and event colors
You can adjust which colors should be used – see “Applying track and 
event colors” on page 245.
This chapter also contains a section describing where 
your preferences and settings are stored (see “Where are 
the settings stored?” on page 248), to help you transfer 
your customized settings to another computer.
The Setup dialogs
The following elements in the program feature Setup dia-
logs and context menus:
 the Transport panel
 the info lines
 the Channel Settings windows
 the toolbars 
 the Inspector
Customizing via 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. For channel settings windows, these options are 
found in the Customize View submenu on the context 
menu. On this menu, you can activate or deactivate ele-
ments as desired.
The following general options are available in 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).If presets are available, they can be selected from the 
lower half of the menu. 
The info line and Inspector setup context menus. In the Inspector setup 
context menu, the available options depend on the track type.
The channel settings setup context menu for a MIDI track. The available 
options depend on the track type.
Customizing via the Setup dialog
If you select “Setup…” from the setup context menus, the 
Setup dialog opens. Here you can:
choose which elements (“items”) should be visible or hid-
den for the Transport panel, the toolbars or the Inspector.
configure where the items should be placed.
save and recall presets, i. e. different configurations.
The Setup dialog, e. g. for the Transport panel. 
						

							245
Customizing
The dialog is divided into two columns. The left column 
displays the currently visible items and the right column 
displays the currently hidden items.
You can change the current show/hide status by select-
ing items in one column and then using the arrow buttons 
in the middle of the dialog to move them to the opposite 
column.
Changes are applied directly.
By selecting items in the “Visible Items” column and us-
ing the Move Up and Move Down buttons, you can change 
the position of the selected item(s).
Changes are applied directly. To undo all changes and revert back to the 
standard layout, you can select “Default” from the setup context menu.
A “customized” Transport panel.
If you click the Save button (disk icon) in the Presets 
section, a text field opens, allowing you to name the cur-
rent configuration and to save it as a preset
The saved setting will be displayed in the Presets field.
To remove a preset, select it and click the trash icon.
Saved configurations are available for selection from the 
Presets pop-up in the Setup dialog or directly from the 
setup context menu.
Appearance
In the Preferences dialog you will find a page called Ap-
pearance. The following settings are available:
Basic Appearance Scheme.
By selecting an option from this pop-up menu you can adjust the general 
look of the program. After selecting an Appearance Scheme and clicking 
Apply or OK, you need to restart the program for the changes to take ef-
fect.
Brightness/Intensity sliders.
These sliders allow you to fine-tune the brightness and contrast in vari-
ous areas in the program. Changes take effect when you click Apply or 
OK.
Applying track and event colors
You can use color scheming for easier overview of tracks 
and events in the event display of the Project window. Ap-
plying colors is divided into two areas; track and event 
colors.
A track color is shown and can be edited in the Inspec-
tor, the Track list, and the corresponding channel in the 
Mixer. It is furthermore displayed in all parts and events for 
the track in the event display.
Track colors can be switched on and off globally.
Event colors are shown for parts and events in the event 
display and are independent from the track colors.
ÖAn applied event color “overrides” the track color, if 
both are used.
The palette of the color bar can be customized, see “The 
Event Colors dialog” on page 247.
Track colors
Applying track colors manually
To activate track colors, proceed as follows:
1.Click the Show/Hide Track Colors button at the top of 
the Track list.
This brings up the track color selector in the Inspector, the 
Track list and in the Mixer.
2.To bring up the color palette, click the track color se-
lector.
Click the arrow in the track name title bar or…
…click the color strip in the Track list. 
						

							246
Customizing In the Mixer, click the track color selector below the channel name.
3.Select a color from the color bar.
The chosen track color is now reflected in the Inspector title bar and the 
color strip as well as in the Mixer and any parts or events on the selected 
track.
Applying track colors automatically
In the Preferences (Editing–Project & Mixer page) you can 
find the option “Auto Track Color Mode”.
This offers you several options for automatically assigning 
colors to tracks that are added to the project.
Coloring parts and events
There are two ways to color parts and events in the 
Project window:
Using the color selector
1.Select parts or events.
2.Choose a color from the color selector in the toolbar.
Using the color tool
1.Select the color tool (the paint bucket icon). 
2.Click the small strip below it to bring up the color pal-
ette.
3.Choose a color. 
4.Click on a part/event to assign the color. 
The color is applied to all selected parts/events and over-
rides the track color (if used).
If you press [Ctrl]/[Command] and click on a part/event 
with the color tool, the color palette is displayed and you 
can choose the desired color for an event.
If you press [Alt]/[Option], the color tool cursor be-
comes a pipette, which can be used to select a color by 
clicking on a part/event.
Customizing the event background
On the Event Display page in the Preferences, you can 
find the option “Colorize Event Background”.
Option Effect
Use Default 
Event ColorThe default color (gray) is assigned. 
Use Previous 
Track ColorUses the color of the track above the new one (i. e. the 
track that is selected when you add a new track).
Use Previous 
Track Color +1Uses the color next to the color of the track above the 
new one (+1 refers to the color number in the palette).
Use Last 
Applied ColorThe last manually assigned color is used. 
Use Random 
Track ColorTrack colors are assigned randomly. 
						

							247
Customizing
This option affects the display of events in the project win-
dow.
When this is activated, the background of the events 
and parts in the event display will be shown in the se-
lected color.
When this is deactivated, the event “content”, i.e. MIDI 
events, audio waveforms, etc. will be displayed in the se-
lected color and the event background will be displayed in 
gray. 
The Event Colors dialog
You can open the Event Colors dialog in two ways: 
Double-click the small strip below the color tool. 
Open the Color pop-up menu on the toolbar and select 
“Select Colors…”.
In the Event Colors dialog, you can fully customize the 
color palette, apart from the default color (gray).To add new colors to the color palette, proceed as follows:
1.Click the Insert New Color button in the Event Colors 
section to add a new color.
A new color icon and color name are added to the Event Colors section.
2.Click the color field next to the name field to activate 
the new color for editing.
3.In the Standard Colors section, choose a standard 
color. You can modify the selected color by:
 Moving to another point in the color circle.
 Moving the handle in the color meter.
 Manually entering the values for red, green and blue and hue, 
saturation and luminosity.
4.Click the Apply button in the Standard Colors section. 
The color setting is applied to the selected color item. 
You can edit every existing event color accordingly.
To delete an event color item, select it and click the Re-
move Selected Color button in the Event Colors section.
To increase or decrease the intensity and the brightness 
of all colors, use the corresponding buttons in the Event 
Colors section.
To save the current set as default, click the button “This 
set as default set” in the Event Colors section. Accord-
ingly, click the button “Use default set” to the right to ap-
ply the saved default set.
To return to the standard setting of the palette in Cu-
base LE, click Reset.
Remove 
new colorIncrease/decrease in-
tensity for all colors This Set as 
Default Set Increase/decrease 
brightness for all colorsInsert
new color
Use Default 
Set 
						

							248
Customizing
Where are the settings stored?
As you have seen, there are a large number of ways in 
which you can customize Cubase LE. While some of the 
settings you make are stored in each project, others are 
stored in separate preference files.
If you need to transfer your projects to another computer 
(e. g. in another studio), you can bring all your settings 
along by copying the desired preference files and install-
ing them on the other computer.
ÖIt’s a good idea to make a backup copy of your prefer-
ence files once you have set things up the way you want!
This way, if another Cubase LE user wants to use his or her personal set-
tings when working on your computer, you can restore your own prefer-
ences afterwards.
Under Windows, preference files are stored in the 
folder “\Documents and Settings\\Applica-
tion Data\Steinberg\Cubase LE 4\”.
On the Start menu, you will find a shortcut to this folder for easy access.
Under Mac OS X, preference files are stored in the 
folder “Library/Preferences/Cubase LE 4/” under your 
home directory.
The full path would be: “/Users//Library/Preferences/
Cubase LE 4/”.
ÖRAMpresets.xml is saved when exiting the program. 
ÖProgram functions or configurations not used in the 
project will not be stored.
The table below shows the location and name of each 
preference file:
Setting Stored in
Current edit 
modifier keysEdit Modifiers.xml
Current key 
commandsKey Commands.xml
Current 
preferences Defaults.xml
Color setup saved in the project
Default Color 
setupDefaults.xml
Crossfade 
presets\Presets\RAMPresets.xml
Drum maps \DrumMaps as *.drm file
Installed MIDI 
devicesMidi Devices.bin
Key commands 
presets\Presets\KeyCommands\.xml
Logical Editor 
presets\Presets\Logical Edit\.xml
Mixer (or channel) 
settingssaved in the last active folder as *.vmx file (VST Mixer 
settings)
Mixer view 
presetsaved in project
Patch name 
scripts\Scripts\Patchnames\ as *.txt file
Port Input/
Output settingsPort Setup.xml
Quantize 
presets\Presets\RAMPresets.xml
Toolbar presets \Presets\RAMPresets.xml
Transport panel 
presets\Presets\RAMPresets.xml
Usage profile
logUsage Profile.xml (only saved if the corresponding 
option in the Preferences is activated)
User templates Under Programs\Steinberg\Cubase LE 4	emplates\
.cpr
VST connections 
presets\Presets\RAMPresets.xml
VST 3 plug-ins 
and instrumentsVstPlugInfo.xml
VST 2 plug-ins 
and instrumentsVst2xPlugins.xml
Not loadable 
VST2 plug-insVst2xBlacklist.xml
VST3 presets
(included in the 
program)In the application folder under 
\VST3 Presets\\
as *.vstpreset file
VST3 presets 
(user-defined, 
for all programs)Win: \Common files\VST3 Presets\\

Mac: Users//Library/Audio/Presets/
/
as *.vstpreset file
VST3 presets 
(public, for all pro-
grams)Win: \Documents and Settings\VST3 Pre-
sets\\
Mac: (Network)/Library/Audio/Presets//

as *.vstpreset file
Zoom presets \Presets\RAMPresets.xml Setting Stored in 
						

							28
Key commands 
						

							250
Key commands
Background
Introduction
Most of the main menus in Cubase LE have key command 
shortcuts for certain items on the menus. In addition, there 
are numerous other Cubase LE functions that can be per-
formed via key commands. These are all default settings. If 
you want, you can customize existing key commands to 
your liking, and also add commands for menu items and 
functions currently not assigned any.
How are key commands settings saved?
Every time you edit or add any key command assignment, 
this is stored as a global Cubase LE preference – not as 
part of a project. Hence, if you edit or add a key command 
assignment, any subsequent projects that you create or 
open will use these modified settings. However, the de-
fault settings can be restored at any time by selecting “Re-
set All” in the Key Commands dialog.
In addition, you can save key commands settings as a “key 
commands file”, which is stored separately and can be im-
ported into any project. This way you can quickly and easily 
recall customized settings, when moving projects between 
different computers, for example. The settings are saved in 
a file on disk with the windows extension “.xml”.
How to save key commands settings is described in the 
section “About key commands presets” on page 252.
Setting up key commands
The following is a description of how you set up key com-
mands and save them as presets for easy access.
Key commands settings are accessed and edited mainly 
in the Key Commands dialog. You can find some key com-
mand settings in the Preferences dialog as well, also ad-
dressed in this chapter.
Adding or modifying a key command
In the Key Commands dialog you will find all main menu 
items and a large number of other functions, arranged in a 
hierarchical way similar to that of the Windows Explorer 
and Mac OS Finder. The function categories are repre-
sented by a number of folders, each containing various 
menu items and functions. When you open a category 
folder by clicking the plus-sign beside it, the items and 
functions it contains are displayed with the currently as-
signed key commands.
To add a key command, proceed as follows:
1.Pull down the File menu and select “Key Commands…”.
The Key Commands dialog appears.
2.Use the list in the Commands column to navigate to 
the desired category.
3.Click the plus sign to open the category folder and 
display the items it contains.
Note that you can also click the “global” plus and minus signs in the top 
left corner to open and close all category folders at once.
!You can also assign tool modifier keys, i.e. keys that 
change the behavior of various tools when pressed. 
This is done in the Preferences dialog – see “Setting 
up tool modifier keys” on page 253.