Dolby Vision now possible through MP4 Mux.

[speeddemon]

So perhaps, Wonka and the ones without 100nits L8 were done in cmv2.9 and upconverted to 4.0 for streaming requirements? or maybe the colorist just was lazy and did not make trims?? idk

Are you seeing a similarity in the studios that are leaving out the 100-nit L8 Trim?

I've been suspecting that it's not an accident that CMv4 produced movies only include an L8 Trim, and that Dolby is telling studios that CMv4 no longer requires separate trims at various luminance levels. I think that some of the "laziness" we're seeing may even be originating from Dolby themselves, or possibly through miscommunications between Dolby and the studios.

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

[valington]

Ok, I think I know what's going on with CMV4.0.

First, Dolby confirmed that L8 is not generated and must fully come from the colorist and only L2 is generated automatically and gets updated through L8 to L2 math. And 600-100nits L8 are not needed/requested most of the time.

Secondly, the 100nits L8 has an effect during DV playback and produce a similar/close effect and image to CMV2.9 with L2 trims. On Windows Energy player or movies and tv app, in HDR10 the active 100nits L8 trim always has an effect but on the C2, the 100nits L8 trim only has an effect if it's alone (without L8 600nits or 1000nits trim). Same behavior in cmv2.9. L2 100nits alone is used but when there are trims, it is not used on the C2.

So in Wonka, there is no active L8 100nit trim and the image is noticeably darker on cmv4.0 device than on 2.9 devices when there is L2 trims.
In Aquaman, there is an active L8 100nit trim and the image looks similar on both 4.0 and 2.9 devices.

So perhaps, Wonka and the ones without 100nits L8 were done in cmv2.9 and upconverted to 4.0 for streaming requirements? or maybe the colorist just was lazy and did not make trims?? idk

I've added the test files in my googledrive: https://drive.google.com/drive/u/1/fold ... fx6vRYDEfs

RESET which player is better for proper dolby vision 7 profile bdmv and mp4 ,SONY X700-X800 OR CLON OPPO ?

[RESET_9999]

Are you seeing a similarity in the studios that are leaving out the 100-nit L8 Trim?

I've seen a couple of CM4.0 without an active L8.
I don't know the % but I'll check my library for sure.

It is strange that it only works when L2 100nits is alone without any other trims on the C2.. It might be different on other TVs because as I mentioned, on windows Energy player, the 100nits trim is always used regardless of the other trims.

[RESET_9999]

RESET which player is better for proper dolby vision 7 profile bdmv and mp4 ,SONY X700-X800 OR CLON OPPO ?

the oppo is more practical because it supports iso and bdmv via the network. In term of quality, there shouldn't be much difference.
x800m2 as fewer bug than the oppo/x700 though.

[kaledi]

I've been using MakeMKV for some time and successfully ripping my 4K BR including those with DV HDR to mkv files and playing these back via a Shield TV pro (2019).
I've just purchased a Fire TV Stick 4K mkv and the same files don't play (via Emby), and I've now discovered the complexity of DV profiles and playback.
There is a lot of info in these forums, but I struggling to find concise and up to date info, so forgive me if this has been answered elsewhere.
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?

[susanstone2022]

It is strange that it only works when L2 100nits is alone without any other trims on the C2.. It might be different on other TVs because as I mentioned, on windows Energy player, the 100nits trim is always used regardless of the other trims.

isn't 100nits trim intended for SDR target display?

[skull88]

Yes, it is primarily intended for that according to Dolby documentation and spec, as colourist should be monitoring on a 100-nit SDR display when making that trim, however, it seems that if it's the only L2 level trim present, it's still used to adjust tonemapping on at least some TV models and playback devices that are not SDR or low-nits. If you think about it, it makes sense, and explains why Dolby says it is mandatory to do the 100-nit trim first, whether any SDR deliverable is going to be exported or not, as 600-nit and 1000-nit level L2 is just interpolated from the 100-nit SDR trim, if no further edits are made. So, if the 600/1000-nit L2 trims are missing/removed, I think the Dolby Vision engine must be doing its own interpretation of the 100-nit trim - we just assumed it was ignored unless screen was 100-nit SDR display, but that doesn't seem to be the case, at least in some situations. I do wonder if EDID plays a role here and/or to what extent? How much of an impact it actually has in real world playback is something RESET_9999 is testing currently, I believe, perhaps he will share findings.

[susanstone2022]

Let's say one makes a content with 1000nits master display and does 100nits trim for SDR. When the content gets playback on a 1000nits display, it will need to use 100nits trim? This does not make sense to me.

[RESET_9999]

trims are not just for diming the picture to the TV target brightness... They can use the trims to lift the brightness and they do that very often. I literally made a bunch of test file with real content that show exactly that.
sorry but It sounds to me that you only read stuff online and you don't actually check out how it behaves on your TV.

[skull88]

Let's say one makes a content with 1000nits master display and does 100nits trim for SDR. When the content gets playback on a 1000nits display, it will need to use 100nits trim? This does not make sense to me.

Re-read my previous post and the following section in Dolby docs. You're focusing too much on the numbers and labels, and not how Dolby designed their pipeline. They interpolate from the 100-nit SDR trim to higher nit targets, and they recommend monitoring the SDR trim preview on the same HDR display or display with similar backlight technology for this reason. Obviously if 100-nit SDR trims were not improving the image (for SDR deliverable or not), they would just be static or removed, but they're almost always present, whether automatically generated or, as is almost always the case, manually adjusted by the colourist, which means Dolby Vision processing does some math and interprets these values for all possible end-user setups. They are also usually required by studios for delivery, although not 100% of time, as Netflix says they are optional for example. There are still questions over implementation, cmv2.9 vs. cmv4.0, but this is a major point of confusion now resolved, at least in my mind. Finally, as RESET_9999 pointed out, you really need to watch his comparison and testing clips, or just test yourself on your setup.

[susanstone2022]

trims are not just for diming the picture to the TV target brightness... They can use the trims to lift the brightness and they do that very often. I literally made a bunch of test file with real content that show exactly that.
sorry but It sounds to me that you only read stuff online and you don't actually check out how it behaves on your TV.

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.

[RESET_9999]

Well if TV-LEd works the same as LLDV for the target brightness, an internal TV config or an edid of 1000+nits with a 1000nits RPU would make the trims to be ignored which makes less sense to me because then the intentional positive lift would be ignored by brighter TV? I know the trims are ignored in LLDV with as shown here but my tv internal config is only 810nits(assuming my calib guy didn't change it) so I don't know if it's the same in TV-LEd (probably)

https://www.youtube.com/watch?v=29ed65Aq5K0

[skull88]

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.

[susanstone2022]

Well if TV-LEd works the same as LLDV for the target brightness, an internal TV config or an edid of 1000+nits with a 1000nits RPU would make the trims to be ignored which makes less sense to me because then the intentional positive lift would be ignored by brighter TV? I know the trims are ignored in LLDV with as shown here but my tv internal config is only 810nits(assuming my calib guy didn't change it) so I don't know if it's the same in TV-LEd (probably)

https://www.youtube.com/watch?v=29ed65Aq5K0

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