Page 701 of 756

Re: Dolby Vision now possible through MP4 Mux.

Posted: Thu Dec 26, 2024 6:09 pm
by ragico
Thank you for explaining

Re: Dolby Vision now possible through MP4 Mux.

Posted: Fri Dec 27, 2024 12:25 am
by deadchip12
RESET_9999 wrote: Thu Dec 26, 2024 4:26 pm Yes, it will be an L1 plot.
The only way to get an HDR plot is with a base-layer video input. An RPU is just metadata, the script can only plot them.
I see. So I can only compare hdr plots (as well as screenshot brightness) if I run 6-2 on the original web video file. Since that seems to take too long, I may as well trust you and inject your rpu file from google drive instead. Will later try the new version of the tool to see if it runs a lot faster though.

Re: Dolby Vision now possible through MP4 Mux.

Posted: Fri Dec 27, 2024 11:00 am
by darrrkmanxxx
Is there a way to adjust cmv4.0 in the RPU to better match peak brightness of a TV panel?

Re: Dolby Vision now possible through MP4 Mux.

Posted: Fri Dec 27, 2024 12:16 pm
by deadchip12
When we use workflow 7-2 to generate screenshots of web and bluray versions and compare their brightness, do we need to view the screenshots on an hdr screen, or sdr should suffice?

Re: Dolby Vision now possible through MP4 Mux.

Posted: Fri Dec 27, 2024 2:11 pm
by RESET_9999
darrrkmanxxx wrote: Fri Dec 27, 2024 11:00 am Is there a way to adjust cmv4.0 in the RPU to better match peak brightness of a TV panel?
the rpu metadata are here to tell your TV about the content brightness. Your TV won't tone map it accurately if you lie about it.

You can only control the aggressiveness of the tone mapping with the analysis tunings. Lower L1 values mean less tone mapping resulting in a brighter image but potentially clipped.
Higher values mean more tone mapping resulting in a darker image without clipping in highlights. L1 Values under your TV internal brightness target (in tv-led) or the edid target (in LLDV), disable the TV tone mapping, and the content is displayed as it is, as intended...

I did a complete analysis tunings comparisons here: https://slow.pics/c/OA0pupEN
old cmv4.0 legacy, match almost 1:1 the peaks of workflow 6-2 (madvr plot)

Re: Dolby Vision now possible through MP4 Mux.

Posted: Fri Dec 27, 2024 2:13 pm
by RESET_9999
deadchip12 wrote: Fri Dec 27, 2024 12:16 pm When we use workflow 7-2 to generate screenshots of web and bluray versions and compare their brightness, do we need to view the screenshots on an hdr screen, or sdr should suffice?
Always HDR image, it doesn't matter if you watch it on an SDR display because you still see the real difference.
SDR tone-mapping is the worst invention ever and is totally misleading and useless.

Re: Dolby Vision now possible through MP4 Mux.

Posted: Fri Dec 27, 2024 2:49 pm
by darrrkmanxxx
RESET_9999 wrote: Fri Dec 27, 2024 2:11 pm
darrrkmanxxx wrote: Fri Dec 27, 2024 11:00 am Is there a way to adjust cmv4.0 in the RPU to better match peak brightness of a TV panel?
the rpu metadata are here to tell your TV about the content brightness. Your TV won't tone map it accurately if you lie about it.

You can only control the aggressiveness of the tone mapping with the analysis tunings. Lower L1 values mean less tone mapping resulting in a brighter image but potentially clipped.
Higher values mean more tone mapping resulting in a darker image without clipping in highlights. L1 Values under your TV internal brightness target (in tv-led) or the edid target (in LLDV), disable the TV tone mapping, and the content is displayed as it is, as intended...

I did a complete analysis tunings comparisons here: https://slow.pics/c/OA0pupEN
old cmv4.0 legacy, match almost 1:1 the peaks of workflow 6-2 (madvr plot)
Thanks for explaining. How to interpret those? Is the madvr plot the best, because it has the most dynamics?
If I do the madvr measuremnt, I adjust cmv4.0 when I generate from madvr file with dovi_tool ,e.g.
Jumanji:

Code: Select all

Mastering display luminance              : min: 0.0050 cd/m2, max: 4000 cd/m2
Maximum Content Light Level              : 3938 cd/m2
Maximum Frame-Average Light Level        : 676 cd/m2
https://github.com/quietvoid/dovi_tool/ ... cmv40.json

