Home › Forums › Help and Support › DisplayCAL scale brightness
- This topic has 8 replies, 2 voices, and was last updated 5 years, 3 months ago by bilanciamist.
-
AuthorPosts
-
2019-01-21 at 13:32 #15334
Hi,
I’d like to calibrate the display of my Sony Vaio notebook with a Datacolor Spyder 3.
(Windows 10 – GeForce Go 330m – i7-740q – 1920×1080 – no rgb controls, just Windows screen brightness set to 100%)Used settings:
Spyder3 (with ArgyllCMS Drivers)
LCD (generic)
White e Black level drift compensation
Output levels: Auto
Correction: Auto (None)
6500°K
120.00 or 140.00 cd/m2
Black level: As measured
Gamma 2.2
Calibration Speed: medium or low
Profile type: XYZ LUT + matriz
Profile quality: medium or high
Testchart: Auto-Optimized 425 or 833 patches
Patch sequence: Minimize display response delayBut the resulting Luminance doesn’t match the target (max 95-96 cd/m2). The uncalibred white level is about 147 cd/m^2.
In the log Displaycal write:
Had to scale brightness from 140.000000 to 96.523598 to fit within gamut, corresponding to aprox. RGB 0.812022 0.780340 1.000000Is there a system to avoid this?
Enclosed is one of the measurement reports.
Thanks
Attachments:
You must be logged in to view attached files.2019-01-21 at 15:19 #15339Is there a system to avoid this?
Yes, by using the native white (“as measured”) of your notebook.
2019-01-21 at 16:20 #15341Tankyou Florian,
Using the native white is the only way?
The native white is about 4800-5000°K (report on uncalibrated display device), too warm for me.
2019-01-21 at 16:21 #15343Using the native white is the only way?
If you want maximum contrast (which seems likely, as the display already seems to be severely limited in that regard), then yes.
2019-01-22 at 11:09 #15359Ok, this is the log of a complete calibration and its measurement report, if you want to check it out.
in orange (8 Warnings):
Warning: Skipping RGB 1.96 1.96 1.96 XYZ 2.286474 2.437223 2.233692 because ↲
↳ Y is not monotonically increasingin red:
Brightness error = -0.266983 cd/m^2 (is 95.953157, should be 96.220140)
White point error = 0.359201 deltaE
Maximum neutral error (@ 0.036503) = 0.421062 deltaE
Average neutral error = 0.225407 deltaEProfile check complete, errors: max. = 2.623368, avg. = 0.292953, RMS = 0.516861
in the report – extended verification testchart (RGB + gray balance):
RGB gray balance (>= 1% luminance) combined Δa*00 and Δb*00 range 2.36 NOT OKthanks again
Attachments:
You must be logged in to view attached files.2019-01-23 at 17:06 #15429Hi,
I’d like to calibrate an external LG monitor as well, but i can’t set FullRGB output in HDMI \ Nvidia settings. (not even using CRU-Custom Resolution Utility).
in the log:
Detected limited range output levels
Using TV encoding range of (16-235)/255but i can use Ycbcr444 output
Which one is better?
Limited RGB output with limited RGB monitor or Ycbcr444 output with fullRGB monitor?
(The monitor can be set in both ways)
Thanks
2019-01-23 at 22:10 #15432Ycbcr444 output with fullRGB monitor?
YCbCr is always limited range.
2019-01-30 at 22:28 #15536Thanks for the reply.
After many tests i can get FullRGB on the LG monitor (with HDMI cable) only if i turn on LG “smart energy saving”.
RGB level 0 is 0.267215 cd/m2
RGB level 16 is 0.506990 cd/m2
Assuming full range output levelsMaybe is a false positive. I try to calibrate the monitor with this option on.
2019-02-01 at 13:30 #15549here is the report of the LG monitor calibration.
Attachments:
You must be logged in to view attached files. -
AuthorPosts