Resolve Python API - Importing AAF, OTIO, FCPXML etc

Ask software engineering and SDK questions for developers working on Mac OS X, Windows or Linux.
  • Author
  • Message
Offline

Cookseyyyyy

  • Posts: 5
  • Joined: Mon Aug 01, 2022 12:59 pm
  • Real Name: Matthew Cooksey

Resolve Python API - Importing AAF, OTIO, FCPXML etc

PostFri May 30, 2025 3:08 pm

Hi everyone,

I’m building a fully automated round-trip editorial workflow using the DaVinci Resolve scripting API and running into a conformance snag.

What I’m doing:

Exporting my timeline from Resolve into various interchange formats:

AAF (clips import linked but loses most effects and transitions)

FCPXML (retains transitions and effects but clips arrive unlinked)

OTIO (ideal since it preserves the most metadata, but again clips arrive unlinked)

Programmatically preloading all referenced media into the Media Pool.

Importing the edited timeline back into Resolve via the API.

The problem:
After import, every timeline clip appears as a bright-red unlinked item (no MediaPoolItem → TimelineItem link). By contrast, when I perform the same import manually through the Resolve UI (File → Import), the clips come in properly linked to the Media Pool.

Questions:

Is this expected behavior when importing via the API for any of these formats?

Are there hidden import options or flags I might be overlooking that trigger Resolve’s conform logic?

Has anyone found a reliable workaround to get clips to auto-link on API import—short of manually running “Reconform From Bin…” each time?

Any insights, tips, or suggestions would be greatly appreciated. Thanks in advance!

for reference this is the result after running the script... Image
Offline

sushi ninja

  • Posts: 22
  • Joined: Tue Feb 14, 2023 8:01 am
  • Real Name: Satoru Taguchi

Re: Resolve Python API - Importing AAF, OTIO, FCPXML etc

PostTue Jun 03, 2025 9:25 am

I have not tried it, but this {importOptions} in the official documentation may be the feature you are looking for.


ImportTimelineFromFile(filePath, {importOptions}) --> Timeline

    ・"timelineName": string, specifies the name of the timeline to be created. Not valid for DRT import
    ・"importSourceClips": Bool, specifies whether source clips should be imported, True by default. Not valid for DRT import
    ・"sourceClipsPath": string, specifies a filesystem path to search for source clips if the media is inaccessible in their original path and if "importSourceClips" is True
    ・"sourceClipsFolders": List of Media Pool folder objects to search for source clips if the media is not present in current folder and if "importSourceClips" is False. Not valid for DRT import
    ・"interlaceProcessing": Bool, specifies whether to enable interlace processing on the imported timeline being created. valid only for AAF import


Sorry if this has already been tried.
Offline

atmosfar

  • Posts: 214
  • Joined: Fri Jun 05, 2020 1:06 pm
  • Real Name: Conor Sexton

Re: Resolve Python API - Importing AAF, OTIO, FCPXML etc

PostWed Jun 04, 2025 12:47 pm

Interested in following your progress here!

This forum might also be able to help you -- https://www.steakunderwater.com/wesuckl ... m.php?f=46

Return to Software Developers

Who is online

Users browsing this forum: No registered users and 7 guests