Dolby Vision now possible through MP4 Mux.

[kazuma]

what does mean tv-led exactly? what is the benefit?

[RESET_9999]

it means it's the TV that does the tone mapping and metadata processing. It's more accurate.

[LV8HD]

@RESET_9999 should I generate a new RPU?

[RESET_9999]

No. Some colorists prefer static L1 with dynamic trims.

[LV8HD]

No. Some colorists prefer static L1 with dynamic trims.

I see, thanks

[deadchip12]

I'm trying to generate the hdr10 brightness plot using workflow 6-2 and see these lines. What do they mean?

[RESET_9999]

install python:

https://apps.microsoft.com/detail/9pjpw ... n-US&gl=US

[deadchip12]

install python:

https://apps.microsoft.com/detail/9pjpw ... n-US&gl=US

Thanks. What about the below warnings? I just used workflow 1 to inject DV web version's RPU to hdr10 bluray version of harry potter sorcerer stone.

[RESET_9999]

you can ignore it.
These warnings are new in the latest metafier.exe version...I'm not sure what they mean but they don't matter because metafier is just an additional metadata check.

[deadchip12]

you can ignore it.
These warnings are new in the latest metafier.exe version...I'm not sure what they mean but they don't matter because metafier is just an additional metadata check.

What are the differences between the MKV, TS, and MP4 version of the DoVi_Scripts bat file?

I normally just downloaded the DoVi_Scripts_MKV.bat and ran it fine, but today when I tried using workflow 6-2 to measure brightness of this file Kingdom.Of.The.Planet.Of.The.Apes.2024.2160p.WEB-DL.DV.P5.ENG.LATINO.DDP5.1.Atmos.H265.MP4-BEN.THE.MEN.mp4, it has run for hours and created a temp folder of over 100GB. Something went wrong.

[RESET_9999]

madvr cannot measure profile 5 video directly so the script converts it to prores first.

the only difference between the script versions is the muxing container

[deadchip12]

madvr cannot measure profile 5 video directly so the script converts it to prores first.

It also takes that long on your end? I had been waiting for hours and it was still running. And the temp folder size was alarming.

Btw, I'm still having trouble with kingdom of the planet of the apes movie. I downloaded your web rpu from the google drive folder, ran workflow 6-2 to get its hdr plot and compare it against the plot of the bluray hdr10 version to see if they are similar. They are not.

web rpu


bluray version

[RESET_9999]

Btw, I'm still having trouble with kingdom of the planet of the apes movie. I downloaded your web rpu from the google drive folder, ran workflow 6-2 to get its hdr plot and compare it against the plot of the bluray hdr10 version to see if they are similar. They are not.

yes, there are many blended shots(the colorist manually merged shots together) but it should be fine and the values are mostly under 600-500nits so they shouldn't matter for most TVs.

It also takes that long on your end? I had been waiting for hours and it was still running. And the temp folder size was alarming.

yes, it runs about 24fps(1x) and the large HDD usage is also normal because prores is a lossless codec.
But in the latest beta, I improved the speed about 2times depending on your CPU. On my end, it now runs at 50fps(2.2x)
https://drive.google.com/file/d/128gq8a ... drive_link

[deadchip12]

Btw, I'm still having trouble with kingdom of the planet of the apes movie. I downloaded your web rpu from the google drive folder, ran workflow 6-2 to get its hdr plot and compare it against the plot of the bluray hdr10 version to see if they are similar. They are not.

yes, there are many blended shots(the colorist manually merged shots together) but it should be fine and the values are mostly under 600-500nits so they shouldn't matter for most TVs.

The thing is in one of your earlier posts you showed me the hdr plot of the web version versus the bluray version for this movie and they looked very similar.
https://slow.pics/s/wQzSIwSH

[RESET_9999]

it's because both plots are a measurement of the base layer with workflow 6-2.
RPU L1 plot is different because it's done by the colorist and the dolby algorithm.