This is only about “fake” a EDID that Windows see the Monitor as DV Monitor so DV can be used at all.
1 Like
You’re an expert in this and I fully trust what you say, thanks for chiming in, seems it’s all smoke then
Looks like a alternative/update to my old LLDV post on windows:
In the org. version the player directly “hacks” the LLDV extension, to get it working on windows, this update seems to circumvent the check by EDID manipulation, so can potentially work with more players
Its normal LLDV on windows, yet there are some metadata issues.
Check the windows section in this guide.
1 Like
No its not, its working LLDV on windows, which has been working for a while now, yet is still super niche and hackish.
The main issue is that DOLBY locked the LLDV extension to specific licensed monitor/devices, which made it not work on any normal “unlicensed” HDR TV/Monitor.
So my old reddit post and this new EDID post, just circumvent this lockout. After that its just normal LLDV and the extension is official and directly from DOLBY. As noted the main issues is the lockout + you need a UWP app player and than also a specific setup/support for this extension and playback-path. The best option is the “Energy Media Player” as its the only player that actually tried to get this working in the first place.
Most users that try this solution are also confused why they don’t see an “DV” logo on there TV, which is normal in this case for LLDV, which is just preprocessed DV and output as HDR10. Yet that’s ofc hard to explain to a normal user…
PS: There is also the very nice MPC video renderer, which keeps adding DV stuff. Yet i think still lacks DV 8.1 support or cant process DV dynamic metadata? Have not tested in a while.
1 Like
okay this is cool (also love the spreedsheet, shared it here
https://forum.kodi.tv/showthread.php?tid=376035&pid=3234384#pid3234384)
So DV might actually be mature in 2 years on windows? not really surprising since DV is becoming more and more popular
thanks for sharing and looking forward to what’s coming
Not sure about this, its still unclear why DOLBY hides/locks this extension in the first place, as it could have allowed any player (UWP) to play DV on windows for years, the extension was released in 2019…
So clearly DOLBY has no real interest in bringing DV to windows/PC. We also kinda had DV on windows on Xbox for games, where it works fine. Yet again not on PC.
My guess is DOLBY does not want a “free” accessible DV solution on windows and rather directly license it to APP’s like Netflix… So those could potentially work in the future on PC, yet again most of those big streaming services are also not focused on PC…
So my bet is we will keep relying on “hacks” or reverse engineered stuff, which is what MPC renderer and the MPV-Player are doing.
1 Like
So Windows is only cheated to have a DV TV and send out LLDV by 422, 12bit.
So yes, it is only static HDR10.
What is better now? Use the ready to use HDR10 metadata or cheat the system to have fake static HDR10 data?
It much easier by using a Vertex2. Just use the EDID of a DV TV and use LLDV. Same result.
1 Like
Or Ezcco splitter with CFW (35$) 
1 Like
Its not the same, the DV extension does the color-conversion if the source has no HDR10 fallback. Than the extension also applies all dynamic DV metadata as any LLDV solution does. The main difference is that the TV will not detect it as “proper” LLDV, so no DV logo.
Technically its similar to “normal” LLDV, mainly just where in the chain the color-conversion and dynamic-metadata is applied. Ofc this excludes FEL atm and there are issues that some metadata is not correctly processed, as the chain is more complex/untested compared to a normal DV or LLDV to a DV capable TV.
Yet as you can see in the table the hacked windows solution is more accurate in some tests than a lot of the licensed DV players in LLDV mode, check the “RPU LLDV RESPONSE” table in the doc.
One of the main reason’s i never really used this windows LLDV is the dreaded “red-push” bug, which is the same as nvidia Shield (does not effect all DV profiles).
2 Likes
Potentially, yet it also cost 400€, while the other just a few $ for the HEVC extension/player. So quite expansive just to get LLDV working on windows. Ofc Vertex will “work” with any player and also “should” have no LLDV anomalies.
1 Like
Any cent would be too much to get LLDV with HDR10 only…
I use the Vertex2 with LLDV on a 10 years old 24" TV…
But for sure only for testing.
I noticed recently that only Windows 10 has the red push: Windows 11 does not.
Also, the latest Windows update now allows TV-LED (TV now triggers DV)
Ah cool, btw does this mean you can pass-through native DV now in TV-Led mode, do we still need the DOLBY extension + UWP player?
Not up-to date with Dev/Beta Windows 11 versions atm.
I don’t really get what that means? As noted the end-result (if all works correctly) would be the same as doing normal Player-Led LLDV. The final output should roughly match.
Does the player have Dolby Vision licence?
When not it’s HDR10 only, also when the TV is in DV mode. It’s a different static meta data.
DV meta data is proprietary.
I found this
Microsoft is also updating Windows 11’s HDR support to allow you to independently toggle Dolby Vision support in content or throughout Windows. Dolby Vision used to be forced on inside Windows if you enabled it on your monitor, so it’s nice to have the option to be able to toggle it on or off.
Windows 11 gets some much-needed HDR improvements - BusinessGhana.
this is going to be baked into windows? so you won’ need an extension?
allot of people complained that it was forced on them but now it seems it’s an easy toggle to turn it off
I dont know but I do have the Dolby extension and using the Energy Player, it passthrough the dynamic metadata to the TV.
Ah cool, btw does this mean you can pass-through native DV now in TV-Led mode, do we still need the DOLBY extension + UWP player?
How do you confirm it’s DV meta data and not HDR10?
The DV logo on TV does not say it’s real DV meta data. It only shows the received vsif DV 0x81 package. This two items are independent from each other.
I only know a test video for HDR10+ with changing the meta data every 10 seconds. So only real HDR10+ TV and meta data do show the response.
1 Like
Easy… My TV has an issue with the Chroma Weight Metadata which doesn’t work in TV-LED on any device. If this was just player-led DV, that metadata would work. All the other levels and trim controls work.
1 Like
Ok, by the extension by Dolby Laboratories itself it makes sense:
This would be also the aproach by @doppingkoala to inject the DV meta data data.
1 Like