[DoVi_Scripts] Multi-Function Scripts for Dolby Vision processing and a lot more...

[SamuriHL]

Yea that makes sense. Given what you said about black crush there's no getting around a proper calibration to fix that. But I suspect that thing is going to ROCK once it's broken in and calibrated. They're finally getting closer to what I wanted to see for my next panel. I'm curious if they've improved on bt.2020 support in terms of percent covered.

[TR-7970X]

I'm pretty impressed with my "old" C4 65" LG, although I haven't bothered to calibrate it....it's SO much better that the 2018 55" I had (which died, btw, the screen just went black, one night, and that's it)

[Kontrarian]

Yeah, no point in calibrating a panel in it's first 200 hours, that's for sure.

My C8 is still hanging in there!

[Gatorman3385]

DoVi_Scripts (8-2-3) is running DoviBaker on a P7 MEL to ProRes. Is this the intended behavior?

[Kuler087]

nop...
fix: https://drive.google.com/file/d/128g...usp=drive_link

[en6ads]

Hi all,

Are the colorist's manual Level 2 / Level 8 adjustments from Level 1 (a Dolby algorithm) stored separately in the RPU?

If I use CPM A14 with the updated skins, in the PPI page can I see the Level 1 values, the Level 2/8 adjustments from Level 1, then the combined result?

I'd like to know what the colorist's are doing in Level 2/8 and how they differ from what Dolby calculates.

Thank you.

[Kuler087]

CPM OSD info is only for L1/L5 and will not display the trims values. How strong the trim's effect is will depend on your display target brightness.
DoVi_scripts has a workflow(7-4) that lets you see the L1 mapping alone and the L1+L2(or L8/L3) mapping. I already created many examples here:
https://drive.google.com/drive/folde...iSlcdMiy2ka0mf

I also did a couple of L1 and L2/L8 trims test files here: https://drive.google.com/drive/u/1/f...rk-Ifx6vRYDEfs

Note that there will be a difference between cmv2.9 and 4.0. I just did some L1 mapping tests about it on my new G5 here:
https://docs.google.com/spreadsheets...gid=1289366200

[en6ads]

Originally Posted by Kuler087

CPM OSD info is only for L1/L5 and will not display the trims values. How strong the trim's effect is will depend on your display target brightness.
DoVi_scripts has a workflow(7-4) that lets you see the L1 mapping alone and the L1+L2(or L8/L3) mapping. I already created many examples here:
https://drive.google.com/drive/folde...iSlcdMiy2ka0mf

I also did a couple of L1 and L2/L8 trims test files here: https://drive.google.com/drive/u/1/f...rk-Ifx6vRYDEfs

Note that there will be a difference between cmv2.9 and 4.0. I just did some L1 mapping tests about it on my new G5 here:
https://docs.google.com/spreadsheets...gid=1289366200

Thank you. I've submitted a feature request to CPM github. I would like to see in the PPI osd if level 2 / 8 trims exist, and if so what are they. Also level 3 but how often does that get used?

[Kuler087]

Most movies are trimmed at least at 100nits and the other target gets interpolated from those adjustments.
L3 is auto-generated and stores the mid-offset adjustments.

Not sure how CPM will add the trim's value in the OSD. That would take a lot of space since the cmv4.0 workflow auto-generated L2 trims at 100,600 and 1000nits (to fix the buggy cmv2.9).
that's a lot of data to add, EG:

"Level2": {
"target_max_pq": 2081,
"trim_slope": 1611,
"trim_offset": 2023,
"trim_power": 1380,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 2048,
"ms_weight": 2048
}
},
{
"Level2": {
"target_max_pq": 2851,
"trim_slope": 2066,
"trim_offset": 2048,
"trim_power": 1959,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 2048,
"ms_weight": 2048
}
},
{
"Level2": {
"target_max_pq": 3079,
"trim_slope": 2049,
"trim_offset": 2048,
"trim_power": 2046,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 2048,
"ms_weight": 2048
}
]
},
"cmv40_metadata": {
"num_ext_blocks": 6,
"ext_metadata_blocks": [
{
"Level3": {
"min_pq_offset": 2048,
"max_pq_offset": 2048,
"avg_pq_offset": 1660
}
},
{
"Level8": {
"length": 10,
"target_display_index": 1,
"trim_slope": 2060,
"trim_offset": 2048,
"trim_power": 2009,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 2048,
"ms_weight": 2048
}
},
{
"Level8": {
"length": 10,
"target_display_index": 28,
"trim_slope": 2048,
"trim_offset": 2048,
"trim_power": 2048,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 2048,
"ms_weight": 2048

[en6ads]

I'm sure they can fit L2/L8 and L3 data on the screen somewhere! Might get busy, but there's room.

[Kuler087]

I'd be surprised if he accepted your request because 99.999999% of users wouldn't even understand the data. Do you understand the data I just posted?
The trims metadata is not like L1, which is easy to understand because it just tells you about the scene's max, average, and minimum brightness.

If you want to see what the colorist did, just watch the tons of samples I posted or create a new sample from any frame of any movie using workflow 7-4.

EG:

[en6ads]

What's the best Windows player currently for correct playback of Dolby Vision mkv rips on a laptop that has a HDR OLED panel (Samsung SDC419D, 10bit 450 nits) and official DV support? Most of my rips are profile 7 cm2.9 Mel and fel. I've seen your YouTube comparing Energy Player and Madvr but that was a while ago. Use case is just for travel. Don't worry I have a couple of Ugoos for home! Thank you.

[en6ads]

Originally Posted by Kuler087

I'd be surprised if he accepted your request because 99.999999% of users wouldn't even understand the data. Do you understand the data I just posted?
The trims metadata is not like L1, which is easy to understand because it just tells you about the scene's max, average, and minimum brightness.

If you want to see what the colorist did, just watch the tons of samples I posted or create a new sample from any frame of any movie using workflow 7-4.

EG:

I'm not a colorist and I've never used any of Dolby's trim controls. I know level 2 and 8 are per target as you say, Lift, Gamma and Gain, with cm4 increasing that to 21 total controls (sounds complicated!).

I'll go through your examples splitting out the levels - thank you for sharing.

I just feel like if CPM is only displaying level 1, then that's not the whole story. If there's a meaningful way to expose RPU L2 (cm2.9) and L3, L8 (cm 4.0), I'd like to see it.