|
|
![]() |
||||||||||||||||||||
|
Best 4K Blu-ray Deals
|
Best Blu-ray Movie Deals, See All the Deals » |
Top deals |
New deals
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
![]() $82.99 7 hrs ago
| ![]() $74.99 | ![]() $28.10 1 hr ago
| ![]() $23.60 31 min ago
| ![]() $48.44 1 hr ago
| ![]() $33.54 3 hrs ago
| ![]() $124.99 1 day ago
| ![]() $99.99 | ![]() $39.02 5 hrs ago
| ![]() $29.95 | ![]() $24.96 | ![]() $70.00 |
![]() |
#7664 | ||
Special Member
May 2017
Earth v1.1, awaiting v2.0
|
![]() Quote:
Quote:
![]() |
||
![]() |
#7665 |
Retired Hollywood Insider
Apr 2007
|
![]()
Hey, I wish I knew what the hell Geoff D and PeterTHX were talking about above, and gkolb already lost me on the last page with that battle in parts unknown (to me).
Last edited by Penton-Man; 12-18-2018 at 03:38 AM. Reason: typo |
![]() |
#7666 |
Retired Hollywood Insider
Apr 2007
|
![]()
Salty, more my speed - https://forum.blu-ray.com/showthread...w#post15701661
|
Thanks given by: | Staying Salty (12-18-2018) |
![]() |
#7667 |
Retired Hollywood Insider
Apr 2007
|
![]()
speaking of which, with regard to another - http://www.digitalcinemareport.com/a...n#.XBhxH1xKiUk
|
![]() |
#7668 |
Retired Hollywood Insider
Apr 2007
|
![]() |
![]() |
#7669 | |
Retired Hollywood Insider
Apr 2007
|
![]() Quote:
|
|
![]() |
#7670 |
Active Member
|
![]()
I am once again getting confused by how much shadow detail ought to be visible in HDR. Since I started watching UHD Blu-rays 4 months ago I’ve had trouble working out what the right settings should be or what profiles to use.
I initially watched HDR10 titles in default “HDR” mode with standard settings (OLED light 100, Contrast 100, Brightness 50, colour 55, all processing/interpolation off save for “Dynamic contrast” on “low”). This looked fine, however there were many instances in films where shots that were supposed to be black (such as the background of end credit frames or fade outs to black) would be a letterboxed 2.39:1 dark grey. In most films black would actually be black in the background of credits, save for some weird frames which stood out. What’s worse was the banding and artefacting, like dodgy-looking tonemapping in the sanctum scene from Infinity War or the awful banding in the bar entrance scene near the beginning of La La Land which even had flickering grey letterbox bars. Fade-ins from black like the very start of Harry Potter 3 would have a sudden visible jump to grey rather than a smooth transition, and I thought that maybe the level for just above black was too high, so I turned brightness down by 1 to 49 and the grey frames were now properly “black”. The problem is that now dark scenes had slightly more posterised blacks and less visible dark details such as hairs and textures which can be seen when brightness is raised. What I assume should be gradients from dark into shadow, like dark hair, appeared more as solid grey jarring against solid black. After some frustration I decided to try forcing Dolby Vision instead and the initial impressions were better, the beforementioned scenes with banding or flickering looked fine without the black crush from needing to lower the brightness to 49, and “black” frames were the same colour as the letterbox bars. It was a sort of “set and forget” solution, but there was a strange problem where the entire screen’s black wasn’t actually black but was a very dark ‘dirty’ grey gradient, brightest at the bottom of the screen and only really visible when the entirety of the screen was black in a pitch black room, given that one’s eyes had adjusted. The thing is, this was fixed and made “perfect” black by turning the brightness down by 1... to 49... which had the same “black crush” effect that had occurred in HDR10. I’m confused if this is actually how it’s supposed to look, perhaps I’m being over sensitive to how the film is actually supposed to appear and I’m perceiving it as black crush. The thing is, there are clearly details present on the transfer that are imperceptible in blobs of black and it just looks sort of... wrong? Recently I realised another problem with watching in forced Dolby Vision and it’s the botched mapping of highlights, Harry Potter 4 had really weird blown out clipping and a World Cup scene which quite frankly ‘fudged’ certain character’s faces. I decided to go back to HDR for HDR10 and the highlights were handled much better, but I noticed some more banding and flickering in solid grey frames which looked like they should have been black (credits) even at 49. Lowering brightness another step feels like too much and there’s a visible loss of detail even in brighter scenes. I’m kind of stuck. I don’t know if the way it looked in HDR was too dark (with regards to black crush/shadow detail), or if the DV wasn’t dark enough. Any suggestions or ideas? ![]() Are those details like hair or textures on clothes, which are there in the image, actually supposed to be seen? |
![]() |
#7671 |
Senior Member
Sep 2010
|
![]()
HDMI carriage of Dolby Vision / HDR10+ dynamic metadata
As HDMI 2.1 Dynamic HDR is not quite available for the time being, the HDMI carriage of Dolby Vision and HDR10+ dynamic metadata have been implemented in proprietary ways in some HDMI 2.0 products. https://www.soundandvision.com/conte...XxdHlHkewzO.99 HDR10+ dynamic metadata are transmitted from a UHD Blu-ray player / steaming player to a HDR10+ TV using the HDMI Vendor Specific InfoFrames (VSIF). VSIF has been specified since HDMI 1.4. Normally, a HDMI 2.0x receiver ignores VSIF: it won’t transfer VSIF or HDR10+ dynamic metadata to a HDR10+ TV. It should be upgraded to forward VSIF, hence HDR10+ capable receiver. https://hdguru.com/hdr10-looks-for-g...tent-hardware/ Dolby Vision dynamic metadata, transmitted across HDMI (1.4), are embedded into the video signal. Standard HDMI receivers should be upgraded to forward these embedded metadata, hence Dolby Vision capable receiver. https://www.avsforum.com/forum/465-h...l#post54128881 In the near future, the CTA-861-G/HDMI 2.1 HDR Dynamic Metadata Extended InfoFrame is used for delivering Dolby Vision / HDR10+ / Technicolor HDR dynamic metadata to a Dolby Vision / HDR10+ / Technicolor HDR compliant TV. https://glenwing.github.io/docs/CTA-861-G.pdf ![]() Last edited by DanBa; 12-18-2018 at 06:02 PM. |
Thanks given by: |
![]() |
#7672 |
Blu-ray Guru
|
![]()
Seems that China gets the first HDR10+ phone with the Lenovo Z5 Pro GT.
|
![]() |
#7673 | |
Blu-ray Samurai
|
![]() Quote:
|
|
Thanks given by: | DanBa (12-18-2018), Robert Zohn (12-19-2018) |
![]() |
#7674 |
Blu-ray Samurai
|
![]()
Penton, they say a picture is worth a thousand words, so Rebel orange flight suits from the Battle of Hoth-
34A23625-06A1-42FA-846E-F631AC431ABE.jpg |
![]() |
#7675 |
Blu-ray Emperor
|
![]()
Dolby Vision Display Management metadata is stored in the LSB (least significant bit) of the reconstituted 12-bit 4:2:2 output signal and is bit scrambled so as not to impinge on the picture quality. While it's sent on a frame-by-frame basis, the metadata can be shared across multiple frames if no deviation is detected and can end up as a scene-based metadata package. Each packet is sent three times for the sake of redundancy, once the first one is correctly unwrapped and passes the CRC then the others are discarded.
|
Thanks given by: | Robert Zohn (12-19-2018), Staying Salty (12-18-2018) |
![]() |
#7677 | |
Active Member
Nov 2017
|
![]() Quote:
|
|
Thanks given by: | mrtickleuk (12-20-2018) |
![]() |
#7678 | |
Retired Hollywood Insider
Apr 2007
|
![]() Quote:
https://forum.blu-ray.com/showthread...c#post15152714 think dissolves |
|
![]() |
#7679 | |
Retired Hollywood Insider
Apr 2007
|
![]() Quote:
https://forum.blu-ray.com/showthread...p#post15654465 P.S. Even more exclusive, are a batch of Top Gun: Maverick challenge coins that have been made for friends (to the production) and family, which aren’t for sale. |
|
![]() |
#7680 |
Retired Hollywood Insider
Apr 2007
|
![]()
Well, I miss your Youtube contribution posts, so get with it!
Meanwhile, here’s a behind-the-scenes one for the Christmas spirit…. http://www.passion-pictures.com/usa/.../xmas-hold-em/ |
|
|
![]() |
![]() |
|
|