Publishing an FCP X XML Sequence with time warps not possible?

[Peter_Tresize]

Hope someone can clarify this:

On Logik, I recently read timewarps aren't possible to export within an XML. 

I can understand ramp TWs wouldn't work, but wonder why basic TW aren't supported.

In the documentation AAF limitations are clear, but the XML page didn't give the info I was looking for: that TW aren't supported.

http://help.autodesk.com/view/FLAME/2018/ENU/?guid=GUID-68D1B817-E18E-4F11-AE9D-B0C0385CC19F

http://help.autodesk.com/view/FLAME/2018/ENU/?guid=GUID-67619F57-5913-4C2A-B4A7-0FF036AEB273

So, is it really back to EDLs for exporting edits with TW?

Thanks

Peter

AAF Limitations:

Limitations

The following guidelines will help you create AAF that should conform properly in third party applications. 

Metadata-only AAF export:

The idea with metadata only AAF export is to provide to third party applications a sequence that reflects the editorial intention. You should prepare the sequence prior to exporting it to minimize problems in the third party application. 

• Only use Dissolve transitions. Wipe, Action, and Matchbox transitions are not exported to the AAF, and should all be converted to Dissolves prior to export to avoid timing issues: these transitions are ignored and the timing of the sequence might be impacted. 
• Avoid using generated sources. Since by definition a metadata-only AAF export does not export any media, the exported AAF would reference sources that are not available outside of Flame. 
  • Timewarps 
  • Containers and Matte Containers 
  • Hard Committed segments 
  • BFX 
  • Content generated internally (Tools, Batch, etc) 
  • Colour sources, Bars, Noise, Gradient 
  • Fade to / from colour

XML Limitations:

Limitations

Note that when exporting a sequence as an FCP X XML file:

• The FCP X XML format does not support file sequences definition so exporting a metadata only XML referencing file sequence OR exporting file sequences will not work in FCP X and DaVinci Resolve. But the file will be loadable in Flame. 
• The accompanying video media files exported by Flame must use either QuickTime or MXF containers. 
• The accompanying audio media files exported by Flame must be either AIFF or WAVE. 
• Audio sub-frame editing is not supported. Ensure audio edits are frame-based. 

Metadata-only export limitations:

• When exporting a sequence as XML-only , the segments of virtual media generated in the application (Colour Sources, Gap FX, Tools or Batch, Container, Matte Container, etc) are seen as Unlinked Media. 
• Avoid using transition fromand to colour clips because these cannot be represented in third party applications when exporting only XML metadata. There is no problem for FCP X XML with exported media files. 
• FCP X XML does not define the bit depth of the sequence. The resulting sequence is created at the project bit depth. Override the project bit depth using MediaHub > AAF & XML Import Option > Select Resolution. 

Media file-related limitations:

• A sequence referencing AVC-HD media files exported as XML-only do import correctly in Apple Final Cut Pro and DaVinci Resolve. You should export the sequence and new media files. 
• When working with mixed resolution content, it is possible to export an XML that references the Original Media and generate media files of the original source clip resolution. 
• A sequence made of mixed frame rates is exported at the sequence rate, and the Original Media option generates files using the sequence rate. If clips were resized to accommodate the resolution difference, the generated media files are exported at the sequence resolution. 
• Containers and Matte Container are exported as new clips and use the sequence's record timecode and rate. No alpha is exported for Matte Container. 
• Transitions in FCP X XML are always centered and have even duration. Since Flame is capable or creating transitions of different orientation and duration, the transitions are modified to be compatible with FCP X. 
• Avoid using illegal Unix characters in sequences and clip names because some third-party applications cannot read media files with such characters. Flame does not sanitize the file names when exporting XML with media files. 
• XML files from DaVinci Resolve referencing file sequences cannot be imported in Flame since the media is flagged as Unlinked Media.

[Grant.Kay]

Hi Peter,

As far as I was aware, basic time-warps are supported via XML and AAF.

If you have any issues importing the XMLs with time-warps, please let us know.

Many thanks!

Regards

Grant

[Peter_Tresize]

Hi Grant,

Thanks for your reply.

I was referring to exporting XML with timewarps.

I found one of your videos helped answer my question: http://area.autodesk.com/blogs/discreetuk/round-tripping-from-smoke-2016-to-final-cut-pro-x

@ 5:30: time warps are “purposely committed in order to keep the sequence timings”

I expected ramp timewarps not to be possible, but thought normal timewarps would be possible. 

@8:45   re: xml only   “effects such as timewarps .. do not link because no media was exported, when you only export the xml”.

Thanks for your video, it makes the limitations very clear.

Maybe I just missed it somewhere, but I’d recommend for the benefit of others, to make it more clear in the documentation.

Regards,

Peter