Dolby Vision now possible through MP4 Mux.

[susanstone2022]

yes. i know it can do stuff other than diming pictures. my question is why a 1000nits tv need to use trim that target to 100nits display? the trim is created by referencing 100nits target. it does not make sense to use it on a 1000nits tv.

I hate to do this, but please see Interpolation. This is literally built into the spec and Dolby's conception of how their technology works. As explained before, the 100-nit SDR trim is already used for interpolation to generate higher-nit trim level data, automatically, by default. It does not mean it's linear and likely Dolby extensively tested this internally over the years to ensure it does "make sense" when TVs or devices tonemap accordingly -- this is important, as not all devices and situations seem to follow the spec and bugs do exist in different versions of the Dolby Vision engine/SDK in devices like the Shield Pro 2019 etc. It is important to separate these two distinct topics: 1) how Dolby Vision (metadata, RPU, engine, spec, algorithms, tools) is designed and works in line with Dolby's suggested best practices and 2) how displays and devices process, pass, and receive Dolby Vision data that is generated by studios/colourists/software.

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. If it didn't do this, it would be hard to sell everyone on Dolby Vision as future-proof, given the huge difference in nits-output between an HDR DV capable consumer display in 2016-2018 and 2023-2025, or even mastering and colourist habits and mistakes (e.g. some UHD BDs had ridiculously strange and seemingly invalid DV metadata even as late as 2019). Case and point, some HDR colourists are putting an SDR grade inside an HDR container, which literally means that Dolby Vision would have to interpolate up from an SDR grade and any 100-nit SDR trims, there's nothing else there! Hopefully that clears things up a little, I'm off for the weekend. I strongly recommend reading and testing more on the side to see things for yourself.

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

[RESET_9999]

do you know the lift is targeted 100nits TV or 1000nits TV? I bet it is the former.

just find out by playing these:
https://drive.google.com/file/d/1NM2Vjz ... sp=sharing
https://drive.google.com/file/d/1Qfa2zo ... sp=sharing
https://drive.google.com/file/d/1TBXGnp ... sp=sharing
https://drive.google.com/file/d/1oN1uV8 ... sp=sharing

As i said earlier the L8 100nits trim is a noticeable positive on my 810nits C2 which matches the positive lift of CMV2.9 (600+1000).
I also tested L2 with a 100nits trim and it also raised brightness but not as much as 600+1000nits.

Same story on my PC monitor(samsung 400nits) with the Energy player.

[skull88]

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

Obviously that's always been the baseline marketing, the "dynamic" part of it. However, that's been there since the initial release and HDR10+ also has this, so what has changed, especially in cmv4.0 is the added creative controls and automatic (now tunable) analysis and generation of trims! If you play around with cm_analyze for example, you'll note that it generates the 3-levels of L2 trims by default for backwards compatibility. Why would this be the case, if L1 was enough? The default is not to have ONLY L1+L3, right? This is precisely because it allows a colourist to run the automatic algo and then only make adjustments to the shots or trims that they actually feel need them. To me, that's precisely why Dolby Vision is the metadata Apple and Netflix chose for their platforms, and not HDR10+, aside from business reasons, it gives a wild amount of control (especially in cmv4.0), but also works quite well if you just let it do its thing automatically, despite bugs and issues with devices/partner implementation. Oh, and forgot to add that you actually don't even need a paid license to generate L1, but you do for adjusting any L2/L8 trims, that tells the whole story in my view. In any case, back to actual work lol. Cheers!

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