User manual

463
File handling
• When referencing media files (see below), you can set
the referenced output path by entering it in the “Media
Destination Path” field or by clicking on “Browser…” and
choosing it in the file dialog that appears.
All file references will be set to this path. You can create references to
media destinations that do not exist on the system you are currently
working with, making it easy to prepare files for use in projects on an-
other system or in a network environment.
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 sub-directory in the ex-
port 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, select “Consolidate Events”.
You can also define handle lengths in milliseconds to include audio out-
side each event boundary for later fine tuning. 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.
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 Ref-
erences”, 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. Pull down 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 should be
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.
• “Import at Timecode Position” will insert the elements
contained in the OMF file at their original timecode posi-
tions.
This is useful when you want to position every imported element at its ex-
act 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 con-
tained in the OMF file starting at the timecode position
saved in the file and keeping the relative distances be-
tween 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 time-
line (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 ob-
jects has highest priority.
• 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 im-
ported OMF file.