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

Exporting 25fps timeline - Davinci Reads as 50 fps

Community Beginner ,
Nov 04, 2024 Nov 04, 2024

Copy link to clipboard

Copied

After updating to 2025 25.0 Premiere I noticed that after exporting 25fps timeline XMLs for grade, colourist receive 50fps timeline in davinci.

After opening same timeline in the premiere 2025 24.6.3 it appears that 2025 premiere exported it as interlaced sequence. 

 

Premiere 25.0 Sequence settings  

Screenshot 2024-11-04 at 22.45.37.png

Davinci Project Import Screen
Screenshot 2024-11-04 at 22.47.00.png
Premiere 24.6.3 same XML import
Screenshot 2024-11-04 at 23.01.44.png
 
 
Bug Fixed
TOPICS
Import and ingest , Projects or collaboration

Views

1.1K

Translate

Translate

Report

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 3 Pinned Replies

Adobe Employee , Nov 05, 2024 Nov 05, 2024

Hi @jonas5C3F  ,

Welcome to the Premiere Pro forums! We are glad to see you here. We need a few more details to try to help with the issue. Please see, How do I write a bug report?

Thanks for submitting your bug report. I hope we can help you soon. Sorry for the frustration! 

Thanks,
Rach

Status Needs More Info

Votes

Translate

Translate
Adobe Employee , Nov 05, 2024 Nov 05, 2024

Hi @jonas5C3F 

I can confirm that this is happening in the current version of Premiere Pro 25 and did not occur in the previous version. For now the work around on Mac  would be to change the field dominance segment to none in text edit. I am logging this as a bug and will speak to our team to have this looked at.

Thanks

Ian

Status Acknowledged

Votes

Translate

Translate
Adobe Employee , Dec 05, 2024 Dec 05, 2024

Hi @jonas5C3F ,

This issue has been fixed in beta 25.2 build 10 . Thank you for pointing it out to us. 

Ian

Status Fixed

Votes

Translate

Translate
19 Comments
Explorer ,
Nov 05, 2024 Nov 05, 2024

Copy link to clipboard

Copied

Same problem as https://community.adobe.com/t5/premiere-pro-discussions/premiere-v25-exports-xml-with-wrong-fps/m-p/...

Here's the XML from the same sequence (with all settings the same) exported from V25.0 compared to V24.6.3
Screenshot 2024-11-05 at 6.26.45 PM.pngScreenshot 2024-11-05 at 6.26.51 PM.png
<fielddominance> is wrong in my V25 XML export. Not sure what TL.SQVisibleBaseTime="4064256000" is but it is different too.

Sequence 1920x1080 25 fps
MacOs 14.6.1 
Premiere V25 
Resolve V19.0.3

Screenshot 2024-11-05 at 6.42.48 PM.png


Doesn't matter if there is no time-remap or speed changes on any clips. ProRes LT clips in timeline.

Current solve:
Import timeline in Resolve as normal, copy clips into a new 25 fps timeline. Make sure to set 25 fps starting timecode in Resolve to match. Most clips should sync up but do manually check and conform each clip!

edit: same situation in beta 25.2

Votes

Translate

Translate

Report

Report
New Here ,
Nov 05, 2024 Nov 05, 2024

Copy link to clipboard

Copied

Thanks for that insight. I've just manually edited XML in notepad, to change "fielddominance" valure to none. That seems to work as workaround and Resolve correctly interprets timeline as 25 fps.
It's a BUG nonetheless.

Votes

Translate

Translate

Report

Report
New Here ,
Nov 05, 2024 Nov 05, 2024

Copy link to clipboard

Copied

Hello, same bug here..

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Nov 05, 2024 Nov 05, 2024

Copy link to clipboard

Copied

Hi @jonas5C3F  ,

Welcome to the Premiere Pro forums! We are glad to see you here. We need a few more details to try to help with the issue. Please see, How do I write a bug report?

