Product specifications
Avid|DS 4.02 Release Notes • June 2001 10
EDL, OMF
, and ALE
OMF Import Fixes Since Version 4.01
A number of OMF import problems that occurred in 4.01 have now been fixed. To install the new .dll files, refer to
the Avid|DS 4.02 Upgrade Instructions.
CMX/GVG EDL Format Detection
When loading an EDL file, the File Open dialog box lets you select a format, such as CMX or GVG. With this
information, Avid|DS will try to validate your choice in relation to the contents of the file. However, the only marker
available for differentiation is the presence or absence of FCM lines in the EDL file. While the presence of FCM lines
indicates without a doubt that it is a CMX file, the converse is not necessarily true. Therefore, it is possible to load a
CMX file as GVG or vice versa, with unpredictable (but generally wrong!) results. If the EDL file you loaded is not
what you expected, verify that you specified the right format for itscontents.
EDL Only Shows One Stream of Multi-stream Clip on Timeline to EDL
A multi-stream clip, such as a 5.1 audio container clip will only show one mono stream in an EDL constructed from
that timeline instead of the expected 6 streams.
One-sided Transitions Not Completely Supported
EDL and OMF effects with one-sided transitions are imported in Avid|DS as clip effects (just like previous versions
of Avid|DS).
OMF Reverse Timewarp Limitation from Avid Media Composer
and Avid Symphony
The OMF files exported from Media Composer and Symphony systems do not contain any negative speed value
information for the timewarp effect.
Parameters of AVX Plug-ins in 24p OMF Files Do Not Conform
24p OMF files created by the Media Composer and/or Symphony systems do not contain parameter information for
AVX plug-ins. When such an OMF file is imported into Avid|DS, the AVX effects are recreated at the correct
location, but all the parameters are at their default values. No entry is added in the OMF log.
Message in OMF Error Log is Incorrect for Audio Transitions
When conforming an OMF that contains audio transitions, the OMF error log will include one or more instances of
the following message: “Unrecognized effect encountered. It was not imported.” The correct message is: “Effect
created but parameters not loaded from OMF.”