www.makemkv.com

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.

update your tool folder.

RESET_9999 wrote: Thu Jan 02, 2025 11:07 pm 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?

@RESET_9999 if I try using the latest version of madVR the workflow 6-2 doesn't work. Why is this?

The version I downloaded comes from https://www.videohelp.com/software/madVR

darrrkmanxxx wrote: Fri Jan 03, 2025 9:38 am Can I ignore it or should I try to remove it form the metadata?

run the xml/rpu in 6-2, it will tell you the first frame of the shot where this spike happens. I suspect there is a glitch in your video.

@RESET_9999 if I try using the latest version of madVR the workflow 6-2 doesn't work. Why is this?

The version I downloaded comes from https://www.videohelp.com/software/madVR

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.

RESET_9999 wrote: Fri Jan 03, 2025 2:31 pm

darrrkmanxxx wrote: Fri Jan 03, 2025 9:38 am Can I ignore it or should I try to remove it form the metadata?

run the xml/rpu in 6-2, it will tell you the first frame of the shot where this spike happens. I suspect there is a glitch in your video.

your were right! It was a glitch. A real cool way btw to verify, thank you so much.

@RESET_9999
Another question:

I have a remux which is profile 8, but has only cmv2.9
L1: https://drive.google.com/file/d/1jALIu_ ... p=drivesdk

Should I transfer thle levels (like in your profile 7), or just go straight for cm_analyze?
What would be superior?

if there's a retail cmv4.0 RPU from streaming yes. Otherwise, it depends on whether the cmv2.9 rpu has trims or not.

RESET_9999 wrote: Fri Jan 03, 2025 11:49 pm Otherwise, it depends on whether the cmv2.9 rpu has trims or not.

Could you elaborate on this? Which workflow to verify the web rpu has trims that the bluray does not?

(6-4) to plot the trims

RESET_9999 wrote: Sat Jan 04, 2025 12:24 am (6-4) to plot the trims

hallo reset is it good enough SEVEN with freman and pit from framestore hybrid 8 profile dolby vision or it s aggain fail from the framestore group and it s in cm4.0 or cm2.9 ?

RESET_9999 wrote: Sat Jan 04, 2025 12:24 am (6-4) to plot the trims

What exaclty should there be?
I used on workflow 6-4 on the example mentioned below (P8 Remux) here are the results:
https://drive.google.com/drive/folders/ ... sp=sharing

If you have a few can you please take a look and myabe point out exaclty what should I look for and if this is worth of transferring genarted metadata?

Also how do I verify if FEL was baked in?

ps hope my questions will get less annoying once I start getting it

valington wrote: Sat Jan 04, 2025 11:45 am hallo reset is it good enough SEVEN with freman and pit from framestore hybrid 8 profile dolby vision or it s aggain fail from the framestore group and it s in cm4.0 or cm2.9 ?

it looks ok.
cmv4.0

darrrkmanxxx wrote: Sat Jan 04, 2025 12:41 pm What exaclty should there be?
If you have a few can you please take a look and myabe point out exaclty what should I look for and if this is worth of transferring genarted metadata?

You can never transfer a generated cmv4.0 block into an original/retail cmv2.9 rpu
if the original cmv2.9 doesn't have any trims (or static ones), then you can completely discard the rpu and inject your generated cmv4.0 rpu

Also how do I verify if FEL was baked in?

compare the encode with the original P7 rip in 7-2

You can never transfer a generated cmv4.0 block into an original/retail cmv2.9 rpu
if the original cmv2.9 doesn't have any trims (or static ones), then you can completely discard the rpu and inject your generated cmv4.0 rpu

Sure, but what should I look for in my example. There are PNGs with L2 titles and there's some stuff in the graphs. Are those the trims?