Steinberg Nuendo 4 Manual

							491
File handling
Importing audio
ÖFor exporting Audio, see the chapter “Export Audio 
Mixdown” on page 437.
ÖFor the option “Replace Audio in Video File”, see “Re-
placing the audio in a video file” on page 474.
Importing audio files
For information on audio file import preferences, please 
see “Audio file import options” on page 41. For informa-
tion on import into the Pool and import options, see “Im-
port Medium…” on page 306.
Importing audio CD tracks
You can import audio from audio CDs into Nuendo 
projects in two ways:
To import the CD tracks directly into project tracks, 
choose the “Audio CD…” option from the Import sub-
menu on the File menu.
The imported audio CD track(s) will be inserted on the selected audio 
track(s) at the project cursor position.
To import the CD tracks into the Pool, select “Import 
Audio CD” from the Media menu.
This might be the preferred method if you want to import several CD 
tracks in one go. For more information, see “Importing audio CD tracks” 
on page 308.
Selecting one of the Import Audio CD menu items brings 
up the following dialog:
To import one or more tracks, proceed as follows:
1.If you have more than one CD drive, select the correct 
one from the Drives pop-up menu top left.
On opening the CD, the program tries to retrieve the track names from 
CDDB (a CD database). If no connection to CDDB can be established 
or the CD track names are not found, you can manually change the ge-
neric track name in the Default Name field, see below.
2.Activate the “Secure Mode” option, if you want to use 
a Secure Read mode.
Activate this if you encounter problems when trying to import an audio 
CD. Error checking and correction will be done during the process. Note 
that this mode will take more time.
3.In the Windows version, select the data transfer speed 
from the Speed pop-up menu.
While you normally want to use the fastest possible speed, you may have 
to select a slower speed for flawless audio extraction.
4.Activate the Copy checkbox for every audio file you 
want to import.
You can also select a copy section for every file, see below. 
						

							492
File handling
5.Click on Copy to generate a local copy of the audio 
file(s) or section(s).
The copied files are listed at the bottom of the dialog. By default, imported 
a u d i o C D  t rac k s  w i ll  b e  s t ore d  a s  W av e  f il e s  (W i n d o w s )  or A I F F  f il e s  ( Ma c )  
in the Audio folder of the current project. To change the folder, click Folder 
and select another one from the dialog. During copying, the button is la-
beled “Stop”; click it to stop the process.
6.Click OK to import the copied audio files into the 
project, or click Cancel to stop the import and discard the 
copied files.
If you import more than one audio file into project tracks, 
a dialog opens in which you have to choose whether to in-
sert the tracks on one track or on different ones. 
The new track(s) are displayed in the Project window. New audio clips 
are created and added to the Pool.
The columns in the “Import from Audio CD” dialog have 
the following functionality:
By default, the complete tracks are selected. If you want to copy and import a section of an audio CD 
track only, select the track in the list and specify the start 
and end of the selection to be copied by dragging the 
handles in the copy selection ruler.
Use the start and end audition buttons to fine tune the selection bound-
aries.
ÖNote that you can import sections of several audio CD 
tracks by selecting them in turn and adjusting the selec-
tion. The start and end settings for each track will be dis-
played in the list.
You can audition the selected audio CD track by click-
ing the Play button.
The track will be played back from selection start to selection end (or un-
til you click the Stop button). 
The arrow up/down buttons allow you to audition the 
start and end of the selection only.
The arrow down button will play a short snippet beginning at the start of 
the selection, while the arrow up button will play a snippet starting just 
before the end of the selection.
In case no connection to CDDB could be established or 
no CD track names were found, you can change the ge-
neric audio file name in the Default Name field.
The imported audio files be will be named accordingly, i. e.  01 etc.
ÖNote that if there is a track name for a specific audio 
CD track in the list, the corresponding audio file will use 
that name instead.
To open the CD drive, click on the Eject button at the 
top of the dialog. 
Column Description
Copy Activate the checkbox in this column for the track you 
want to copy/import. To activate more than one check-
box, click and drag over the checkboxes (or press [Ctrl]/
[Command] or [Shift] and click).
# Number of track.
CD Track When you import an audio CD track, the file will be 
named according to the name in this column. The names 
are pulled automatically from CDDB, if possible. You can 
rename a track by clicking in the Track column and typing 
a new name. You can also apply a generic name to all au-
dio CD tracks, if no name was available in CDDB.
Length The length of the audio CD track in minutes and seconds.
Size The file size of the audio CD track in MegaBytes.
Copy Start You can copy a section of a track if you like. This indi-
cates the start of the section to be copied in the track. By 
default, this is set to the start of the track (0.000) but you 
can adjust this on the copy selection ruler (see below).
Copy End Indicates the end of the section to be copied in the track. 
By default, this is set to the end of the track but you can 
adjust this on the copy selection ruler (see below).
Play
StopPlay start of selection
Play end of selection
Start of selection handle
End of selection handle 
						

							493
