www.makemkv.com

Sure. I was just wondering how it differed from the current implementation in your script, since I haven't been able to find officially updated sources for madMeasurementAnalyzer.exe and madMeasureHDR.exe. Well, the madvr data is the same regardless of the tool you use to read it. By the way, talki...

LV8HD wrote: ↑

Tue Mar 31, 2026 1:10 pm

RESET_9999 wrote: ↑

Tue Mar 31, 2026 1:07 pm

useless since a free version of the official Dolby algo (cm_analyze) can be used to create proper cmv4.0 metadata.

Yeah, but what about HDR analysis with MadVR integration?

nothing new here, been available in my scripts for years.
DoVi_Scripts\tools\madMeasurementAnalyzer.exe

LV8HD wrote: ↑

Tue Mar 31, 2026 12:56 pm

@RESET_9999 what do you think about https://github.com/tinof/hdr-analyze?

useless since a free version of the official Dolby algo (cm_analyze) can be used to create proper cmv4.0 metadata.

Yes, you need to remove DV if it’s a P8 hybrid WEB-DL. Only dual-layer, dual-track P7 is valid for Blu-ray discs with DV. A Blu-ray structure with P8 HEVC might still play on some Blu-ray players, but I’ve never tested it.
If the WEB-DL is cropped, the Blu-ray structure may not be valid either.

Hi everyone, my father has a Sony x700U and I've tried to play some of the mp4 test files from the "Dolby_Vision_Stuff" google sheet. The one that works is "FEL TEST ST DL P7 CMV4.0 4000nits V4", and I can see the text. However, when I try to play some of the others, such as &qu...

This isn't true. 422 12 bit works just fine. I don't care what the LG claims. SOURCE: Amlogic MBox Meson Ref IN TX0: 1080P23.976 74MHz 422 BT709 12b This is why having a VRROOM is useful. Yeah, if the HDFury device reports 12-bit, I trust that more than LG’s reporting. On my end, CEC no longer work...

you should use auto 444 12bit. There might be a bug with the 422 output and you should ask avdvplus about it since i know he made some changes about 422 in his build.

on mine auto = 444 12bit
422 = 8bit

That's what I thought. Thank you for confirming.

thank you, great work!

I’ve ported DoViBaker to VapourSynth, making it compatible with macOS on Apple Silicon in the process. I’ve also significantly optimized it (LUT implementation, code cleanup, and optional use of VapourSynth’s internal resizers). I plan to make it public soon (once I’ve improved the build process). ...

LV8HD wrote: ↑

Tue Jan 27, 2026 8:31 am

But as I pointed in the previous post, can I generate a new RPU with dynamic L1, CMv4.0 and transfer L2 trims from the original RPU?

no

Simple question but probably not a simple answer. I want to rip DV FEL files and keep FEL. Staxrip converts to 8.1 but doesn't keep FEL. I understand with Dovibaker it is possible? But although I've used Avi/Vapoursynth a lot, I'm still not really an expert at working out how to import files to the...

Wouldn't it be wrong to keep retail? The movie was mastered at 4000 nits; proven by a HDR analysis, MaxCLL: 4427 nits, MaxFALL: 2325 nits. On the other hand, Dolby Vision L1 is statically capped at 650 nits. Doesn't this mean that even if a TV hypothetically supported up to 4427 nits, using Dolby V...

I dont know, but you can always test the original and generated tone mapping with workflow 7-4 and decide which one you prefer.

LV8HD wrote: ↑

Mon Jan 26, 2026 3:20 pm

@RESET_9999 given this:
Since L2 trims are not static, what is the best practice here: generating new metadata or keeping retail RPU?