Back to Overview

Export Finished Media & Editor Timelines

Avid Media Composer & Premiere Support

Move a Sequence edit into Premiere by converting its FCPXML export, and understand the current Avid Media Composer options.

Sequence currently creates editable timeline exports for Final Cut Pro and DaVinci Resolve. Both destinations use the modern FCPXML format.

Premiere and Avid Media Composer use different interchange formats. You can convert a Sequence export for Premiere today, but Sequence does not currently create the AAF package required for a dependable Avid handoff.

Adobe Premiere

Premiere cannot directly import the modern .fcpxml file that Sequence exports. Adobe’s documented workflow is to convert FCPXML into the older Final Cut Pro XML format that Premiere recognises.

Convert and import the timeline

  1. In Sequence, open the variant you want to transfer and choose the DaVinci Resolve export destination. Save the .fcpxml file.
  2. Convert that file with XtoCC, the conversion tool recommended in Adobe’s FCPXML import guide.
  3. Open Premiere and choose File → Import.
  4. Select the converted .xml file and complete any import prompts.
  5. Check the imported sequence before continuing: confirm the edit points, media links, audio, frame rate, sequence dimensions, markers, and titles.

Conversion is an interchange step, not a perfect project translation. Adobe notes that some complex effects, transitions, and third-party plug-ins may not transfer correctly. Sequence exports a rough-cut timeline rather than an effects-heavy Final Cut project, but you should still review the complete sequence after import.

If media is offline

Keep the converted XML and the source media together when handing the project to another machine. If Premiere cannot find a source file, use its relink workflow and point it to the original media or the prepared audio exported by Sequence.

Avid Media Composer

Avid Media Composer uses AAF for this kind of editorial handoff; it does not import Sequence’s FCPXML export as an editable timeline.

Avid’s documented ingest workflow expects an AAF plus compatible MXF OP-Atom media. Importing the AAF into a bin creates master clips that link to that MXF media.

Sequence does not currently write AAF or create an Avid MediaFiles/MXF package. Renaming an .fcpxml file or passing it through the Premiere conversion above will not create a valid Avid handoff.

For now, use one of these routes:

  • Export finished media from Sequence when the edit does not need to remain editable in Media Composer.
  • Export FCPXML to DaVinci Resolve, rebuild and verify the timeline there, then use a Resolve-to-Avid workflow appropriate to your facility. Treat this as a separate conform and test it before relying on it for production.
  • Continue the editorial handoff in Final Cut Pro or DaVinci Resolve, which Sequence supports directly.

Why the formats differ

Sequence first projects transcript edits, silence removal, reordered sections, prepared audio, titles, markers, and profanity handling onto an editor-independent timeline. Each destination then needs a serializer for its own interchange format:

  • Final Cut Pro and DaVinci Resolve: FCPXML 1.14
  • Adobe Premiere: legacy Final Cut Pro XML
  • Avid Media Composer: AAF, normally paired with an MXF-aware media workflow

This shared timeline model makes native Premiere and Avid exporters possible without redefining Sequence’s editing decisions. Those serializers are not included in the current release.