So I did a quick test with my usual example files. All the targets are identical, except Blade Runner 2049 (225nits instead of 200nits), which is fine.
Well done, this works great!
And thanks again
for implementing this target nits field.
Here is my simplified algo now:
if (hdr) and (srcWidth <= 3840) and (srcHeight <= 2160) and (fps > 31) "BT2390 Mode 10 (Fast)"
else if (hdr) "HDR BT2390"
else "Send Metadata SDR"
[EDIT: I have a default target of 401nits in my single HDR BT2390 profile, to make sure that a different target displayed in the OSD comes from the measurements file.]
A few comments:
1) It looks like the utility still doesn't skip a file when an up-to-date measurement already exists. Did you run out of time to implement this?
2) Performance is still poor here, both from the MBP and the HTPC. It takes around 4'10'' for 22 files on the MBP, 6'10'' on the HTPC, so 12-18s per file.
3) Please could you use 107nits instead of 100nits as the baseline for my algo? That what I've used most and my actual nits target if I have more brightness on tap. As you know, that's the Dolby Cinema target for diffuse white and a realistic target for many users. It's great that we can adjust the algo so easily by indicating the actual peak brightness in the utility. Also you might want to specify in your notes that my algo is designed for 107nits peak brightness in a dedicated room (bat loft, 0nits ambient light), as the environment influences the values. Someone with 107nits actual peak but some ambient light will probably want to "lie" and specify a lower actual nits value. I'll try to add something about this in the post related to my algo. I'll add a link to your latest utility as well.
4) It might be worth adding Dexter's latest algo posted above. It's quite similar to mine but brighter for dimmer titles, and a bit more contrasty for The Meg. So it might suit some with a different environment and more brightness to start with. Its actual peak brightness is 212nits. I attach the measurements comparing my algo, Dexter's algo and the implementation in your utility (Manni01-S column) for my usual examples if anyone wants to take a look.
Keep up the good work! I'll try to do more visual tests with the new thresholds using 107nits actual peak brightness as a reference and I'll let you know if there are any adjustments to the algo.
Very curious to see which algo of your own you're going to come up with...
, do you have a new build coming up, and are there any changes to be expected for MadMeasureHDR? If there are no changes to MadMeasureHDR, I'll run the measurements for the rest of my titles over the next few days, otherwise I'll wait for the new build.