Dolby Vision now possible through MP4 Mux.

[deadchip12]

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.

I used workflow 6-2 too. The input file was your web rpu.

Are you saying if i use workflow 6-2 with your web rpu, it will generate the L1 plot, not the hdr plot?

[RESET_9999]

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.

[ragico]

I just used workflow 1 to inject DV web version's RPU to hdr10 bluray version of harry potter sorcerer stone.

What is the benefit of this RPU replacement?

[RESET_9999]

What is the benefit of this RPU replacement?

what? replacement?

[ragico]

I will better explain my question.
Example the Harry Potter movie cited by @deadchip12
I have the 8.1 version made using rpu from you.
Then there is a P5 version on the web.
If I replace your rpu by the one from the P5 is there any benefit?

[RESET_9999]

When both Generated P8 and a retail WEB P5 are available on my Google Drive, it's because the retail P5 rpu is cmv2.9 without dynamic L2 trims so the cmv4.0 generated RPU is better.

[ragico]

Thank you for explaining

[deadchip12]

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.

[darrrkmanxxx]

Is there a way to adjust cmv4.0 in the RPU to better match peak brightness of a TV panel?

[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?

[RESET_9999]

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)

[RESET_9999]

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.

[darrrkmanxxx]

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?

[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.

[darrrkmanxxx]

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?