Color performance after a full software calibration
Now let’s take a closer look at the BOE panel when you make improvements with the help of measuring devices. Since not everyone has one at home – I have summarized the different white point settings for the standard mode as well as sRGB and P3 – including the measured values.
OSD Setting D65 @ 200 Nits
These settings apply to the standard mode (default) if you only want the D65 and a better RGB balance. This should be sufficient for most of you. In addition, these settings also form the basis for my color calibration with Calman Ultimate.
In the OSD, go to Picture Settings, Color Temp, User 1 and set the RGB settings. Set the brightness to 71, then you have 200 nits at 100 percent white.
Gray Scale, Saturation and ColorChecker (full calibration with Calman Ultimate)
Titan Standard Mode Calibrated
You can expect these values if you use the hardware and software at home. For your information, I have also attached the Calman Ultimate protocols regarding the corrected white point (RGB balance).
Gray Scale, Saturation and ColorChecker (CCT-Corrected)
If you use these white point settings for the sRGB or DCI-P3 mode, you already have a well-calibrated monitor that you can use for color-critical work.
In the OSD, go to Picture Settings, Color Temp, User 2 and set the RGB settings. Brightness 71 can be left as it is.
sRGB mode
sRGB Mode CCT Corrected
P3 mode
DCI-P3 Mode CCT Corrected
It is important to note that the white point settings in the OSD must be triggered manually when switching from standard to sRGB or from sRGB to DCI-P3. The fact that you have to switch from standard mode to sRGB is already complicated enough. Why you have to switch from sRGB to DCI-P3 from CCT user 2 to user 1 and back to user 2 is not only incomprehensible, but also annoying. Firmware bug! I would therefore stay in DCI-P3 mode and be done with it. This gives more color saturation when gaming and many people will probably like that better. If not, then use the sRGB mode.
Spectral distribution and “Eye-Safe”
The BOE panel has a strong red bias. Nevertheless, the RGB colors are well differentiated. Reminiscent of the KTC monitor we looked at recently.
Spectral distribution @ D65, 200 nits (100 % white window)
The peak here is at 632 nm – i.e. in the red light spectrum. In terms of eye-safe, the blue light component in the peak is exactly 457 nm. Can this still be described as eye-safe? I don’t think so. Titan Army offers the option of reducing the blue light component in several stages in the OSD. So it’s up to the end customer. I would like to point out that you then lose color accuracy!
Uniformity
As always, the image uniformity of an IPS panel depends a little on the panel lottery. My sample has its biggest weakness on the right edge. At least there is no dirty screen effect – IPS glowing and bleeding are limited in my sample. But that varies from panel to panel…
Image errors and other issues
Apart from the issues I’ve already mentioned, I couldn’t find any other problems with the P2510S. VRR via AMD FreeSync or NVIDIA G-Sync works without any problems – thanks to Adaptive-Sync. I don’t need to say any more about this.
Sound reproduction
The P2510S doesn’t have speakers. Sound via audio connection works without any problems.
Webcam and microphone
Are not installed. This brings us to the topic of HDR.
- 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
16 Antworten
Kommentar
Lade neue Kommentare
Mitglied
Mitglied
Moderator
Moderator
Urgestein
Urgestein
Urgestein
Urgestein
Moderator
Urgestein
Urgestein
Veteran
Urgestein
Moderator
Urgestein
Neuling
Alle Kommentare lesen unter igor´sLAB Community →