Dolby Vision now possible through MP4 Mux.

[RESET_9999]

I think the major selling point of DV previously or at the moment is L1 data compare to HDR10.

Actually the best thing about DV is the trim pass because they can control how it will look on more display.
L1 only is like HDR10plus or madvr HDR dynamic tonemaping, it basically just compress the highlights.

[RESET_9999]

The logical leap, if any, is that if only the 100-nit L2 (or L8) trim exists, the engine still uses that to interpolate/interpret and adjust the image for higher-nits and variety of displays.

yep, I think that is what's happening. The 100nits trim response is clearly different on my 400 and 800 monitor

[susanstone2022]

The logical leap, if any, is that if only the 100-nit L2 (or L8) trim exists, the engine still uses that to interpolate/interpret and adjust the image for higher-nits and variety of displays.

yep, I think that is what's happening. The 100nits trim response is clearly different on my 400 and 800 monitor

Have you asked Dolby directly on how the trim data are used or supposed to be used during playback? Can you please ask if you have not?

[RESET_9999]

They haven't responded to my L2 trim offset being ignored in TV-LED yet so I don't want to open a new ticket already but I do want to ask them what happens with positive lift for 1000nits RPU with 1000+nits TV.
This is the only remaining thing that doesn't make sense in my mind. Everything else is pretty clear.

[RESET_9999]

1. Does MakeMkv rip DV tracks as dual track dual layer, or single track dual layer profile 7?
2. Related to above, are there options for how MakeMKV rips DV layers I should be aware of?
3. I believe that to improve compatibility of DV files, I need to convert profile 8 and there are tools available to do this (dovi_tool)
4. I've read that removing FEL in that process is a good thing as it isn't used by players?

1- single track dual layer P7
2- idk
3- yes if your device doesn't support fel, P8 is better.
4- same as response as 3 but be aware that some movies require FEL to be displayed correctly. see: https://docs.google.com/spreadsheets/d/ ... edit#gid=0

[RESET_9999]

I tested the AppleTV , Shield and x700, the behavior was the same:

on the C2, 100nits L2 or L8 has an effect if 600-1000trims is not 2048 and the effect is much more pronounced with lower nits TV.

[susanstone2022]

I tested the AppleTV , Shield and x700, the behavior was the same:

100nits L2 or L8 has an effect if no 600-1000trims exist and the effect is much more pronounced with lower nits TV.

Does the effect ever phase out on higher nits TV?

[RESET_9999]

Does the effect ever phase out on higher nits TV?

I guess and it depends on how strong the L2 trim is and a 4000nits RPU probably has a bigger effect. I only tested 1000nits RPU and in TV-LED on C2 810nits, Vizio 600nits and Samsung 400nits. I'll check with higher edid in LLDV this weekend.

[susanstone2022]

Does the effect ever phase out on higher nits TV?

I guess and it depends on how strong the L2 trim is and a 4000nits RPU probably has a bigger effect. I only tested 1000nits RPU and in TV-LED on C2 810nits, Vizio 600nits and Samsung 400nits. I'll check with higher edid in LLDV this weekend.

This is the part I am curious.
for content mastered at 1000nits, the final content after processing should be no more than 1000nits (or a little more like 1200 or 1300nits for peaks)? So theoretically, it would make sense for the effect to phase out at 1000nits TV?
for content mastered at 4000nits, the final content after processing could be > 3000nits for peaks. it would make sense it has stronger effect on 1000nits TV.

[chros]

I have added DoVi section to all the available settings docs.
VSVDB is the EDID value.

Were those values retrieved using bscpylgtv command or by extracting the default DV config files from the C2 TV firmware?
As discussed prior, I think @quietvoid commented that the EDID Tmax values transmitted to an hdmi external device are used for “detection/player led” and TV led uses those internal config values.

The C2 default config file entry is same to what you’ve captured in the docs. It may not or is not the same as the EDID VSVDB value transmitted over the wire. Here’s my findings for my older E7, where the EDID VSVDB Dolby Tmax is way lower (350) than my TV’s internal DV Tmax (~750). I don’t have any Vertex to confirm this, I used an rpi5 connected to the TV & a command to get the EDID.

