Bug alert 8.1 – XML to FCP7 turns out a 24.98 fps timeline?!?

[Ola Haldor voll]

I had it once but I’ve never figured out how to reproduce it. I’m on a new episode today, so we’ll see when the day is over, or tomorrow perhaps after rendering what’s going on.

Quick solution in FCP was to select all clips, cut, open Sequence Settings, make it 25fps and hit OK, then paste.

All OK.

I’ll email BMD directly if there’s an issue with this again.

[Juan Morales]

I did the same, copied everything on the timeline, made a new sequence 1080 – 25p and pasted everything back.

Hmm, 24.98 fps. Still, never had this problem before with Resolve… or FCP7 for that matter.

[Ola Haldor voll]

I don’t have the XML nor that particular project, but if you do – could you check the XML and see if there’s any weird things going on, like drop-frame or NTSC mode? Or maybe the frame rate itself has been modified in the XML?

[Juan Morales]

Checked the XML file… It looks like something was misinterpreted somewhere by the looks of it. Here’s a bit of the XML code genereted by Resolved:

Andreas Ensemble_DEF (Resolve)
5284

25
true

-1
-1

00:00:00:00
0
NDF

25
false

Any thoughts?

[Juan Morales]

Wait… Posted it wrong. Here it goes again:

[Margus Voll]

maybe your original files are not 25 ? and resolve sees that ?

—

Margus

https://iconstudios.eu

[Rohit Gupta]

Could you please send us the original and new XML? At davincihelp at blackmagic-design.com?

[Ramesh Jai]

Same issue here. I copied and pasted into a new sequence. Never had this problem with the previous version.

[Rohit Gupta]

Hi Juan,

Thanks for alerting us to this issue, and this has now been fixed. This will be available in the next dot update.

Meanwhile, if you open your XML file in any text editor, do the following:

Replace all occurrences of this pattern in the XML:

<ntsc>true</ntsc>

with

<ntsc>false</ntsc>

[Juan Morales]

Thanks, I love the quick response you guys have with this software!