Code: Select all

{
    "cm_version": "V40",
    "length": 10,
    "level6": {
        "max_display_mastering_luminance": 4000,
        "min_display_mastering_luminance": 50,
        "max_content_light_level": 3938,
        "max_frame_average_light_level": 676
    }
}
It this correct or is there something else to adjust?

Soemtimes Maximum Content Light Level, Maximum Frame-Average Light Level are missing, what should I enter then?

Re: Dolby Vision now possible through MP4 Mux.

Posted: Fri Dec 27, 2024 2:59 pm
by RESET_9999
Thanks for explaining. How to interpret those? Is the madvr plot the best, because it has the most dynamics?
If I do the madvr measuremnt, I adjust cmv4.0 when I generate from madvr file with dovi_tool ,e.g.
No, madvr generated metadata (3-2) is the worst and not really suited for DV playback. Also, Madvr scene cut detection is not very good. It's quite sensitive to flashes/explosions/fast movement and can sometimes miss obvious scene cuts. The best dv metadata generation is one of the analysis tunings using Davinci Resolve. I prefer the ''balanced tuning'' which is the dovi_scripts default in workflow 3-1

It this correct or is there something else to adjust?
Soemtimes Maximum Content Light Level, Maximum Frame-Average Light Level are missing, what should I enter then?
it doesn't matter, Level 6 metadata are 100% useless.

Re: Dolby Vision now possible through MP4 Mux.

Posted: Fri Dec 27, 2024 6:41 pm
by darrrkmanxxx
RESET_9999 wrote: Fri Dec 27, 2024 2:59 pm
Thanks for explaining. How to interpret those? Is the madvr plot the best, because it has the most dynamics?
If I do the madvr measuremnt, I adjust cmv4.0 when I generate from madvr file with dovi_tool ,e.g.
No, madvr generated metadata (3-2) is the worst and not really suited for DV playback. Also, Madvr scene cut detection is not very good. It's quite sensitive to flashes/explosions/fast movement and can sometimes miss obvious scene cuts. The best dv metadata generation is one of the analysis tunings using Davinci Resolve. I prefer the ''balanced tuning'' which is the dovi_scripts default in workflow 3-1

It this correct or is there something else to adjust?
Soemtimes Maximum Content Light Level, Maximum Frame-Average Light Level are missing, what should I enter then?
it doesn't matter, Level 6 metadata are 100% useless.
got it, do you have a video by chance on how to generate metadata with Davinci Resolve?

Re: Dolby Vision now possible through MP4 Mux.

Posted: Fri Dec 27, 2024 7:31 pm
by SamuriHL

Re: Dolby Vision now possible through MP4 Mux.

Posted: Sat Dec 28, 2024 12:50 am
by deadchip12
@RESET_9999

I saw you just updated the Transfer CMv 4.0 Dolby Vision from WEB streaming to Profile 7 tutorial video. Would be great if you can do the same for the ADD Original Dolby Vision from WEB STREAMING to HDR10 Bluray Rip (P8 Hybrid) video as well, and a tutorial on how to use the new GUI in the latest dovi script version.

Re: Dolby Vision now possible through MP4 Mux.

Posted: Sat Dec 28, 2024 1:27 pm
by RESET_9999
the p8 hybrid tuto doesnt really need to be updated... Nothing changed...
A couple of things were automated in the transfer cmv4.0 workflow so that's why I redid this one.

Re: Dolby Vision now possible through MP4 Mux.

Posted: Sat Dec 28, 2024 7:36 pm
by darrrkmanxxx
RESET_9999 wrote: Sat Dec 28, 2024 1:27 pm the p8 hybrid tuto doesnt really need to be updated... Nothing changed...
A couple of things were automated in the transfer cmv4.0 workflow so that's why I redid this one.
How can I tell if a device supports cmv4.0?

Re: Dolby Vision now possible through MP4 Mux.

Posted: Sat Dec 28, 2024 11:41 pm
by RESET_9999
just try one of the cmv4.0 rpu test files

https://drive.google.com/drive/u/1/fold ... eyGDQEGJuF

Re: Dolby Vision now possible through MP4 Mux.

Posted: Tue Dec 31, 2024 12:59 am
by voodoomamajuju
@RESET_9999 Just wanted to say thanks for the Dolby_vision_stuff sheet but I just noticed that the link is broken. Is the sheet hosted somewhere else now? Thanks again!