Dolby Vision XML Import Broken on Flame 2025?

Wondering if anyone else is experiencing this. We recently moved from Flame 2023 on Centos 7 to Flame 2025.2.2 Update on Rocky 8.7. Importing of Dolby Vision XMLs is now broken. When importing an XML I get repeated warnings in the Terminal of “Cannot set GlobalMidOffset: No analysis available”. It lists out one warning for every event in the XML. The import is mostly successful except that the HDR FX events are missing the Mid Offsets like the warnings say. Therefor the SDR conversion is wrong.

I’ve tried importing xmls from different sources. Resolve v19, 18 and 17, Flame 2025, 2023. All experience the same terminal warning on import. I have no issue importing the same xmls on Flame 2023.

I’ve even started fresh by creating a new HDR track using HDR graded source, analyzing it, exporting it out using the Dolby Vision 4 distribution package preset and then reimporting the XML that was created. This also results in the same error and NG SDR conversion.

I haven’t tested this on earlier versions of 2025.
Dolby Vision config is v1.3, Preview Mode is v4.0. Perpetual License installed.

Thoughts?

Flame 2025.2.2 Update
Rocky 8.7

@i3djoe Late reply but I somehow missed this nearly a year ago! Did you ever get a solution for this? Did you report it and have a case number you’d be willing to share?

We have been reporting multiple bugs with the Flame Dolby Vision workflow since 2021. Although we do dozens of DoVi projects each year, the vast majority of them get delivered out of Baselight (we don’t grade in Flame). We only need the Flame DoVi postgrade workflow once or twice a year, but every time we go back to it, we find new problems, and have limited time to troubleshoot. It’s so buggy that we’re even getting to the stage of talking about using Resolve for these jobs in the future…

Anyway in answer to your original question, yes we are experiencing this (again) and I’m opening a new case, so any further info you got would be useful.

1 Like