Hello y’all. I need assistance is setting up a Rec2100HLG workspace. I am looking for a direct phone conversation and willing to pay for it… I need someone who knows this inside and out.
This should take less than an hour. I need this right away (within the next day)… Thanks!
We’re also going to need to have an HDR workflow pretty soon. Would love to know if there are any specific Logik Lives, YouTube vids, or threads particularly for those who haven’t touched it?
HDR really isn’t that difficult to get your head around once you get into it. What would you like to know? I’m happy to try to help and answer some questions if you’d like.
I covered HDR workflow in an online discussion for Autodesk and Dolby a few years back. Not sure if that is helpful to you at all but I attached a link to the video below? I didn’t really cover HLG but have delivered it multiple times so if you have anything specific you’d like then feel free.
Thanks very much, Adam.
We finish most of our HDR jobs in Baselight, but about once or twice a year we have a major project requiring HLG (or PQ) deliverables from Flame. For these we inherit graded media from Baselight and create versions in HDR and SDR. If this is your end goal (whether or not you’re grading in Flame), it’s worth knowing that over the last few years we’ve uncovered multiple bugs with the DoVi workflow, always involving the Dolby Analysis and SDR trim. Some have been fixed, some haven’t.
We’re actively exploring finishing in Resolve for these jobs, as the SDR trim part of the wrokflow seems to have so many issues.
If you only have HDR deliverables (which is unlikely) then you shouldn’t have any problems!
That’s interesting. I haven’t touched the Dolby tools for a couple of years and it was working then. How is it broken? Have you contacted support?
There is a bug in flame where getting a trim pass from Baselight causes a very slight gamma shift on the SDR output. This has been an issue since 2025, maybe 2024 and not sure if it has been fixed yet.
We were doing colour loops with baselight and noticed it. We are having to use 2023 for HDR finishing
Autodesk acknowledged it but we haven’t had time to test the latest versions
All logged with support…
FLME-66770: Imported Baselight XML HDR track shows luminance jump over dissolves
FLME-63099: Exporting a Dolby Vision sequence with the Export Between Marks option enabled does not generate a media file with the selected tone mapping.
FLME-67823: Segment (media or gap FX) aligned to video cut point on lower tracks affects HDR Track tone mapping
(merged with another case number): L3 MidOffset metadata is keyframeable in Baselight. In Flame it’s readable but not editable, and so not keyframeable, so it gets corrupted in an imported DoVi XML, causing luminance bumps. This actually feels like part of the implementation of DoVi is broken in Flame, as DoVi should behave the same and have the same features irrespective of host software. This is probably whsat @Ben is referring to as well.
There have been others which I haven’t listed as we think they’ve been fixed, but you see why we’ve lost confidence in it…
FLME-70086 - strikes again. The dev team are looking at it, but it hasn’t been acknowledged on any release notes.
In Flame 2026.2.2 and Flame 2027, the issue is still there. Trying to use DV Trims gives you a luma shift.
That’s disappointing if that is the case. The Flames Dolby Vision toolset is excellent, I much prefer it over any other implementation I have seen and I’ve seen a few. You need to be able to trust it.
I’m not involved in the beta program any more so not sure if it is being used much in beta?
Yeah its essential it’s fixed as we can’t move on from flame 2023 until it is!
Why it’s taken so long to look into it have no idea.
@fredwarren any ideas if this is fixable? Basically we can’t use external trim passes in any version of flame from atleast 2025 onwards
It’s hard for me to not sound like an asshole so why disguise it:
If you don’t participate in the software development programme and your niche voice gets drowned out by four voices that talk about the fonts used in subtitles then Don’t be surprised that things don’t move in the direction of your desires.
it’s 100% legitimate that your business requirements from the year 2022 have not been addressed, but you’re whining about them 1,400 days too late.
Which is like calling for a tow truck four years after you broke down.
I think that was the last version with permanent licenses?
Good thing you aren’t paying for subs. We are sitting here for 2+ years paying 10s of thousands in sub to have the privilege of using 2025 due to multiple critical failures in Flame, of which I’ve been incredibly vocal about during the development cycles.
Or have submitted a bug report.
to be fair though, it looks like someone has at least done that. From experience, I also know that being on the beta program doesn’t always equate to seeing what you want implemented either. It is still rewarding and helpful to be part of the process so would encourage those with time to do so.
I don’t recall ever caring about subtitles or fonts or text layers or paint but it doesn’t stop me from attempting to redirect the asteroid.
@ALan You funny boy…
NOW you’re justifying people lingering on older versions?
Hilarious but ironic…
What’s that American phrase that I’m supposed to understand and use by now?
Give me a break?
Excellent
Onwards
We will be on 2025.2.5 until the day I retire. Not by choice. Not by want. Not by lack of effort.
But by the complete in-ability to be provided a version of Flame that does not have critical Studio killing bugs.
One thing I realized about how much I enjoyed my time on the mountain, was looking up, looking down, looking to the side, and I am where I am. The totality of my being, my life, at that moment, was right there. No ambiguity. One foot in front of the other, and that’s where I am.
My time at work, is all about ambiguity, and relying on the in-competence of others.
Good luck hiring freelancers
Before we get in to some stupid he said she said stuff:
We did great work
Using flame 2027.
The client accepted our efforts.
Hundreds of millions of eyeballs saw it.
Our team are undeniably exceptional.
So there’s that…
Cool. Now work collaboratively, centrally, and burn.
Nothing I have written is disputed by ADSK.