File handling
Importing Audio from Video files
While you can automatically extract the audio when im-
porting a video file (see “Extracting audio from a video file” 
on page 472), it is also possible to import the audio from a 
video file without importing the video itself:
1.Pull down the File menu and select “Audio from Video 
File…” from the Import submenu.
2.In the file dialog that opens, locate and select the 
video file and click Open.
The audio in the selected video file is extracted and converted to a Wave 
file in the project’s Audio folder.
A new audio clip is created and added to the Pool. In the 
Project Window, an event referencing the audio file will be 
inserted on the selected track at the project Cursor posi-
tion. If no track was selected, a new track will be created.
This works just like when importing regular audio files.
ÖFor importing video files, see “Importing a video file” 
on page 470.
Importing ReCycle files
ReCycle by Propellerhead Software is a program designed 
especially for working with sampled loops. By “slicing” a 
loop and making separate samples of each beat, ReCycle 
makes it possible to match the tempo of a loop and edit the 
loop as if it was built of individual sounds. Nuendo can im-
port two file types created by ReCycle:
 REX files (export file format of the first versions of ReCycle, 
extension “.rex”).
 REX 2 files (file format of ReCycle 2.0 and later, extension 
“.rx2”).
Proceed as follows:
1.Select an audio track and move the project cursor to 
where you want the imported file to start.
You probably want to import REX files to tempo based audio tracks, since 
this will allow you to change the tempo later on (having the imported REX 
file automatically adjust).
2.Select “Audio File…” from the Import submenu on the 
File menu.
3.Select REX files or REX 2 files with the file type pop-
up menu in the file dialog.4.Locate and select the file and click Open.
The file is imported and automatically adjusted to the current Nuendo 
tempo. 
Unlike a regular audio file, the imported REX file will con-
sist of several events, one for each “slice” in the loop. The 
events will automatically be placed in an audio part on the 
selected track and positioned so that the original internal 
timing of the loop is preserved.
5.If you now open the part in the Audio Part Editor, you 
can edit each slice separately by muting, moving and re-
sizing events, adding effects and processing, etc.
You can also adjust the tempo and have the REX file automatically follow 
(provided that its track is tempo based).
ÖYou can achieve similar results by using Nuendo’s 
own loop slicing features, see “Working with hitpoints and 
slices” on page 278.
Importing compressed audio files
Nuendo can import (and export, see “Mixing down to an 
audio file” on page 438) 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, Nuendo will 
create a copy of the file and convert this to Wave format 
(Windows) or AIFF format (Mac OS X) before importing 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 resulting Wave/AIFF file will be several times 
larger than the original compressed file. 
						

							494
File handling
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. 
Nuendo can read two types of audio MPEG files: MPEG 
Layer 2 (*.mp2) and MPEG Layer 3 (*.mp3). Currently, 
mp3 is the most common of these formats, while the mp2 
format is mostly used in broadcast applications.
Ogg Vorbis files
Ogg Vorbis is a relatively new format that is open and 
patent-free and offers very small audio files maintaining 
comparatively high audio quality. Ogg Vorbis files have the 
extension “.ogg”.
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 OMF files
Open Media Framework Interchange (OMFI) is a platform 
independent file format intended for transfer of digital me-
dia between different applications. Nuendo can import 
and export OMF files (file extension “.omf”), allowing you 
to use Nuendo in conjunction with other audio and video 
applications.
Exporting OMF files
You can only export stereo files in OMF format.
1.Pull down the File menu and open the Export submenu. 
2.On the submenu, select “OMF…”.
The Export Options dialog opens:
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”.
When referencing media files (see below), you can set 
the referenced output path by entering it in the “Media 
Destination Path” field or by browsing the file dialog.
All file references will be set to this path. You can create references to 
media destinations that don’t exist on the system you are currently work-
ing with, making it easy to prepare files for use in projects on another 
system or in a network environment.
4.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 sub-directory in the ex-
port destination folder. To specify a different location for the copied files, 
use the “Media Destination Path” field.
5.If you want to copy only the portions of audio files that 
are used in the project, select “Consolidate Events” option. 
You can also define handle lengths in milliseconds to include audio out-
side each event boundary for fine tuning later. If you do not have any han-
dles when consolidating audio files, you will not be able to adjust fades 
or edit points when the project is imported in another application.
6.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. 
						

							495
