HDR performance
When it comes to HDR, I can basically give the all-clear when it comes to NVIDIA vs AMD GPUs. The performance you end up with will “almost always” be the same. Which of the 1000 nits modes you end up using doesn’t really matter. However, I would use the Console HDR mode, which is the most accurate at the end of the day. That’s why you can only see it today. Then it’s back to the usual PDF madness.
NVIDIA HDR True Black 400
AMD HDR True Black 400
HDR True Black 400 AMD
NVIDIA Console HDR (Peak Brightness 1000 Nits)
Console HDR NVIDIA
AMD Console HDR (Peak Brightness 1000 Nits)
Console HDR_AMD
Interim conclusion HDR
The differences between AMD and NVIDIA are marginal and not worth mentioning. What I have noticed, however, is that there can be significant inconsistencies in terms of brightness with an AMD graphics card. If you take a closer look at my measurements, you’ll notice that there are fluctuations, especially in Console HDR mode. Compare Peak vs. Window Sizes with Luminance Stability. You will see that the maximum brightness fluctuates with larger APLs. The 100 percent window in Peak vs. Window Size only reaches 143 nits. After I deactivated VRR and activated it again, I was suddenly back at 250 nits.
The comparison with NVIDIA Peak vs. Windows Sizes is also interesting, because you can also see clear differences here. From an APL of 10 percent, the AMD GPU easily loses 100 nits compared to NVIDIA. My colleague Tim Schiesser was able to measure similar phenomena in real-world HDR applications. He experienced brightness drops of up to 50 percent with an AMD GPU compared to NVIDIA. I agree with Tim that the FreeSync Premium Pro pipeline seems to be the problem here. Because with AMD, the sound mapping is done on the driver side and sent to the monitor. NVIDIA sends the HDR signal to the monitor, which then takes over the sound mapping (simplified explanation). AMD owners may need to redefine the FreeSync Premium Pro pipeline to FreeSync Premium using GRU. You can find help with this in our forum!
Unfortunately, that’s not all there is to report regarding the PG32UCDM and AMD GPUs. I have already told you about the firmware update from ASUS. Unfortunately, this has a negative effect on AMD GPU owners. After installing the update, I was no longer able to select HDR settings, which were suddenly grayed out. By deactivating VRR, I was able to access and adjust the settings again. (e.g. switch from True Black 400 to Console HDR)
Then you have to activate VRR again. If you want to change it again, the OSD setting fun starts all over again. So much for the issue of making things worse with firmware updates. In future, ASUS needs to validate much better before releasing updates to the public. Fortunately, the update had no negative effects on the SDR or HDR performance.
It is also interesting that the monitor with an AMD GPU says that it runs in HDR with FreeSync Premium Pro, but the AMD driver recognizes the monitor as Adaptive Sync. So only ASUS and AMD probably know what is really going on here. Let’s close the article – last page.
- 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
101 Antworten
Kommentar
Lade neue Kommentare
Veteran
Veteran
Veteran
Urgestein
Mitglied
Moderator
Urgestein
Veteran
Moderator
Urgestein
Urgestein
Urgestein
Veteran
Urgestein
Mitglied
Veteran
Urgestein
Urgestein
Urgestein
Alle Kommentare lesen unter igor´sLAB Community →