Thanks for submitting your bug report. I hope we can help you soon. Sorry for the frustration! 

Thanks,
Rach

Status Needs More Info

Votes

Translate

Translate

Report

Report
Community Expert ,
Nov 05, 2024 Nov 05, 2024

Copy link to clipboard

Copied

@Rach McIntire @jonas5C3F 


Hello.

 

I am chiming in to say that I am able to reproduce this, but with an additional note.

 

  • Issue - Incorrect field dominance in XML export.
  • Adobe Premiere Pro version number:  25.0.0 (Build 61)
  • Operating system - macOS Sonoma14.6.1
  • System Info:
    • Apple M1
    • 16GB
    • 512GB Internal Flash Storage
  • Video format:  1080p25 ProRes 422 LT
  • Workflow details:  Stringout of source footage using Video Track 1 and Audio Track 1
  • Steps to reproduce
  1. Start a new Project in Premiere Pro 2025.
  2. Create a new Sequence using the "HD 1080 25 fps" preset.
  3. Assemble source clips in Sequence.
  4. Save project.
  5. With Sequence selected, choose File > Export > Final Cut Pro XML....
  6. Set name and location of XML file and save.
  7. Open XML file in TextEdit and search for "field'.
  • Expected result - Field dominance should be "none".
  • Actual result -  Field dominance is "lower".

 

Additional note:  If a Premieer Pro 24.x project with a 25 fps Sequence is opened in Premiere Pro 25.x, the XML exports as expected.  This appears to affect Sequences made from scratch in 25.x.

 

Workarounds:

  • Edit the field dominance flag in the XML file in a text editor.  Or,
  • Import the XML and change the Fields from Lower Field First to None.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Nov 05, 2024 Nov 05, 2024

Copy link to clipboard

Copied

Hi @jonas5C3F 

I can confirm that this is happening in the current version of Premiere Pro 25 and did not occur in the previous version. For now the work around on Mac  would be to change the field dominance segment to none in text edit. I am logging this as a bug and will speak to our team to have this looked at.

Thanks

Ian

Status Acknowledged

Votes

Translate

Translate

Report

Report
New Here ,
Nov 08, 2024 Nov 08, 2024

Copy link to clipboard

Copied

Facing the same glitch as well. I have been export AAF which detects normally as 25 fps. Below are the AAF settings, Try it out. Been sending these AAF to colorists and haven't face any issue.

 

Screenshot 2024-11-09 004436.png

Votes

Translate

Translate

Report

Report
Explorer ,
Nov 10, 2024 Nov 10, 2024

Copy link to clipboard

Copied

Field information incorrectly written as 'lower field first' when exporting progressive sequence to xml

Not written as 'none'

 

Premiere pro ver 2025.0

MAC STUDIO M1 Ultra
MAC OS Sequoia 15.0.1

스크린샷 2024-11-10 20.22.36.png

스크린샷 2024-11-10 20.33.16.png

스크린샷 2024-11-10 20.29.40.png

  

Votes

Translate

Translate

Report

Report
New Here ,
Nov 17, 2024 Nov 17, 2024

Copy link to clipboard

Copied

Hello everyone!
I've been struggling for a couple of weeks now with a bit of a problem interpreting the timecode in Resolve (19) from Premiere 2025 exports. Namely, when keeping all settings in Premiere, that is, 25 fps (europe) and exporting the XML and then importing them, the dialog informs that the ‘EDL frame rate’ is 25fps, but the ‘timeline frame rate’ dialog informs 50fps. I'm working on a normal 25fps timeline, progressive scan, there are no interlacing settings or anything to indicate a different frame rate.
I already find a workaround - exported AAF without breaking it to mono. But...
I've been working extensively for a couple of years and have only now encountered the problem, especially as it happens the same on my version of Resolve as it does on clients. Has anyone encountered a similar problem? It's starts happening when i switched to newer version of Premiere.

Votes

Translate

Translate

Report