File handling
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 Ref-
erences”, the file will be small, but the referenced audio files must be 
available for the receiving application.
7.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”, respectively.
8.Specify a sample size (resolution) for the exported files 
(or use the current project settings).
9.If you activate “Quantize Events to Frames”, the event 
positions in the exported file will be moved to exact frames.
10.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.Pull down the File menu and open the Import submenu.
2.On the submenu, select “OMF…”.
3.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 should be 
created for the file or not.
If you select “No”, the OMF file will be imported into the current project.
4.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 by clicking on Cre-
ate and entering a name in the dialog.
5.The Import options dialog opens, allowing you to 
choose a track for the import.
Activating the “Import all media” 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.
If the OMF file contains Video Event information, you are 
asked whether you want to create Markers at the start po-
sition 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 AAF files
The Advanced Authoring Format (AAF) is a multimedia file 
format used to exchange digital media and meta data be-
tween different systems and applications across multiple 
platforms. Designed by the top media software compa-
nies, this format will help media creators by allowing them 
to exchange projects between applications without losing 
valuable meta data such as fades, automation and pro-
cessing information.
Exporting AAF files
1.Select “AAF…” from the Export submenu on the File 
menu.
The Export Options dialog for AAF files. 
						

							496
File handling
2.You can choose which tracks will be exported from 
your project by clicking in the export column for each track 
name in the list.
A check mark will appear next to each track that will be exported. You 
may also click the “Select All” button to select every track in the project 
for export.
3.If you wish to only export the portion of project that is 
between the left and right locators, check the box marked 
“From Left to Right Locator.”
If an event crosses over the left or right locator, it will be trimmed in the 
AAF file to the point of the locator. Only the portions of events that lie 
within the boundaries of the locators will be included in the exported file.
4.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 sub-directory in the ex-
port destination folder. To specify a different location for the copied files, 
use the Media Destination Path field.
5.If you want to copy only the portions of audio files that 
are used in the project, select the “Consolidate Events” 
option. 
You can also define handle lengths in milliseconds to include audio out-
side each event boundary for fine-tuning later. 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.
ÖEven when selecting neither of the above two options, 
you can still enter a media destination path.
All file references will be set to this path. You can create references to 
media destinations that don’t exist on the system you are currently work-
ing with, making it easy to prepare files for use in projects on another 
system or in an network environment.
6.In the Options section, you have the choice of export-
ing all data to one file or to create media references to files 
from within the AAF file.
Exporting only one file makes transfers simpler, but, at the time of writing 
of this manual, certain applications cannot handle single AAF files. 
Check with each software manufacturer for up-to-date information re-
garding AAF support in other applications.
7.You can specify the Sample Size by using the pop-up 
menu. 
This defaults to keeping the same setting as the project.
8.You can quantize events to frame boundaries by acti-
vating the last option.
Quantizing events to frame boundaries is sometimes necessary when ex-
porting projects to video workstations that limit the accuracy of edits to the 
frame. Any events that begin or end not on a frame boundary can exhibit 
odd behavior or be moved when imported into a workstation of this type.
Importing AAF files
1.Select “AAF…” from the Import submenu on the File 
menu.
2.Once you have selected a valid AAF file, Nuendo will 
ask you if you wish to create a new project. Choosing Yes 
will import tracks into a new project.
3.Select a directory or create one for the new project. 
If you choose not to create a new project, the imported tracks will be 
added to the currently active project.
4.In the dialog that opens, select the tracks you wish to 
import by clicking in the Import column next to each track.
You can also click the Select All button to import all tracks in the AAF file.
5.Click OK.
The import process will begin. Depending on the size of the imported 
project and if the files are embedded or referenced, the import process 
may take a while.
Exporting and importing AES31 files
The AES31 standard is an open file interchange format, de-
veloped by the Audio Engineering Society as a means of 
overcoming format incompatibility issues between different 
audio hardware and software. It can be used for transferring 
projects via disk or network from one workstation to an-
other, retaining time positions of events, fades, etc.
AES31 uses the widely used Microsoft FAT32 file system 
with Broadcast Wave as the default audio file format. This 
means that an AES31 file can be transferred to and used 
with any digital audio workstation that supports AES31, 
regardless of the type of hardware and software used, as 
long as the workstation can read the FAT32 file system 
and Broadcast Wave files (or regular wave files).
Exporting AES31 files
1.Select “AES31…” from the Export submenu on the 
File menu.
2.Select a name and location for the new file and click 
Save.
The exported file will contain all Audio Track data, including audio file refer-
ences. If any of the audio events in your project has real-time fades (as set 
up with the fade handles for the events), these will automatically be con-
verted to fade audio files and stored in a fades folder next to the AES31 
file. 
						

							497
