Apple Final Cut Pro 6 - Manual (Page 1641)

158 Part II Project Interchange
An explanation of the sample code above follows.
Every Final Cut Pro XML file requires the first three elements:
 element: This defines the document as an XML file. The example above
shows an element with two attributes: version and encoding.
 element: Every XML document requires a Document Type Definition, or
DTD. The DTD for the Final Cut Pro XML Interchange File Format is called xmeml.
 element: This is the root element of every Final Cut Pro XML file. Every
document should end with a closing tag.
The element defines a Browser clip in Final Cut Pro. The element above
contains the following elements:
 element: This is the name of the clip.
 element: This is the duration of the clip, in frames.
 element: This is the frame rate of the clip. The element contains a
element that determines the clip’s frame rate and an element
that determines whether the clip frame rate is actually 29.97 fps or 30 fps.
For a complete list of Final Cut Pro XML Interchange Format elements, see the
documentation for the Final Cut Pro XML Interchange Format at
http://developer.apple.com/appleapplications .
Example: Creating an XML File and Importing It into Final Cut Pro
Final Cut Pro always exports verbose XML, which means that every element and
subelement is included. However, when you import XML, Final Cut Pro accepts sparse
XML, which means that you only need to provide a limited number of required
elements. This means you can create fairly terse XML and Final Cut Pro fills in missing
information with default information.
You can use the sample XML code on page 157 to create an XML file and import it into
a Final Cut Pro project.
1 Open a text editing application such as TextEdit.
Note: This example assumes you are using TextEdit, the built-in text editing application
that comes with Mac OS X. TextEdit is located in the Applications folder on your hard disk.
2 If a new window doesn’t already exist, choose File > New (or press Command-N).
3 Type or copy and paste the sample XML code on page 157 into the new TextEdit window.
Errors in XML code will result in errors during import. Make sure you type carefully and
check your work.