|
|
![]() |
||||||||||||||||||||
|
Best 4K Blu-ray Deals
|
Best Blu-ray Movie Deals, See All the Deals » |
Top deals |
New deals
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
![]() $82.99 5 hrs ago
| ![]() $74.99 | ![]() $124.99 1 day ago
| ![]() $99.99 | ![]() $39.02 4 hrs ago
| ![]() $29.95 | ![]() $24.96 | ![]() $70.00 | ![]() $35.99 | ![]() $23.79 16 hrs ago
| ![]() $33.49 | ![]() $33.49 |
![]() |
#7081 |
Retired Hollywood Insider
Apr 2007
|
![]()
https://forum.blu-ray.com/showthread...n#post15508703
since then ^ , 3 weekly updates -> https://www.rtings.com/tv/learn/real...d-burn-in-test with an op-ed by Display Daily - https://www.displaydaily.com/article...urn-in-problem |
![]() |
#7082 |
Retired Hollywood Insider
Apr 2007
|
![]()
https://forum.blu-ray.com/showthread...s#post15513258
^ On a pro level, and for JVC aficionados, affordable ![]() |
![]() |
#7084 |
Retired Hollywood Insider
Apr 2007
|
![]()
Still nobody yet know/recognize Maverick’s patch as seen in the ABC National News broadcast from last week - https://forum.blu-ray.com/showthread...h#post15620014 ?
o.k. then, here’s a hint on the locale, from conversation back in the day about an altogether different actor and movie - https://forum.blu-ray.com/showthread...st#post5039056 P.S. Don’t assume that all filming locations for Top Gun: Maverick have been restricted to Coronado and NAS Lemoore. |
![]() |
#7086 |
Senior Member
Sep 2010
|
![]()
"Announced in September, Microsoft has now publicly released the update that adds Dolby Vision support for streaming apps on Xbox One. However, at this time, Dolby Vision is only supported for Netflix.
It should be stressed that this new "low latency profile" is not compatible with all Dolby Vision TVs. LG’s 2016 TVs as well as Vizio TVs are notably missing from the list of supported devices. Microsoft claims that Dolby is getting ”working with TV OEMs to update TVs currently in market”." https://www.flatpanelshd.com/news.ph...&id=1539730922 I can’t find a Dolby document mentioning this low latency profile. Without the information on the low latency profile, it is my understanding that there are two main versions of Dolby Vision: . Dolby Vision before the introduction of the MEL (Minimal Enhancement Layer) . Dolby Vision with MEL ![]() Goal of MEL: "The MEL can be used to minimize the processing requirements for the enhancement layer and thus ensure broader use among UltraHD (Blu-ray) SoCs." https://www.dolby.com/us/en/technolo...les-levels.pdf A double layer Dolby Vision video stream is composed of a base layer video stream and an enhancement layer video stream. The full enhancement layer (FEL) is a HEVC video stream with embedded Dolby Vision metadata: it requires a SoC to be capable of simultaneously decoding two video streams (base layer video stream and FEL video stream). The minimal enhancement layer MEL, a constrained FEL, only consists of metadata: it requires a SoC to be capable of only decoding one single base layer video stream. ![]() https://www.dolby.com/us/en/technolo...les-levels.pdf Possible cases with new Dolby Vision certified video files & devices compliant with the latest Dolby Vision version: (decoding in a streaming device is more explicit than in a TV) "A profile 4 bitstream with a MEL is a constrained version of the original profile 4 bitstream. It produces a high dynamic range Dolby Vision video signal on both older and new Dolby Vision certified devices." [Dolby] Dolby Vision profile 4 with MEL video file stored on a streaming server >> Internet >> streaming device > 10-bit Dolby Vision with MEL video signal >> HDMI >> Dolby Vision with FEL-compliant TV "A new Dolby Vision certified device is able to decode a profile 4 MEL bitstream without instantiating a secondary HEVC decoder for the enhancement layer." [Dolby] (it can do more, i.e. double decoding; it can do less, i.e. single decoding) Dolby Vision profile 4 with MEL video file stored on a streaming server >> Internet >> streaming device > 10-bit Dolby Vision with MEL video signal >> HDMI >> Dolby Vision with MEL-compliant TV Possible cases with original video files / original Dolby Vision-compliant TV: original Dolby Vision profile 4 video file stored on a (Netflix) streaming server >> Internet >> original streaming device > original 12-bit Dolby Vision video signal >> HDMI >> original Dolby Vision-compliant TV "If a Dolby Vision playback device supports Dolby Vision profile 4 and chooses not to instantiate a second HEVC decoder, then it must check for these values in the reference processing unit of a Dolby Vision bitstream. If the values are not exactly as shown for all three channels, the device must flag the bitstream as a Dolby Vision original profile 4 bitstream; otherwise, flag the bitstream as profile 4 minimum enhancement layer." [Dolby] original Dolby Vision profile 4 video file stored on a streaming server >> Internet >> streaming device able to convert original FEL to MEL > 10-bit Dolby Vision with MEL video signal >> HDMI >> Dolby Vision with MEL-compliant TV "An original profile 4 bitstream with a full enhancement layer distributed after December 31, 2017, may not produce the high dynamic range Dolby Vision video signal on all Dolby Vision devices." [Dolby] "A new Dolby Vision device that chooses not to instantiate a second HEVC decoder and supports profile 4 must distinguish the original profile 4 bitstream from the profile 4 MEL bitstream. When receiving an original profile 4 bitstream, such a device: • Exits the Dolby Vision video pipeline • Uses its normal video pipeline for video processing, and displays a standard dynamic range video signal only • Does not display the Dolby Vision logo." [Dolby] original Dolby Vision profile 4 video file stored on a streaming server >> Internet >> original streaming device > original 12-bit Dolby Vision video signal >> HDMI >> interoperability issue >> Dolby Vision with MEL-compliant TV original Dolby Vision profile 4 video file stored on a streaming server >> Internet >> streaming device able to convert original FEL to MEL > 10-bit Dolby Vision with MEL video signal >> HDMI >> interoperability issue >> original Dolby Vision-compliant TV Dolby Vision profile 4 with MEL video file stored on a streaming server >> Internet >> streaming device > 10-bit Dolby Vision with MEL video signal >> HDMI >> interoperability issue >> original Dolby Vision-compliant TV Original Dolby Vision-compliant TV: 2016 LG OLED TV, Vizio TV, ... (for the time being not yet updated) (New certified) Dolby Vision with FEL-compliant TV: 2017/2018 LG OLED TV, ... (New certified) Dolby Vision with MEL-compliant TV: Sony TV https://www.dolby.com/us/en/categori...compatible.pdf Original Dolby Vision-compliant TVs are capable of simultaneously decoding two video streams like the Dolby Vision with FEL-compliant TVs. They can be more or less easy to be updated to be compliant with the latest Dolby Vision version: they can do more, i.e. double decoding; they can also do less, i.e. single decoding. https://twitter.com/xQuatroK/status/1051972830651445254 https://twitter.com/VIZIO/status/1051962330475634690 |
Thanks given by: | Robert Zohn (10-19-2018) |
![]() |
#7091 |
Blu-ray Emperor
|
![]()
The player can do both profiles, but not all TVs can. The DV Sonys can't do the full-fat version, LG's 2016 sets can't do the low-latency profile. Doesn't matter when you've got a player that can do both...but the Xbox can't do both, which is the point.
|
![]() |
#7092 |
Power Member
Nov 2013
|
![]()
It's similar to the Sony profile in that they're both low latency, but Microsoft stated that this is a profile that they specifically created with Dolby. As far as I know, Microsoft had no involvement with the Sony profile that was initially deployed to Sony TVs.
|
![]() |
#7093 |
Power Member
Nov 2013
|
![]() |
![]() |
#7095 |
Retired Hollywood Insider
Apr 2007
|
![]() ![]() Not sure what’s in here - https://www.kodak.com/corp/podcast/p...tid=4295010656 with regards to - https://www.imdb.com/title/tt6628394...ef_=tt_dt_spec but may be an interesting listen for those stuck in traffic on the way to wherever or waiting at your local DMV to renew your driver’s license and ultimately then sit in said traffic. Bike. |
![]() |
#7096 | |
Retired Hollywood Insider
Apr 2007
|
![]() Quote:
the patch would provide a little history as to where Maverick’s been since Miramar, and it hasn’t been doing this out of the Far East – https://vimeo.com/64333578 P.S. I realize that with all this Top Gun: Maverick conversation we’re a couple years ahead of social media and websites, be they movie or technically related, but that’s not that uncommon for the HDR Discussion Thread as we have a history of leading far ahead of the pack with lots of things, including HDR geeky, to list only a few, for there are many more ![]() https://forum.blu-ray.com/showthread...r#post13324408 https://forum.blu-ray.com/showthread...ar#post9754213 Stay tuned. |
|
![]() |
#7097 | ||
Retired Hollywood Insider
Apr 2007
|
![]() Quote:
I’ll leave that sort of tinkering up to guys like LordoftheRings and JohnAV. |
||
![]() |
#7098 |
Retired Hollywood Insider
Apr 2007
|
![]()
because unlike others, we have proven past history of unfettered access to the most cutting edge proposals and decisions from the ITU, e.g. – https://forum.blu-ray.com/showthread...ry#post7361160
as well as from SMPTE study groups, for example - https://forum.blu-ray.com/showthread...g#post14203568 and have shared with our readers various tidbits of HDR/WCG developments from along the way (before publication) and will continue to do so when at liberty, without revealing too much – ![]() These things ^ form the basis or DNA of consumers’ devices and the importance of the work in these various groups can not be overstated, thusly they are presented here for insight. |
Thanks given by: | mrtickleuk (10-20-2018), Staying Salty (10-19-2018) |
![]() |
#7099 |
Retired Hollywood Insider
Apr 2007
|
![]() ![]() and then back to the airstrip again for yet another take as the sun was setting further down.... Last edited by Penton-Man; 12-16-2019 at 03:47 PM. Reason: poor spelling |
![]() |
#7100 | ||
Special Member
May 2017
Earth v1.1, awaiting v2.0
|
![]() Quote:
Quote:
![]() |
||
|
|
![]() |
![]() |
|
|