Summary
The MCM105 firmware update brings Dolby Vision – for those customers who may need it. Whether you want to use Dolby Vision with a maximum peak brightness of only 450 nits at the end is another matter. Was that intentional on ASUS’ part? I’m lacking a lot of imagination in order to chalk that up to an intention. I assume that the validation here was poor. Why ASUS is releasing a half-finished update – for no reason and prematurely – is beyond me. ASUS, what’s going on?
A bug that I found in my sample regarding color space clamping has been fixed. Instead, there is now a bug in relation to the manually set white point, which is interpreted differently for each color space. So if you often use different color spaces, you should be prepared for a lot of fiddling around in the OSD or work with ICC profiles. What I couldn’t understand is the issue of vertical flickering. There do seem to be some buyers with this problem, but it doesn’t seem to be a systematic fault.
Conclusion
Windows and the automatic HDR format detection does not “yet” work, which can lead to incorrect tone mapping. Dolby Vision support for PC games is still in its infancy, but at least the ASUS PG32UCDM and the Dell AW3225QF are now being sold with Dolby Vision support. The main beneficiaries are console gamers and those who connect external devices via HDMI (Apple TV, Fire TV, etc.).
The implementation of Dolby Vision was not entirely successful for ASUS, as a brightness cap was imposed even at 450 nits. When it comes to bug fixes, ASUS needs to work on the software again!
7 Antworten
Kommentar
Lade neue Kommentare
Urgestein
Veteran
Moderator
Veteran
Veteran
Mitglied
Veteran
Alle Kommentare lesen unter igor´sLAB Community →