XML opened in resolve not matching timeline in premiere

Report · Feb 21, 2020

Getting FCP translation results with many errors like this.

Translation issue:

Effect <Blackmagic RAW> on Clip <A004_02041730_C018.braw> not translated.
The format as far as frame rate and resolution are matching as 23.976 and 3840 x 2160. When playing the timeline back in resolve, all of the clips are off by a few seconds.

The funny thing is, I have no issue exporting my timelines back and forth if I use another transcribed codec and then relink back to braw. but when it's braw to braw, then everything is jacked up!

Report · Feb 22, 2020

Are you using the BlackMagic plugin? That one was buggy enough for me across several updates I finally gave up and bought the Autokroma AfterCodecs/BRAW plugin for Premiere and MediaEncoder. Farve, with A-K, has actually been on here a few times helping users of the BM plugin get it functioning better, and one of the issues I think was time-code problems.

So ... you might try the Autokroma plugin and see if that works better.

Neil

Report · Feb 22, 2020

I bought Autokroma back when braw wasn't supported in Premiere but now that it is supported i've been updating the braw. But I never actually uninstalled Autokroma so not sure if that may be causing an issue. I'll try that when I get home.

Report · Mar 12, 2020

Hello Endrid,

There are always issues when working with 23.96 framerate BRAW files in Premiere Pro and then exporting to FinalCutPro XML, it is because how Adobe and BRAW are handling Timecodes.

With BRAW Studio, you can solve this problem ! See this article to know how to : https://www.autokroma.com/blog/BRAW-Wrong-Timecode-Adobe-Premiere-Pro/

Also please remember to update BRAW Studio to the latest version !

Best,

Nicolas from Autokroma

Report · Feb 18, 2021

I'm having the same problem now. The funny thing is that in my case I was able to export an older version of the project when I did it for practice prior to actually trying to color graded. Once the edit was finished now every time I try to export FC XML I get that error and when uploading to Resolve the old project I tried is importing (that project doesn't exist inside my Mac anymore).

Have you found a solution?

Report · Feb 19, 2021

Hello @ochovisuals,

Are you using BRAW files in your project ? Which plugin do you have ?

In case you are using BRAW Studio, did you try the "Export Corrected XML" feature ?

Best,

Nicolas from Autokroma

Report · Feb 19, 2021

Hi Nicolas,

I am using BRAW files but I'm using the Blackmagic plugin. I was able to do it before with this plugin and in my color grade class everyone did it with that plugin as well.

I'm just not able to figure out why this is happening. I did look up BRAW studio and it is $59 so since I seem to be the only one with the issue (even online I found only 1 more person with the same problem) I'd like to find a solution outside of BRAW Studio.

Thanks for commenting.

Report · Feb 19, 2021

I work with a lot of BRAW, from my BPMCC4K. Love the cam, love the media.

But ... from hours of experience with it, the freebie plugin from BlackMagic is worth exactly what you paid for it ... zero, zip, nada. Dang thing kept 'breaking' and causing all sorts of hassles. I finally went and paid for the Autokroma plugin.

It just ... works. And you have options for doing things like setting presets within it for different types of work or settings you may do with the camera. If you've got different cameras, make presets for each cam. That bit I really love.

Plus ... they have other options for helping with timecode issues and such. and they also provide by far the best support for the BM plugin here! Their customer service is great, whether you use their plugin or the BM one.

So ... you gotta make your own choices, but spending time screaming at the computer or banging your head on your table is both uncomfortable and an expensive waste of time. Well, and compared to say the Red Giant Universe ... which I also finally broke down and got ... this is cheapo.

You gotta be able to just get the work out.

Neil

Report · Feb 21, 2021

Thanks @R Neil Haugen !

If you want to stay with the BMD (free) plugin, here are some few advices though :

There are problems with 23.97 and 29.97 framerates, so if you want to avoid problems with XML, just don't use those framerates (if you can) while recording your BRAW footages.

Otherwise, you can fix the timecodes yourself by hand in Premiere Pro. You need to change the "Media Start" timecode of your BRAW footages, but it will be painful if you have a long timeline ...

You can correct BRAW timecodes with BRAW Studio without a license too. But it will be also be dangerous and painful :

keep a project NEVER saved with BRAW Studio installed (be careful on this : make backup before installing) and do not erase existing BMD plugin while instaling BRAW Studio.
Convert your project to BRAW Studio with the BRAW Studio Panel (no need for a license)
Correct all your BRAW timecodes with the BRAW Studio Panel (no need for a license)
Export XML from PPro directly
Uninstall BRAW Studio

Just an advice if you want to continue with the BMD Plugin : updating the BMD plugin can be bad (sometimes updating makes your BRAW clips in premiere pro unusable), so don't try to update in a middle of a project!

Also, Resolve doesn't like network paths for footages. I didn't find any workaround though. Maybe I would need to dig more on the internet if some people found workarounds for this.

That's all I know on this, hope that it helps.

Bon courage!

Nicolas from Autokroma

Report · Feb 21, 2021

Thanks Nicolas,

I was able to make it work. I'm not sure what was creating the problem but I deleted the entire project in Davinci then just added everthyng back BUT I didn't add the clips first to Reaolve. Before I was adding the clips then importing the XML. This time, after reading a few articles, I imported the XML and let Davinci pull the clips on its own and it worked.

Don't see how the first method would be a problem but this just worked.

thanks for taking the time to help.