The "EDL Export" feature allows users to export the arrangement of audio items on the timeline into a file. The term "EDL" stands for "Edit Decision List". The generic export format is XML but other formats can be tailored on request, or by the user.
To enable "EDL Export", set the
UseEDLExport parameter to
1. Set it to
0 (its default value) to disable the feature. The parameter can be set at USER, LOCAL, or GLOBAL level. Note that USER settings, as always, override LOCAL and GLOBAL settings, and LOCAL settings override GLOBAL settings.
"EDL Export" will be available from now on in the "File" menu, above the "Cleanup..." item.
Using EDL Export
The "EDL Export" menu item is enabled when the timeline contains at least one audio on any track, although you will usually have several audio elements on several tracks when you want to use EDL Export.
When you click the "EDL Export" menu item, the audio editor asks you for a directory and file name to which to save the EDL data. It will remember the most recently selected directory, even across editing sessions. The file is given the extension
.xml by default unless you explicitly type a different extension.
The exported EDL file contains all information about the arrangement of audio elements in tracks, including name and position of audios, position of mark in and mark out points, and about which tracks (if any) are muted. The XML information is defined by an XML schema file which is delivered by DAVID upon request.
Exporting into Other File Formats
The audio editor enables users or administrators to plug in their specific output format. This is achieved via an XSL transformation. You can create your own transformation, or place an order with DAVID to have it created, save it into a file, and configure the audio editor to execute the transformation. You need the file "DigaXMLTransformer.dll" which is available from DAVID upon request to execute the transformation.
Create a configuration entry with the name
EDLTemplate_1. The entry value is the path of the file that contains the transformation. From now on, the File menu will display a sub menu "Export EDL" which offers the configured transformation, and in addition raw XML export. To configure several transformations, use configuration entries
If you want the menu entry to be different from the file name, add a vertical bar (
|) after the file name, and after the bar, write the text you want to appear in the menu.
To supply a default file extension for the created file, add another vertical bar, followed by the extension.
EDL Configuration Example
EDLTemplate_1=C:\DigaSystem\test.xslt||xml EDLTemplate_2=C:\DigaSystem\nomute.xslt|Omit muted tracks EDLTemplate_3=C:\DigaSystem\ToHtml.xslt|Export as HTML|html|1
Line 1 defines the "test" format into a file with the default extension
Line 2 defines the "nomute" transformation which appears in the menu as "Omit muted tracks". This entry has no default extension; if the user doesn't type the extension, the file will not have one.
Line 3 defines the "ToHtml" transformation. The menu entry is named"Export as HTML", and the default file extension is
.html. Script execution is allowed.
Note that script execution should only be allowed if the respective XSL transformation actually contains script code. It is disallowed by default, for security reasons. Administrators should see to it that unauthorized script execution is not possible.
Grouped Audio Elements and Complex Clips
The MultiTrack screen enables you to join several audio elements into one, for easier handling. Internally, these joined elements are still maintained as separate identities. The EDL file also treats them as such, i.e. the exported file will contain all joined audio elements as though they were not joined at all.
The same is true for "complex clips". A complex clip is one that is made up from more than one audio take. The exported file will list all source files from which this clip was created.
Metadata in the EDL
Since Audio Editors version 7.4.1511.0, the EDL optionally contains all available metadata for the audio clips. This feature is active by default and can be switched off by setting the configuration value
0. The EDL contains version number 1 if no metadata is present, and version number 2 if metadata is included.
Projects that were saved with a modern version of the MultiTrack editor contain all information that is required to create the EDL data. Thus, the exported EDL file of a loaded project will have the same content as an EDL that was created immediately after composing the project.
- Volume edits, fades, and markers are not contained in the EDL.
- When the project contains audio material that was compiled from different sources, the EDL refers to the compiled data and not to the sources from which the material was originated. "Compiling," here, refers to the "Compile object" operation, or to saving a project as an audio file.