File handling
The following will not be included in the resulting AES file:
 Any mixer settings or automation made in Nuendo. 

The saved file will be an xml file (but with the extension 
“.adl”, for audio decision list) – this means you can open it 
in any text editor to check file references etc.
Importing AES31 files
1.Select “AES31…” from the Import submenu on the 
File menu.
2.Navigate to the location of the AES31 file (extension 
“.adl”), select it and click Open.
You are prompted to select or create a project folder for the new project.
3.After specifying the name and location of the project 
folder, the new project opens containing all the audio 
tracks and events stored in the AES31 file.
Exporting and importing OpenTL files
OpenTL is a file exchange format originally developed for 
Tascam hard disk recording systems. OpenTL facilities 
also exist in a variety of DAWs, making Nuendo project 
transfer reliable and solid. For example, a common use of 
OpenTL is to convert hassle free between Nuendo and 
Pro Tools. If you import or export an OpenTL file to/from 
Nuendo, the resulting project will contain all audio files, 
edits, and track names made in the Tascam device or 
DAW, with all events positioned sample accurately on the 
time line.
OpenTL implementation in Tascam® MMR-8, 
MMP-16 and MX-2424
All three Tascam devices work with either two types of 
disk volume formats: FAT32 (Windows standard) or 
HFS+ (Mac OS standard). For proper Nuendo compati-
bility it is necessary that each and every MMR-8/MMP-16 
be running OS v5.03 and MX-2424 v3.12. A number of 
crucial OpenTL updates only appear in these machine op-
erating systems, and only this setup can assure reliable 
Nuendo exchange.Audio file formats are volume type dependent: for FAT32 
this is BWF (*.wav) and for HFS+ this is SDII. OpenTL 
files can only be transferred within file systems of the 
same format which means that it is not possible to import 
an OpenTL project exported from Mac (HFS+) into a 
Windows system (FAT32) or vice versa, unless you use a 
conversion utility (e. g. MM-EDL).
Nuendo for Windows supports OpenTL FAT32/BWF. 
Nuendo for Mac OS X supports OpenTL HFS+/SDII as 
well as FAT32/BWF. MMR-8, MMP-16, and MX-2424 
support OpenTL projects sourcing or targeting Nuendo 
PC with up to 999 mono tracks.
Exporting OpenTL files
First, make sure all audio files (in the Pool) and tracks (in 
the Project window) in the project are in mono (split ste-
reo tracks and stereo interleaved audio files to dual mono) 
and all 16-bit or all 24-bit. The OpenTL specification does 
not include support for 32-bit audio files. If the Pool con-
tains 32-bit audio files, these will not be exported. Make 
sure all referenced audio files are located on the drive to 
which you want to export the OpenTL file.
1.Select “OpenTL…” from the Export submenu on the 
File menu.
In the dialog that opens, activate the “Copy Media” or the “Consolidate 
Events” option to guarantee that all audio is exported. Locate the target 
hotswap FAT32 disk, select the appropriate project folder and click Open.
2.Select a name and location for the new file and click 
Save.
The exported file will contain all audio track data, including file references, 
clip based volume automation, fade-in, fade-out, and crossfades. 
3.Now you can mount the carrier in the Tascam device 
and load the project.
The following will not be included in the resulting OpenTL 
EDL file: 
 Any real-time mixing, EQ, effects settings, breakpoint automa-
tion tracks
 MIDI tracks made in Nuendo
!When exporting OpenTL files on PC, do not change 
the DF or NDF frame notation after you have set the 
project start time. Make sure that all audio files in the 
Pool have the same sample rate, bit depth, and that 
all are set to Broadcast Wave file type. 
						

							498
File handling
The following is a basic OpenTL specification description:
 Maximum number of mono tracks: 999
 Supported samplerates (Hz): 44056, 44100, 44144, 47952, 
48000, 48048, 42294, 42336, 45938, 45983, 46034, 
46080, 50000, 50050, 88200, 96000
 Bit depth: 16, 24
 Audio file types: BWF (Broadcast Wave format), WAVE 
(Standard Wave), SDII (Sound Designer II)
 Volume formats: FAT32, NTFS, HFS+
 Automation support: clip based volume, breakpoint volume 
and mute
 Fade support: fade in, fade out, and cross fade
 Frame rates (Fps): 24/24, 23.976/24, 24.975/25, 25/25, 
