Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
2

P: Imported xml timeline - motion properties disappeared

Explorer ,
Sep 14, 2025 Sep 14, 2025

Issue: Clips in a timeline imported from a Resolve xml file appear with no motion properties. Properties are null in the properties panel. The twirl-down motion menu in the effect controls panel is gone entirely. Operations like "fill frame" or manipluating the null properties can cause crashes. This is when using Beta & main release.

 

Use case: I intend to use Resolves AI smart-switch feature to expedite a podcast edit. Then send to premiere for finishing. I have successfully imported the sequence with all edits appearing correctly. But I can't be certain I will be able to scale it to a 1080p timeline to match my gfx assets etc without it breaking. I'm hoping this is a simple case of a parameter needing to be specified in the xml but this is where my knowledge ends. Happy to provide more details.

 

xmlISSUE1.jpg

xmlISSUE2.jpg

Bug Acknowledged
TOPICS
Import and ingest , Interoperability or 3rd party tools , Performance or Stability , Projects or collaboration
400
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Pinned Reply

Adobe Employee , Sep 23, 2025 Sep 23, 2025

Great news! The team was aware of this issue, and it has been fixed in Premiere Pro beta version 25.6.0 build 74 and later. The fix will be included in the next stable release, 25.6.0

Status Acknowledged
Translate
13 Comments
Adobe Employee ,
Sep 15, 2025 Sep 15, 2025

Hi @L.Ni -   Thanks for submitting your bug report. We need a few more details to try to help with the issue.
Please see, How to Report a Problem.

 

What are your system specs?

 

What version of Resolve are you using?


Sorry for the frustration.

Status Needs More Info
Translate
Report
Explorer ,
Sep 16, 2025 Sep 16, 2025

Instead of xml, I tried again using the .itio format (into premiere beta) and this worked without issue. Resolve version is 20.2, build 13.

Translate
Report
Adobe Employee ,
Sep 17, 2025 Sep 17, 2025

Hi @L.Ni - Can you send the XML to jamiec@adobe.com 

I'm glad OTIO has helped your issue.

Translate
Report
New Here ,
Sep 17, 2025 Sep 17, 2025

Same issue with xml from Resolve. I can´t see motion properties. Doing Match frame and replacing it works, but replace clip by clip is not a good solution

Translate
Report
New Here ,
Sep 22, 2025 Sep 22, 2025

Our workflow is to record video through Atem mini pro and them we export timeline from Davinci to XML and import it into the Premier Pro and this is where problem begins, we cant edit properties because we are missing Motion in our video from that xml

photo as proofSnímka obrazovky 2025-09-22 o 15.40.49.png

do somebody know why is this happening?

Translate
Report
Adobe Employee ,
Sep 22, 2025 Sep 22, 2025

Hi @Lukáš38753644xjrl -  Thanks for submitting your bug report. We need a few more details to try to help with the issue.
Please see, How to Report a Problem.

 

Can you send the XML to jamiec@adobe.com 


Sorry for the frustration.

Status Needs More Info
Translate
Report
Community Beginner ,
Sep 22, 2025 Sep 22, 2025

Having the same issue. Exporting XML timeline from Resolve into Premiere delivers no Motion Properties.

Mac OS 15.6.1. Premiere Pro 25.5.0. Resolve 20.2.13.

Temp workaround is applying Video Effects>Transform onto every clip but still not ideal.

Translate
Report
Community Beginner ,
Sep 22, 2025 Sep 22, 2025

Try this as a workaround...

In Premiere, open the problematic sequence created from the XML you imported from Resolve.  Export it as a Final Cut Pro XML (name it something else so you don't get confused).  Import the newly created XML.  The resulting sequence should now have Motion parameters in the effects tab.  At least it did for me.   Kind of an annoying extra step but doesn't take long.

Translate
Report
Adobe Employee ,
Sep 23, 2025 Sep 23, 2025

Great news! The team was aware of this issue, and it has been fixed in Premiere Pro beta version 25.6.0 build 74 and later. The fix will be included in the next stable release, 25.6.0

Status Acknowledged
Translate
Report
Community Beginner ,
Sep 24, 2025 Sep 24, 2025

See my post below.  Workaround is far less painful than adding a transform effect on every clip.

Translate
Report
Community Beginner ,
Sep 25, 2025 Sep 25, 2025

Thanks @John22368521k4cl!  That's a much easier work around. I tried it and it worked perfectly.  Great find!

Translate
Report
Community Beginner ,
Sep 25, 2025 Sep 25, 2025

Quick test for you: can you try exporting your Resolve timeline as FCPXML instead of standard XML and see if the Motion properties survive the import?

 

 

Translate
Report
Community Beginner ,
Sep 25, 2025 Sep 25, 2025
LATEST

@Rabih_Sleiman8490 Premiere won't import FCPXML. At least not without running it through something like XtoCC.

Translate
Report