Originally Posted by ausvette
I've been using madmeasurehdr for a long time. But development seems to have finished and the thread seems to be dead.
Is the dynamic toning mapping superior in the latest madvr beta to the madmeasurehdr method?
This thread isn’t dead, it is only active when madshi needs feedback on a specific build. He is currently busy working on getting the Envy ready for launch, so this thread is paused. It might get some action very soon...
The live algo works very well 99% of the time. Apart from a few blink-it-and-miss-it situations only visible if you watch the content frame by frame, the measurement files might only help with the flicker present with contrast enhancement algos that are too strong in some situations. This is not an issue if you use a conservative algo, such as Neo XP Log conservative (the one I use). Others can use stronger algos in their setup, but they flicker in mine (110 peak nits).
If madshi manages to “look into the future” for a few frames, which is an improvement that has been discussed for the live algo, it will make measurements files even less relevant, so I’d rather see this implemented when the time comes.
Anyway, I don’t miss measurements files and it makes sense for madshi to keep them disabled for now, as he needs feedback to improve the live algo even further, not to improve measurement files results for people who never use the live algo, hence never help to improve it.
IMO the files were useful when the live algo had big shortcomings, but it’s not the case anymore, provided your config is powerful enough, as enabling the files free a bit of resouces for those who were borderline.
So give the live algo a try, and let us know where you think it still falls short compared to measurement files.
That would be useful feedback!