Originally Posted by Franin
Ive recently purchased the Vertex 2 and awaiting my NX9 to come back from service. Where can I find JVC LLDV so I can upload and experience DV ?
It's not just JVC LLDV. Any HDR10 display can be fed LLDV - low latency Dolby Vision. The display just needs to be in an HDR picture mode whether selected manually, by having the HDfury device include HDR10 metadata, or by using the HDfury device JVC RS-232 command macros.
The AVS thread is here where you can find instructions on configuring the HDfury device, including downloads of custom LLDV EDIDs:
There is a similar thread on the "European" AV forum.
Some want to call this Dynamic Tone Mapping. It is Dolby Vision and if you want to call DV DTM that is up to you. I prefer to not do so.
LLDV was introduced by Dolby and Sony. Sony TVs cannot process a full Dolby Vision signal. With LLDV it is the player that performs tone mapping using the Dolby Vision content scene by scene metadata layer and not the display. There is also a Dolby Vision data block in the EDID that a display presents to the player that includes whether the display prefers DCI-P3 or BT2020, its RGB X/Y values, its maximum and minimum luminance nit values, and other information regarding the display's capabilities that the player uses to tone map.
LLDV is output from the player as a 4K 4:2:2 12-bit signal that closely follows ST 2084. While we don't know everything about how Sony TVs process this signal, we can apply an HDR curve in our TV or projectors to the input and get good results.
With an HDfury device you can configure it to present an EDID to the player that reports support for LLDV but not full Dolby Vision. This will trigger any player that has support for LLDV to output LLDV when playing a Dolby Vision title.
The newer HDfury devices, Vertex 2, Diva, and Maestro include more LLDV related capabilities than the earlier ones.
- All models include the built-in custom Sony A1 LLDV EDID. You would need either a DCI-P3 color profile applied in the JVC or load a custom color profile that matches the values in the EDID. Dominc Chan created such a custom profile.
- As I mentiond earlier markswift2003 created a custom BT2020 LLDV EDID from the 4K HDR10 full audio EDID in the HDfury device and added an LLDV data block. You can load this EDID to any of the HDfury models.
- The newer models include the ability to configure your own custom DV data block using the browser based web server interface that gives advanced users the ability to fine tune the LLDV related EDID values presented to a player.
- The newer models also have the ability to include custom HDR10 metadata only when the signal is LLDV. With older models custom metadata is either on or off that is sent with all input including SDR and HDR10 that you don't want. Like I mentioned the only reason to send HDR10 metadata is to trigger the display into an HDR picture mode. I don't send any metadata as I use the JVC RS-232 macros for user mode switching based on content type. The newer models have an LLDV macro. The older models do not.
Some players also have the ability to convert SDR and HDR10 content to Dolby Vision that can then be ouput as LLDV. These include the Oppo 203, newer Sony UHD players, and the Apple TV 4K. Players like the UB820/UB9000 can output LLDV for Dolby Vision content but cannot convert SDR and HDR10.
I use MadVR to tone map all of my UHD and HD discs so I do not output LLDV for these. The rest of my UHD viewing is from my Apple TV 4K. With so much DV content available on the ATV4K, it is a good choice for LLDV. I was never satisfied with HDR10 from my ATV4K. The Vincent Teoh video I posted details some of the shortcomings of HDR10 from the ATV4K. With LLDV output instead, the ATV4K is now my go to streaming player.
Should you send LLDV instead of using the JVC Frame Adapt DTM? Probably not in my opinion, but that is your choice to make. Frame Adapt can examine each frame. LLDV is dependent upon the scene by scene DV metadata, but does allow for display device capabilities to be considered in tone mapping.
One final note. I think it was either Kris Deering or Stacy Spears that reported that there are issues with Dolby's LLDV implementation.