I'm working on a feature edited in FCP 7 w/ DNxHD proxies, passed through RCX 14 to relink the R3Ds, and imported to Premiere Pro CS6/AE for additional work.
In RCX fcpxml import, if I choose "replace with slugs", then in the timeline I see slugs for problem clips. If I export this as fcpxml and import into premiere, the importer dies with a generic error.
If I choose "manual relink", problem clips are simply gone (I don't get any questions). Exporting fcpxml and importing into premiere works*. I have all my video clips linked to r3ds; all audio, transitions, effects have been stripped out. *Bug: All the clips have been scaled to 0, and are thus invisible. I have to reset the motion/scale to 100% and then I can see the clips.
If I import the FCP XML (direct from FCP) I can import all the proxies directly into premeire with transitions, some color and speed effects, and all audio. I even have some FCP slugs that show up in premiere as slugs.
Thus, I would like to request the following adjustments to the FCP XML import/export in RCX:
- Make RCX slugs compatible with premiere and FCP. To demonstrate the proper XML, you could create a slug in FCP, export as FCP XML. If RCX used that xml definition, maybe PPRO CS6 would read it fine as demonstrated above.
- Fix the scale bug on the clips so premiere automatically assumes each clip is 100%. Easy work around: Select all clips in timeline, right-click, remove effects, Motion. I understand this may be an adobe bug, so can you talk to their adobe labs to fix the r3d importer if so please?
- Allow the option of either stripping out all non-r3d stuff (apparent current behavior), or keeping everything RCX doesn't understand as is (log notes, comments, transitions, effects, etc), only linking the proxies to the r3ds, but passing through all the other stuff as is to the xml export. That could remove a lot of work after round tripping or passing through RCX (see workflow below). Although as is, the automatic relinking of r3ds is great and is way worth using rather than doing it manually. This suggestion would improve this gain even further.
My workflow for the curious:
Edit in FCP 7
Import fcpxml in RCX with: absolute timecode, manual relink
Export fcpxml in RCX
Import fcpxml(RCX) in Premiere. Relink as needed, I usually just need to find the first.
Import fcpxml(FCP) in Premiere. Relink proxies as needed.
Now you have two timelines, one with r3ds only at as shot resolution (5k). The other at your proxy resolution with proxies, sound tracks, and some effects and transitions (whatever PPro can import from fcp). From here do what you like depending on your deliverable.
One method might be to create a new 5k sequence. Copy all proxy footage/audio to new timeline. Copy all r3d footage to new timeline, starting at a layer above the proxy layers. Select all r3ds, right-click, Remove Effects, Motion (to reset scale). Then go through and adjust as necessary, copying important meta data, transitions, and effects from the proxy and applying it to the r3d. (RED: The third request above would minimize this last step).
I saw no appreciable difference on my project other than file size to using FCPs native xml export versus Automatic Ducks export.