29.97/DF, 29.97/NDF, 30/DF, 30/NDF 
Importing OpenTL files
1.Select “OpenTL…” from the Import submenu on the 
File menu.
2.Navigate to the location of the OpenTL file, select it 
and click Open.
3.You are prompted to select or create a project folder 
for the new project.
After specifying the name and location of the project folder, the new 
project opens containing all the audio files stored in the OpenTL file and 
their associated edits. Save the imported file as a Nuendo project. 
4.Open the Pool, and select “Prepare Archive…” from 
the Pool context menu. 
This will copy any necessary external audio files into the local Nuendo 
project directory. 
5.Select the Save option from the File menu. 
Importing XSend projects from 
Liquid
For Liquid users, XSend provides a means to export a Liq-
uid sequence directly to a Nuendo workstation either on 
the same machine, over a network or via portable media 
such as DVD-R.
The XSend options and features are available only if 
XSend is installed on your computer. You can either install 
XSend during the Nuendo installation process, or at a 
later point in time using the XSend installer supplied on 
the Nuendo program DVD. Also, make sure the XSend 
plug-in is activated in the Plug-in Information window.Proceed as follows to import XSend files:
1.You must designate the XSend Incoming folder by se-
lecting the XSend preferences from the Nuendo File menu.
A dialog opens, allowing you to browse your system to select a folder 
where exported Liquid projects will be stored.
2.Export the Liquid project to the Nuendo system.
This can be done directly over a network if the two systems are con-
nected by one. No file sharing is needed. All file transfers are handled by 
XSend. Refer to the Liquid system’s documentation for more information 
on how to do this. You may also export the sequence to portable media 
such as DVD-R or CD-R discs for transfer when no network is available.
3.On the File menu–Import submenu, select “XSend…”.
Navigate to the exported Liquid sequence which will be an .XSD file type.
4.You will be asked if you wish to create a new project.
Choose Yes if you want to import the XSend sequence into a blank 
project. If you choose No, the imported sequence will be appended to 
the currently active project. The new audio tracks are displayed below 
the lowest track or channel in the project. In either case, both audio and 
video files can be included in the XSend sequence, providing a conve-
nient means to receive entire projects from Liquid users.
Exporting and importing standard 
MIDI files
Nuendo 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 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 Ex-
port submenu. A regular file dialog opens, allowing you to 
specify a location and name for the file. 
						

							499
File handling
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 
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 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!
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 358.
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.
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.
Export 
AutomationIf this is activated, recorded automation (see “Introduc-
tion” on page 214) is converted to MIDI controller events 
and included in the MIDI file. This also includes automa-
tion recorded with the MIDIControl plug-in. This is de-
scribed in the chapter “MIDI Effects” of the separate 
manual “Nuendo Expansion Kit – Cubase Music Tools for 
Nuendo 4”.
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 “Us-
ing markers” on page 109) 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 
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. For more information about the 
Delay option, see “Basic track settings” on page 344. Option Description 
						

							500
File handling
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:
When you import a MIDI file into the project, the Tempo 
track will be adjusted according to the Tempo track in the 
MIDI file.
It is also possible to import a MIDI file from disk by drag-
ging and dropping it from the Windows Explorer or the 
Mac OS Finder into the Nuendo Project window. The Im-
port Options apply as well.Exporting and importing MIDI loops
Nuendo 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 189.
Exporting and importing tracks
You can export Nuendo tracks (Audio, FX, Group, Instru-
ment, MIDI and Video) as track archives for import into 
other Nuendo projects. All the information associated with 
the tracks will be exported (mixer channel settings, auto-
mation tracks, parts and events etc.). If you select the op-
tion “Copy” (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 “Track Pre-
sets” on page 327.
Exporting tracks as track archive
1.Select the tracks you wish to export.
2.Pull down the File menu and open the Export submenu. 
3.On the submenu, select “Selected Tracks…”.
4.You are prompted to choose between two options:
Click Copy to include copies of the media files in the ex-
port.
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 me-
dia subfolder, which will contain any associated audio or video files.
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).
5.Click OK to save the respective track archive type.
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 Marker If this is activated, Standard MIDI File Markers in the file 
will be imported and converted to Nuendo 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 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.
Auto Dissolve 
Format 0If 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.
Import to Instru-
ment tracksIf this is activated and you drag a MIDI file into the 
project, an Instrument track will be created instead of a 
MIDI track. Furthermore, the program will load the corre-
sponding track preset for the instrument track (based on 
the program change events included in the MIDI file).