Hi.
I recently purchased a PG32UDCP. This is actually the second one, the first one I had to return due to a bad panel. But all the problems described below, I also noticed on the first device. Both were manufactured in July'24 and were approx. 200 units apart according to their serial number.
Also, none of the problems are in any way related to the operation system, nor the device connected to the monitor. Everything described can be seen with Linux (my main OS) and Windows (both via DP) as well as other devices connected through HDMI.
- Gamma kink / Black crush
As reported by various reviewers (see e.g. XDA Developers , TFT Central ), the monitor has a kink in its lower part of the gamma curve which causes some noticeable black crush and banding in the lower gray shades. This is NOT limited to SDR but also very noticeable in HDR which really dampens the experience when consuming HDR content.
This apparently also was an issue with the LG model with the same panel but they have fixed that rather swiftly with a firmware update.
- Lower gray shades with reddish hue
Lower gray shades have a distinct reddish hue to them. If you look at black level test over at lagom.nl, every shade including and below 20 has a noticeable reddish hue. You can also see this clearly at the EIZO monitor test by selecting the gradient test and choosing white with 256 steps. You will notice immediately that the lower left part of the gradient is neither smooth (see gamma kink above), nor pure gray but reddish in its hue.
This is very distracting with many dark mode themes since those are unfortunately mostly used by them.
- Pixel cleaning bugged?
As many before me have reported, the pixel cleaning seems to run quite often, not every 4 hours. Also, I have noticed a few times that the power led (showing stand-by) starts blinking (indicating a refresh cycle) but stops after three or four seconds. Which has me worried, if the pixel cleaning really runs automatically or just starts and stops after a few seconds but still increments the counter. Unfortunately there is no way to confirm either way. And yes, the monitor was in stand-by and not being used, so it wasn't interrupted in any way.
Ony my unit, the OLED Time Track says 72 hrs with 61 Pixel Cleaning Times, resulting in an 2h interval, by the way.
This brings me to my question: Are those problems known and actively being worked own by the firmware engineering team? Is a new firmware going to be released this year/soon or when can we expect fixes for the above problems (if at all)?
Also, more of a feature wish: It would be nice to turn off the power led only for the "power on mode" where it is distracting but keep it for signaling stand-by and refresh cycles. The way it is implemented now, makes it impossible to see if a refresh cycle is running once the power led is permanently turned off.
Otherwise this is a great device and I hope those problems above can and will get fixed.
Thanks,
Matthias
