yes all cmv4.0 movies have cmv2.9 fallback metadata. Your G3 + CE device should support cmv4.0.
Don't I have to add a 800nit trim to the RPU to get the most brightness out of it?
All the trims(100-600-1000) work together and the metadata can be extrapolated to any target brightness.
Cool, what would be the best way to create dv from hdr10 cm_analyzer or davinci resolve?
My primary device is still the cmv2.9 Philips TV 65oled934.
What I want is to create cmv4.0 DV Profile 8 with most compatibility for my my old philips tv while future proof for device like LG G3 and up as I share content with multiple deolby vision devices.
Cool, what would be the best way to create dv from hdr10 cm_analyzer or davinci resolve?
CM is 100% automated but can be slow and relies on madvr for the scene-cut detection
Resolve is not automated but is much faster and has slightly better scene-cut detection.
Cool, what would be the best way to create dv from hdr10 cm_analyzer or davinci resolve?
CM is 100% automated but can be slow and relies on madvr for the scene-cut detection
Resolve is not automated but is much faster and has slightly better scene-cut detection.
got you, I trying out both now. I'm on macos, so I'm running windows in parallels and davinci on macos.
what about comatibility with cmv2.9, any difference there?
What is the use case for "Transfer RPU levels" workflow 2-3?
Do all the checks as I did in the video and find out.
This title is probably missing(IIRC) from my ''okay to transfer'' list because I deleted the old sheet by mistake.
I found a bug in the latest version of workflow 6-2 when using the CLI. When calculating the MaxCLL and MaxFALL threshold percentages, the CLI reports an "unrecognized arguments: -m over" error, and the percentages all read "0" on the plot. "HDR10 Plotter" works, however, in the GUI.
Do all the checks as I did in the video and find out.
This title is probably missing(IIRC) from my ''okay to transfer'' list because I deleted the old sheet by mistake.
thats great news! Thanks for letting me know.
Meanwhile, I ran the workflow 3-1 on my windows machine and unfortunately it took forever since I have an AMD RX 6900 XT (no CUDA) , which I plotted afterwards and now there a 10000nit spike: https://drive.google.com/file/d/1zNmTGD ... sp=sharing
Can I ignore it or should I try to remove it form the metadata?
I don't know; I don't use the time-limited beta build. When they expire, they can break madmeasureHDR.exe.
I use the version included in the tool pack, the latest beta version before the time-limited ones.