If you haven’t already installed the Premiere Pro CS5 (5.0.2) update, then you should do so. That updates fixes a lot of problems and adds a lot of new capabilities.
In the post providing details of the Premiere Pro CS5 (5.0.2) update, one item says ‘various fixes for Final Cut Pro XML export’. A few people have asked what those fixes are, exactly. So, here they are.
- Premiere Pro no longer appends
file://localhostto network path names on Windows.
<name>attributes are now exported for
- Any special characters in the
<reel>attribute are now encoded as XML instead of passing through untranslated.
- The duration and rate of master clips are now set accurately instead of using dummy default values. This typically only matters for media that’s offline when the XML is imported, since the contents of an online media file overrule these in both FCP and Premiere Pro.
- Markers and subclip offsets should now be written using the correct framerate instead of always being set to 29.97fps.
<audio>element now has a new complex subelement
<outputs>objects are exported for audio track groups. This subelement is used primarily for round-tripping 5.1 channel audio through Premiere Pro.
<audiolevels>objects are now written to tracks that have had audio level adjustments in Premiere Pro.
- Each audio
<track>element now has a new
<hardpan>attribute (Premiere Pro proprietary) and
<outputchannelindex>attribute (FCP standard) to help with multi-channel audio round-tripping.
<uuid>attributes are now exported for clips and sequences. These UUIDs (universally unique identifers) can be used for custom workflows. When using the normal FCP import mechanism, Premiere Pro will generate new UUIDs for each clip or sequence it imports through FCP XML, rather than reusing the ones in the XML file.
- Fixed an FCP import failure on 64-bit Windows when running with top-down memory addressing.
See this page for details of exporting a Premiere Pro project as a Final Cut Pro XML project file.
“Export a Final Cut Pro XML project file”