Report
LEGEND ,
Nov 17, 2024 Nov 17, 2024

Copy link to clipboard

Copied

I work for/with/teach pro colorists, so am always on the BM forums and LGG also. I've seen a couple posts in those places about R19 misreading data from XMLs also.

 

If you or anyone has a 'fix', I'd be interested in seeing it.

Votes

Translate

Translate

Report

Report
New Here ,
Nov 17, 2024 Nov 17, 2024

Copy link to clipboard

Copied

As I said, I have found a workaround to this problem by exporting AAF but this is no solution for me at the moment. The question is, which software is creating the problem? My guess is that the problem lies with Premiere, as for testing I imported my XML from a few months ago and everything read correctly.

Votes

Translate

Translate

Report

Report
LEGEND ,
Nov 17, 2024 Nov 17, 2024

Copy link to clipboard

Copied

As someone having been around colorists for a decade, the ongoing discusssions pretty much always include how to conform projects where you are fighting timecode for part or all of an XML/EDL/AAF file. I wish it was always just doable in a solid fashion. But it ain't that I've ever known.

 

I had a project a few years back where Premiere read every bit of timecode as the end points one frame 'farther' down the clip than Resolve. So 00:23:18:22 was one frame later in Premiere than Resolve. 

 

As we were shipping discs with files forth & back, and the other person insisted it wasn't his fault, I had to manually change the in/out points for every clip of a 58 clip sequence every flipping time I sent him a set. I did not find that humorous.

 

And in talking with the Premiere and Resolve devs the next NAB, both knew exactly what the issue was. Both said that they were interpreting TC correctly, and explained why the other was wrong.

 

Not ... helpful. At. All.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Nov 18, 2024 Nov 18, 2024

Copy link to clipboard

Copied

HI @wojtiman - This is a discovered issue that the devs are aware of.  I'm going to merge this to a different thread.  Thank you for your patience.

Votes

Translate

Translate

Report

Report
Participant ,
Nov 20, 2024 Nov 20, 2024

Copy link to clipboard

Copied

I can confirm this is happening too.

Votes

Translate

Translate

Report

Report
New Here ,
Dec 03, 2024 Dec 03, 2024

Copy link to clipboard

Copied

I honestly don't know how people use Premiere in a professional environment. How can such a simple task such as exporting a XML suddenly have bugs? I've been a Prem editor for over 10 years and have slowly been rolling over all my presets and plugins to alternative software. The focus on rolling out new features over fixing old bugs and creating a stable program is mind blowing.

Votes

Translate

Translate

Report

Report
LEGEND ,
Dec 03, 2024 Dec 03, 2024

Copy link to clipboard

Copied

As noted, is work for/with/teach pro color, most of them based in Resolve or Baselight. I spend nearly as much time in Resolve and the BM forums as Premiere.

 

Conforming from any app to another is a huge part of on-going discussions. Standard clips are solid enough, but scaling can be an issue.

 

And time things are always difficult for simple speed changes. But if you do any speed ramps, forget it. There's no way to get that between apps. Period.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Dec 05, 2024 Dec 05, 2024

Copy link to clipboard

Copied

Hi @jonas5C3F ,

This issue has been fixed in beta 25.2 build 10 . Thank you for pointing it out to us. 

Ian

Status Fixed

Votes

Translate

Translate

Report

Report
New Here ,
Dec 10, 2024 Dec 10, 2024

Copy link to clipboard

Copied

Why not just fix it in the actual release? So I need to install both versions of Prem now just to export XMLs correctly?

Votes

Translate

Translate

Report

Report
LEGEND ,
Dec 11, 2024 Dec 11, 2024

Copy link to clipboard

Copied

LATEST

They always run things first through the public beta, to catch unexpected issues.

 

Then schedule a new shipping release with several items in it. I think only once or twice in the last decade have they ever fixed one thing and done an immediate "shipping" update release.

Votes

Translate

Translate

Report

Report