Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
16th January 2021, 14:26 | #81 | Link | ||||
Broadcast Encoder
Join Date: Nov 2013
Location: Royal Borough of Kensington & Chelsea, UK
Posts: 2,905
|
Kanpai!! xD
Quote:
When I was making SafeColorLimiter this discussion popped up: and Quote:
Quote:
Quote:
So, in a nutshell, this is what I think led to the misunderstanding. 1) End users receive a Limited TV Range 10bit 64-940 file with a color curve applied, either HLG or PQ 2) Broadcast studios can also use Full PC Range YUV values for those curves, however it's much more likely to have Full Range only for curves like Slog, Clog, LogC, etc 3) You're checking values and doing your calculations in RGB (assuming that the content is in Full Range) as LUTs must be applied in RGB but here's the thing: when you have a Limited TV Range YUV file that is delivered to a TV, the TV can read the flag and convert to RGB correctly (since the display is always in RGB), but if you try to deliver an RGB whose black start at 64 and white peaks at 940, there's no way to flag it as "Limited", therefore it would almost definitely be displayed incorrectly unless a YUV conversion is applied or there's some system that is aware of this. This is probably the reason why the FFMpeg guys thought that, when you convert a Limited TV Range content to RGB, you don't want to "work with it", but you want to "deliver it" and, since it wouldn't be displayed correctly if it's linearly mapped, it will expand it! So, in the end, you were doing all correctly in the first place as your calculations assumed Full PC Range, the content was in Limited, but FFMpeg took care of it during the YUV to RGB conversion! So... I think I may have made you lose time on something that has already been addressed by a conversion you were doing, but hey, we both learned something new today, which is that FFMpeg expands Limited to Full in YUV -> RGB. Who would have thought that... I'll leave you to the Sakč: (fun fact I: the first time I tried sakč was in 2009 with my friends in an allegedly Japanese restaurant which was probably run by Chinese pretending to be Japanese; anyway I didn't like it that much.) (fun fact II: there are three glass in the picture I grabbed from a website 'cause one is for you, one is for me and the other is from whoever wants to grab it. I think StainlessS is more of a Beer guy, so let's see... xD) Last edited by FranceBB; 16th January 2021 at 14:32. |
||||
16th January 2021, 22:21 | #82 | Link |
hlg-tools Maintainer
Join Date: Feb 2008
Posts: 413
|
I just learned how to revert a range of commits in Git.
Since you're handing out drinks, I'll let it go. Hell, I have a Ryzen 3950X. I can do two movies at a time and make up for lost time. Last edited by wswartzendruber; 16th January 2021 at 22:36. |
24th January 2021, 06:57 | #83 | Link |
hlg-tools Maintainer
Join Date: Feb 2008
Posts: 413
|
I believe that as of this very moment, my tooling is complete. This includes a pgsmod utility I have written to crop and tonemap SUP subtitles.
The one thing I don't understand is why my pqstat utility returns higher MaxCLL values than what's in the metadata. Usually it's marginally higher. |
3rd March 2021, 07:05 | #84 | Link |
hlg-tools Maintainer
Join Date: Feb 2008
Posts: 413
|
pq2hlg and pqstat have now been consolidated under this single repository: https://github.com/wswartzendruber/hlg-tools. The original pq2hlg and pqstat repositories have been archived.
There will soon be a comprehensive HOWTO regarding converting 4K UltraHD Blu-rays to HLG for universal viewing. |
7th March 2021, 10:37 | #86 | Link | |
hlg-tools Maintainer
Join Date: Feb 2008
Posts: 413
|
Quote:
That's the best place I could think of to put it. |
|
Tags |
hdr, hlg, pq2hlg |
|
|