Those values come from the extracted firmware.
quietvoid is right, vsvdb values are used by lldv external devices.
And internal and vsvdb values can be different, eg with C8 (560 in Cinema vs 700 vsvdb).

Maybe I will add more models later as a sub section (Bx, Ax, and diferent sizes with newer models).

I added lot of other models to available settings docs.

[aboulfad]

I added lot of other models to available settings docs.

cool! Too bad I can’t find my 2017 E7 config, I’ve searched hi & Lo in the FW as well on my TV (lg dev mode not rooted) but can’t find it.I found some but Tmax was too low for E7.

[chros]

I added lot of other models to available settings docs.

cool! Too bad I can’t find my 2017 E7 config, I’ve searched hi & Lo in the FW as well on my TV (lg dev mode not rooted) but can’t find it.I found some but Tmax was too low for E7.

Look in "tvservice-dvb.pak.unsquashfs/mnt/lg/tvservice/pqldb/dolby" (not in rootfs) in the extracted firmware, that's where 2018/2019 models have it.

[aboulfad]

Look in "tvservice-dvb.pak.unsquashfs/mnt/lg/tvservice/pqldb/dolby" (not in rootfs) in the extracted firmware, that's where 2018/2019 models have it.

Thanks, per prior search in a different path for 2017 E7 the highest Tmax I found was 430nits. If indeed E7 or other newer series are using default DV config files shipped with firmware for TV-Led, that would imply for older gen a much lower Tmax is used by default for TV-led. 2017 E7 as per rtings & few publicly shared DV calibration configs is around 700-760nits.

The retrieved (from EDID) VSVDB(Dolby) Tmax is 350 nits which is oddly also a very low value for player-led. I realize my TV is old but just curious what's up !

PS: path for E7 DV OLED firmware file

Code: Select all

06.10.30.01-HE_DTV_W17H_AFADATAA/tvservice-atsc.pak.unsquashfs/mnt/lg/tvservice/pqldb/dolby/OLED_All.txt

[chros]

Look in "tvservice-dvb.pak.unsquashfs/mnt/lg/tvservice/pqldb/dolby" (not in rootfs) in the extracted firmware, that's where 2018/2019 models have it.

The retrieved (from EDID) VSVDB(Dolby) Tmax is 350 nits which is oddly also a very low value for player-led. I realize my TV is old but just curious what's up !

PS: path for E7 DV OLED firmware file

Code: Select all

06.10.30.01-HE_DTV_W17H_AFADATAA/tvservice-atsc.pak.unsquashfs/mnt/lg/tvservice/pqldb/dolby/OLED_All.txt

Just checked it in "mnt/lg/tvservice/pqldb/dolby/C1_OLED.txt", Tmax = 374 in PictureMode=2 (DoVi Cinema) and only PictureMode=12 has Tmax = 350 entry (not sure which preset/vsvdb this is).

Note that these default Tmax values not necessarily mean the peak or 10% patch window peak values, they are set according to the underlining factory 1D LUT in DoVi presets. E.g. on the 55"-77" G2 the gamma 2.2 factory 1D LUT is the same across all SDR and HDR10 presets and they use 990 value to compensate it in HDR10 (and DoVi as well), while you could only measure 920 nits on better days with 10% patch window and only 870 after 2000 hours later.

[aboulfad]

… Note that these default Tmax values not necessarily mean the peak or 10% patch window peak values, they are set according to the underlining factory 1D LUT in DoVi presets. E.g. on the 55"-77" G2 the gamma 2.2 factory 1D LUT is the same across all SDR and HDR10 presets and they use 990 value to compensate it in HDR10 (and DoVi as well), …

The newer TVs & their associated DV config files do have more details. Thanks for the explanation! There must be somewhere for the E7 where this higher Tmax “compensated” for HDR (HDR10/DV) resides. It’s possible it is baked in the firmware libs and not explicitly specified in config files as in later TVs.