#FREE42 FORUM HOW TO#
#FREE42 FORUM SOFTWARE#
#FREE42 FORUM TV#
#FREE42 FORUM FREE#

#FREE42 FORUM HOW TO#

Dolby isn't going about figuring out how to control the LG OLED backplane, and how to translate their metadata into the voltage across the various diodes. Of course, this is all the more argument that how the net result of DV's tone-mapping is 'rendered' to the panel must by controlled more by the set than DV's 'processing'. So what exactly, on an OLED set, is DV 'taking control of.' An OLED is an emissive display, every single red, green and blue (and white for LG) diode is its own little 'backlight'. There are no backlight zones on an OLED there is no backlight. If you were watching on an OLED set, I'm curious what backlight zones you're talking about.Ĭlick to expand.I don't know what you're getting at. Not sure why you left out the rest of the paragraph from Matt. I think the real reason that Samsung and Sony didn't adopt DV from the beginning is that they simply didn't want to cut into their profits, which makes sense from a business point of view, but the ultimate reason their profits are going to be cut into is the simple fact that other manufacturers are making displays that are better and cost less. Vizio has put out(3 years of working with Dolby and untold amounts of money in R&D) and they are getting out amazing UHD picture quality from a relatively affordable display(compared to Samsung and Sony). What it sounds like is what it always has been, 'You get out what you put in'.

#FREE42 FORUM FREE#

None of this screams free R&D from Dolby to me. He also says at the end of the paragraph that they re-designed their own SoC to offload the DV real-time metadata. Sounds to me like Vizio spent quite a bit of money on R&D to make sure their display's could be used to display what the DV content created wanted. however there are usually hardware dependencies because the level of processing is absolutely massive (so we designed a special block in our SoC to offload this).

#FREE42 FORUM TV#

a lot of the TV system had to be redefined or reinvented by VIZIO to achieve what the format was capable of. We worked with Dolby for nearly 3 years on doing it right. It was up to VIZIO to build a system to handle the processing requirements (and the backlight, color filters etc to create a display that could achieve the quality possible by DV). DolbyVision is a format + processing/mapping SW.

#FREE42 FORUM SOFTWARE#

So, how well it is done will still be dictated by the set's manufacturer.Įdit: even if DV wrote software to assist their clients, I doubt they would force it upon them.Ĭlick to expand.Not sure why you left out the rest of the paragraph from Matt.

I highly doubt DV is going to write software to implement this algorithm generically for every possible backlight solution.

However, I'd guess the set, who knows how many actual zones it has, be it a few on edge-lit or more on FALD, would still have to contain an algorithm to translate these hints into the voltage supplied by each backlight controller. He says, 'Consider you could use dynamic metadata to change one of 16,000 backlight zones on a Dolby Pulsar to slam from 1000 nits to 4,000 nits on a scene change.' What consumer set has 16k zones? So, even if it 'takes over' the backlight, it only does so by giving hints. If I'm reading him right, there may be metadata data to hint at the brightness of various parts of the screen (the 'backlight'). Click to expand.If you were watching on an OLED set, I'm curious what backlight zones you're talking about.Īlso, Tom, above, mentioned something interesting about the dynamic metadata and backlight zone 'control'.

Free42 forum