HDR performance
One important piece of information first: it makes no difference whether you have an NVIDIA or AMD GPU, and that’s already something positive. I looked at all the common HDR presets and of course measured them. Before I say anything, you should take a look at the measurement results.
HDR True Black 400
True Black 400 NVIDIA
HDR Peak 1000
HDR Peak 1000 NVIDIA
Before you look at the data on Dolby Vision, it might be useful to understand the basics: How Dolby Vision currently works in conjunction with Windows. You can find more information here: ASUS PG32UCDM Firmware MCM105 Click here!
Dolby Vision Dark
Dolby Vision Bright
Dolby Vision Bright
Interim Conclusion HDR
On the subject of HDR10, I can say that the performance is still ok. The fact is that the AW2725DF performed slightly better here. Here again for comparison the Peak 1000 of the AW2725DF:
HDR Peak 1000 NVIDIA
Nevertheless, anyone who gambles in HDR10 will certainly not be completely disappointed here. Dell should take another look at the EOTF tracking and improve it with a firmware update. Or, in the end, it’s simply because this sample is not one for the press. Because my colleague Tim has given the AW3225QF a much better report card – both in terms of SDR color accuracy and HDR. This is also not the first time that I have come up with different results (despite using the same measurement technology and the same software). In other words, I am officially questioning the individual calibration of monitors. And that applies to all manufacturers!
Now I need to give you some background information on the subject of Dolby Vision. The bottom line is that Dolby Vision Dark Mode is nothing more than HDR10 True Black 400 mode. It stops at 450 nits, but gives you the best possible color fidelity. At least that’s what my measurements show. The only question that remains is whether I really sent a Dolby Vision signal to the monitor via a test pattern?
The current status is that I am only sending HDR10 patterns and no Dolby Vision patterns to the monitor via Calman. This makes the picture much too bright, especially with small APLs. However, this can certainly offer an advantage if you force HDR10 content into Dolby Vision. The brightness is too much at the bottom, but the roll-off is not too hasty. This is particularly noticeable when you have bright HDR scenes over a large area. Here’s a comparison:
The topic of Dolby Vision is unfortunately still in its infancy, so it’s not just down to my non-existent test patterns. Windows can only rarely distinguish between Dolby Vision and HDR10 and automatically switch the monitor to the correct mode. In most cases, Windows sends HDR10 to the monitor as Dolby Vision. This is also the reason why there is a manual selection between HDR10 and Dolby Vision in the OSD. The customer should set the monitor to the correct mode because Windows cannot do this in case of doubt. With my LG OLED TV, this is always done automatically, as the signal is recognized by the scaler and the TV is set to the correct HDR mode. There is no Windoof uh Windows device connected to it.
But it gets worse, because even if you have a Dolby Vision pattern generator, you can’t measure Dolby Vision. I was initially talking to Tim from Monitors Unboxed about this. Quote: (DV = Dolby Vision)
“It has something to do with the monitors not supporting a DV feature necessary for pattern insertion. You’ll have to talk with TFT Central to get all the details, he’s the one that figured it out”
I also contacted my colleague Simon Baker (TFTCentral) and here is the gist: Quote:
“I have a DV pattern generator, but annoyingly none of the DV capable monitors I’ve seen so far actually support the HDMI tunnelling necessary to use it! I approached some very knowledgeable people in the industry who confirmed this was a limitation at the moment. So right now there’s actually no way to input a DV test pattern to allow you to properly measure EOTF tracking of DV content on these monitors.”
So there is currently no way to measure Dolby Vision, even if you have the right hardware. Only the maximum peak brightness can be derived here. This means that all measurements (including those from the ASUS PG32UCDM) should only be considered in terms of brightness and not in terms of accuracy. If you want some more information about HDR10 in Dolby Vision, you should read the article by Simon Baker. Click here!
Ok, that’s it for today. Last page… If you still have time, here’s Tim’s review:
- 1 - Introduction, Features and Specs
- 2 - Workmanship and Details
- 3 - How we measure: Equipment and Methods
- 4 - Pixel Response Times
- 5 - Display Latencies
- 6 - Color-Performance @ Default Settings
- 7 - Direct Comparison and Power Consumption
- 8 - Color-Performance calibrated
- 9 - HDR-Performance
- 10 - Summary and Conclusion
20 Antworten
Kommentar
Lade neue Kommentare
Veteran
Veteran
Moderator
Moderator
Veteran
Veteran
Veteran
Veteran
Moderator
Urgestein
Mitglied
Urgestein
Veteran
Moderator
Veteran
Urgestein
Veteran
Urgestein
Urgestein
Alle Kommentare lesen unter igor´sLAB Community →