As most of you probably know, AMD Ryzen CPU owners in particular will benefit from Windows 11 24H2. Great performance improvements that 24H2 has miraculously unlocked. Over the last few weeks, I’ve had various software problems that have forced me to perform a completely new Windows installation. My old image with Windows 23H2 just wouldn’t work with Calman – Calman would start, but after a few seconds the app just crashed. Why? I have no idea!
So I used a different SSD, which now only has my test software installed for the monitor tests. Of course, I installed a Windows 11 24H2 version right away. I was also able to successfully test the MSI MPG321URX until 13.11.2024 (article coming soon). When I started testing the ASUS ROG Swift PG27AQDP (1440p with 480 Hz) last weekend, I was in for a nasty surprise. This must have been caused by the Windows 11 24H2 update KB5048162 or some other update.
As you know, I test all monitors in the default settings. On the one hand, you can see the performance of the monitor – as probably 90 percent of all users will use it – and on the other hand, the monitors usually run in the extended color space by default. In other words, the maximum that the monitor can do. This is also how the ASUS PG27AQDP was set. But take a look at what Calman reported back to me as color space coverage:
ASUS PG27AQDP Color Space
That’s pretty low for an OLED display! So I was really confused. Let’s see what happens if I restrict the color space to sRGB using OSD?
Now I was sure it must be the monitor. ASUS has once again sent me a defective device. Firmware bug was my first thought. So I immediately called ASUS Germany. The details of this phone call don’t matter here, because in the end I was so wrong!
I immediately grabbed the next monitor, the Corsair Xeneon 34WQHD240-C. Same test site and same error. The QD-OLED panel only manages sRGB color space coverage? It’s impossible that two such different monitors have the same problem. So I measure my Samsung OLED G8 too, just to be on the safe side. My Samsung can also only cover the sRGB color space. I’m sure you can imagine how stupid I looked!
What else could it be? Graphics card, right – NVIDIA or AMD is to blame. Tested both, but always the same problem. In the meantime, I have communicated my problem to Tim (Hardware Unboxed) and Simon (TFTCentral). I also called ASUS again, as I was obviously wrong with my firmware bug diagnosis. The big guessing game with Rosenthal began. In the end, I found a completely new function in Windows that caused all the chaos.
Previously, you could change the color profile here via dropdown. If you now click on Color profiles, this window opens, which did not exist before. Have a look:
This slider was set to “on” for me. What Microsoft is describing here is a color space limitation to sRGB. Windows presumably retrieves the panel information provided by the scaler from the LUT (Look up Table). Windows then simply bills the sRGB limits and all wide-gamut enthusiasts look into the sRGB tube. The only problem is that Windows applies this factor to everything. If you limit the color space in the OSD (emulated) to sRGB, then this Windows factor is added on top. This results in the color space being limited even further – completely unnecessary! (see picture PG27AQDP – sRGB Cal. Mode)
Conclusion
It seems that Microsoft has set this feature to “on” by default. Microsoft should definitely change this again, because not everyone wants sRGB exclusively. This feature is a nice thing if your own monitor does not have an sRGB profile and the sRGB color space is clearly exceeded. Then it is a “nice to have” function. Anyone who wants to edit their videos in P3 or their images in Adobe RGB will probably only notice this when the child has already fallen into the well. Under certain circumstances, this can not only cost a lot of time – but also a lot of money. Will Microsoft pay for any damages? I suspect not – hence my urgent appeal to Microsoft: Please change this immediately!
If in doubt, all monitor owners should deactivate this function on the part of Windows – especially if you prefer to use Adobe RGB, DCI-P3 or even Rec. 2020. At this point, I would also like to say a big thank you to ASUS Germany – sorry for all the confusion and the false alarm. For your information: My colleague Tim knew that this feature was coming from Windows, but he was also surprised that it was automatically set to “on”. I have not yet been able to speak to Simon.
With Windows sRGB mode deactivated, I can now continue testing as usual. The Corsair 34WQHD240-C sends its regards with 85 percent Rec. 2020.
73 Antworten
Kommentar
Lade neue Kommentare
Veteran
Urgestein
Urgestein
Urgestein
Veteran
Veteran
Moderator
Urgestein
Moderator
Urgestein
Veteran
Moderator
Urgestein
Urgestein
Veteran
Urgestein
Moderator
Urgestein
Mitglied
Alle Kommentare lesen unter igor´sLAB Community →