Steinberg Nuendo 3 Operation Manual

							NUENDO
File handling 29 – 651
Exporting and importing OpenTL files
OpenTL is a file exchange format originally developed for Tascam hard 
disk recording systems. OpenTL facilities also appear 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+ (MacOS standard). For 
proper Nuendo compatibility 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 operating sys-
tems, 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 trans-
ferred 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 conver-
sion 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 audio Pool) and tracks (in the 
Project window) in the project are in mono (split stereo 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 project pool contains 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. 
						

							NUENDO
29 – 652 File handling
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 au-
dio files in the project pool have the same sample rate, bit depth, and 
that all are set to Broadcast Wave file type.
1.Select “OpenTL...” from the Export submenu on the File menu.
In the dialog that appears, activate the “Copy Media” or the “Consolidate Events” op-
tion to guarantee that all audio is exported. Locate the target hotswap FAT32 disk, se-
lect 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 automation tracks
• MIDI tracks made in Nuendo
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
• Framerates (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. 
						

							NUENDO
File handling 29 – 653
3.You are now 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.  
						

							NUENDO
29 – 654 File handling
Importing XSend projects from Liquid
For Liquid users, XSend provides a means to export a Liquid se-
quence 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 in-
stalled on your computer. You can either install XSend during the Nu-
endo 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 dialog.
Proceed as follows to import XSend files:
1.You must designate the XSend Incoming folder by selecting the 
XSend preferences from the Nuendo File menu.
A dialog will appear allowing you to browse your system to select a folder where ex-
ported 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 connected by one. No 
file sharing is needed. All file transfers are handled by XSend. Refer to the Liquid sys-
tem’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 net-
work is available.
3.From the File menu’s Import submenu, choose “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 will appear below the lowest track or channel in the project. In ei-
ther case, both audio and video files can be included in the XSend sequence, provid-
ing a convenient means to receive entire projects from Liquid users. 
						

							NUENDO
File handling 29 – 655
Importing Premiere Generic EDL files
You can transfer audio files and their associated edits from the Adobe 
Premiere application to Nuendo. This is made possible by rendering a 
“Generic EDL” file from a session in Premiere, and importing the re-
sulting file. 
Proceed as follows:
1.Select “Premiere Generic EDL...” from the Import submenu on the File 
menu.
2.Navigate to the location of the Premiere Generic EDL file, select it and 
click Open.
You are now prompted to select a name and location for the new project folder that 
will be created.
3.After selecting, the new project opens containing all the audio files 
stored in the Premiere Generic EDL file and their associated edits.
Nuendo will also automatically extract any audio from video files if the audio is refer-
enced in the EDL file.
Exporting and importing MIDI files
Nuendo can import and export Standard MIDI Files, which makes it 
possible to transfer MIDI material to and from virtually any MIDI appli-
cation, 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. 
						

							NUENDO
29 – 656 File handling
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:
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 322) 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 PDF 
document “Working with MIDI”.   
						

							NUENDO
File handling 29 – 657
• The MIDI file will include the Tempo track.
• 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 the “MIDI realtime param-
eters and effects” chapter in the separate PDF document “Working with MIDI”.
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 173) 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. Option Description 
						

							NUENDO
29 – 658 File handling
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 chose 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.
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:
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-
tomation trackIf 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 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. 
						

							NUENDO
File handling 29 – 659
As mentioned on page 657, 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 the “MIDI 
Processing” chapter in the separate PDF document “Working with MIDI”).
• 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.
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 Nuendo 
Project window. The Import Options apply if you use this method as well.
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. Option Description 
						

							NUENDO
29 – 660 File handling
Importing Cubase VST files
As described on page 638, Nuendo can open Cubase SX/SL projects 
with the regular Open function. It is also possible to import 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 
Cubase 5.0 or later and convert it to a Nuendo project. When import-
ing 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.
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 Connections” dia-
log 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.