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. Domains: forum.doom9.org / forum.doom9.net / forum.doom9.se |
|
|||||||
![]() |
|
|
Thread Tools | Search this Thread | Display Modes |
|
|
#61 | Link |
|
Registered User
Join Date: Jan 2019
Location: Canada
Posts: 583
|
No, just this specific frame/shot.
__________________
LG C2 OLED | GitHub Projects |
|
|
|
|
|
#62 | Link | |
|
Registered User
Join Date: Nov 2004
Location: Poland
Posts: 2,869
|
Quote:
Chroma subsampling is huge enemy of MaxCLL calculation (bigger than compression most likely). I downloaded Netflix Sparks 1K TIFF master. And it was 1K when measured in Resolve. When exported as 12bit 444 lossless jpeg2000 it was still 1K. ProResXQ was 1085, where ProResHQ was 4208 (straight from TIFF export in Resolve and measured back in Resolve)!!! It also depends on content nature and also which tool you measure with. It should be all calculated in 32bit float as it quickly generates errors on rounding (PQ curve is strong so errors propagate heavily to final nits). Last edited by kolak; 11th July 2022 at 19:38. |
|
|
|
|
|
|
#63 | Link |
|
Registered User
Join Date: Nov 2004
Location: Poland
Posts: 2,869
|
Ok- makes more sense.
Best way to test all of it is to download eg. Netflix Sparks 1K nits TIFF sequence. This is 1K nits MaxCLL. Then you can create different formats from it and analyse them and compare to reference value. If you start with compressed title you are bit blind as you have no idea what it should be. Last edited by kolak; 11th July 2022 at 19:32. |
|
|
|
|
|
#65 | Link | ||
|
Broadcast Encoder
Join Date: Nov 2013
Location: Royal Borough of Kensington & Chelsea, UK
Posts: 3,374
|
Hi Tom,
thanks for the function, I've been using it for several years and it works. Up until now I only really used it manually so I didn't mind to look at the various results and scroll down to the bottom to get the final one, however I'm now including it in a workflow to measure the values and write both MaxCLL and MaxFALL with a bitstream filter on already encoded files. This means that I'll be processing those in batch and given that I was only really interested in the last value, I took the chance to add a new parameter called LogIntermediateStats. It's a boolean and it can be specified by the user to signal whether all values need to be reported (i.e update the .txt with the values every 100 frame, which is the current behavior) or just the final calculated value. In other words, this: Code:
LWLibavVideoSource("Test_Source.mov")
ConvertToRGB64(matrix="Rec2020")
MaxCLLFind(maxFallAlgorithm=0, LogIntermediateStats=true)
Code:
LWLibavVideoSource("Test_Source.mov")
ConvertToRGB64(matrix="Rec2020")
MaxCLLFind(maxFallAlgorithm=0)
Quote:
while if we set the new boolean explicitly to false like this: Code:
LWLibavVideoSource("Test_Source.mov")
ConvertToRGB64(matrix="Rec2020")
MaxCLLFind(maxFallAlgorithm=0, LogIntermediateStats=false)
Quote:
Let me know if you're ok with this new parameter. I've opened a pull request here: https://github.com/TomArrow/MaxCLLFindAVS/pull/15 just in case, but feel free to change/modify anything. ![]() In the meantime, in case anyone wants to give it a go, I've made some temporary builds here: https://github.com/FranceBB/MaxCLLFi...leases/tag/0.4 and, before anyone says anything, yes, it also works on Windows XP!
|
||
|
|
|
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|