Home › Forums › Help and Support › Calibrate toward different color spaces?
- This topic has 17 replies, 3 voices, and was last updated 3 years, 4 months ago by Vincent.
-
AuthorPosts
-
2020-02-11 at 4:13 #22838
I just recently got a HP spectre x360 with OLED screen option and would like to calibrate it with my i1display pro. The laptop comes with an app to switch different colorspaces which seems to be just load different ICC profiles (see attached).
Is it advisable to calibrate my screen towards different color spaces and replace the factory profiles? AFAIK windows w/o HDR mode on is sRGB only and having profiles for WCG feels confusing.
- This topic was modified 4 years, 1 month ago by Ender.
Attachments:
You must be logged in to view attached files.Calibrite Display Pro HL on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.2020-02-11 at 15:06 #22865I just recently got a HP spectre x360 with OLED screen option and would like to calibrate it with my i1display pro. The laptop comes with an app to switch different colorspaces which seems to be just load different ICC profiles (see attached).
Is it advisable to calibrate my screen towards different color spaces and replace the factory profiles? AFAIK windows w/o HDR mode on is sRGB only and having profiles for WCG feels confusing.
It needs to do more that that, like some GPU powered gamut emulation based on HP app colorspace choice.
Validate each mode with DisplayCAL and check how they behave. Display autodimming may mess with verification/profiling.
If there is something wrong DisplayCAL may help you to correct white and grey (grey color & gamma) with a GPU calibration on top each mode. Gamut inaccuracies like sRGB being a liitle bigger that it should, or sorter cannot be corrected this way, it will need some vendor software.
Make sure to use RGB OLED correction for i1DisplayPro when measuring.
2020-02-19 at 21:47 #23032I just recently got a HP spectre x360 with OLED screen option and would like to calibrate it with my i1display pro. The laptop comes with an app to switch different colorspaces which seems to be just load different ICC profiles (see attached).
Is it advisable to calibrate my screen towards different color spaces and replace the factory profiles? AFAIK windows w/o HDR mode on is sRGB only and having profiles for WCG feels confusing.
It needs to do more that that, like some GPU powered gamut emulation based on HP app colorspace choice.
Validate each mode with DisplayCAL and check how they behave. Display autodimming may mess with verification/profiling.
If there is something wrong DisplayCAL may help you to correct white and grey (grey color & gamma) with a GPU calibration on top each mode. Gamut inaccuracies like sRGB being a liitle bigger that it should, or sorter cannot be corrected this way, it will need some vendor software.
Make sure to use RGB OLED correction for i1DisplayPro when measuring.
How do I validate the results? I usually just do the calibration and using all default settings and never looked into details. What exact parameter should I look into?
For example this is the profile info from measuring HP display control in “Default” mode:
Size 499500 Bytes (487.79 KiB)
Preferred CMM 0x6172676C ‘argl’ ArgyllCMS
ICC version 2.2
Profile class Display device profile
Color model RGB
Profile connection space (PCS) XYZ
Created 2020-02-11 22:17:50
Platform Microsoft
Is embedded No
Can be used independently Yes
Device
Manufacturer 0x0000834C
Model 0x00004142
Media attributes Reflective, Glossy, Positive, Color
Default rendering intent Perceptual
PCS illuminant XYZ 96.42 100.00 82.49 (xy 0.3457 0.3585, CCT 5000K)
Creator 0x4443414C ‘DCAL’ DisplayCAL
Checksum 0xC835300D23480D3D01A6E3578A8AB6D5
Checksum OK Yes
Description (ASCII) 16706 #1 2020-02-11 21-57 2.2 F-S XYZLUT+MTX
Copyright No copyright. Created with DisplayCAL 3.8.9.3 and
ArgyllCMS 2.1.2
Device model name (ASCII) 16706
Luminance 371.81 cd/m²
Media white point
Is illuminant Yes
Illuminant-relative XYZ 93.33 100.00 108.02 (xy 0.3097 0.3318)
Illuminant-relative CCT 6643K
ΔE 2000 to daylight locus 4.26
ΔE 2000 to blackbody locus 8.06
Media black point
Illuminant-relative XYZ 0.0000 0.0000 0.0000
Absolute to media relative transform Bradford (ICC recommendation)
Matrix 0.8951 0.2664 -0.1614
-0.7502 1.7135 0.0367
0.0389 -0.0685 1.0296
Video card gamma table
Bitdepth 16
Channels 3
Number of entries per channel 256
Channel 1 gamma at 50% input 1.24
Channel 1 minimum 0.0000%
Channel 1 maximum 100.00%
Channel 1 unique values 256 @ 8 Bit
Channel 1 is linear No
Channel 2 gamma at 50% input 1.24
Channel 2 minimum 0.0000%
Channel 2 maximum 100.00%
Channel 2 unique values 256 @ 8 Bit
Channel 2 is linear No
Channel 3 gamma at 50% input 1.25
Channel 3 minimum 0.0000%
Channel 3 maximum 100.00%
Channel 3 unique values 256 @ 8 Bit
Channel 3 is linear No
Device to PCS: Intent 0
Matrix 1.0000 0.0000 0.0000
0.0000 1.0000 0.0000
0.0000 0.0000 1.0000
Input Table
Channels 3
Number of entries per channel 2049
Color Look Up Table
Grid Steps 33
Entries 35937
Output Table
Channels 3
Number of entries per channel 2
Red matrix column
Illuminant-relative XYZ 52.75 24.64 0.05 (xy 0.6812 0.3182)
PCS-relative XYZ 56.68 26.32 -0.09 (xy 0.6837 0.3174)
Green matrix column
Illuminant-relative XYZ 22.83 69.62 4.69 (xy 0.2350 0.7167)
PCS-relative XYZ 26.06 69.19 4.32 (xy 0.2617 0.6949)
Blue matrix column
Illuminant-relative XYZ 17.75 5.74 103.28 (xy 0.1400 0.0453)
PCS-relative XYZ 13.68 4.49 78.26 (xy 0.1418 0.0466)
Red tone response curve
Number of entries 256
Transfer function ≈ Gamma 2.83 100% (Δ 3.82%)
Minimum Y 0.0000
Maximum Y 100.00
Green tone response curve
Number of entries 256
Transfer function ≈ Gamma 2.83 100% (Δ 3.82%)
Minimum Y 0.0000
Maximum Y 100.00
Blue tone response curve
Number of entries 256
Transfer function ≈ Gamma 2.83 100% (Δ 3.82%)
Minimum Y 0.0000
Maximum Y 100.00
Device to PCS: Intent 1
Matrix 1.0000 0.0000 0.0000
0.0000 1.0000 0.0000
0.0000 0.0000 1.0000
Input Table
Channels 3
Number of entries per channel 2049
Color Look Up Table
Grid Steps 33
Entries 35937
Output Table
Channels 3
Number of entries per channel 2
PCS to device: Intent 1
Matrix 3.1394 -0.7487 -0.3373
-1.3070 3.1691 0.1104
0.0690 -0.0581 2.4142
Input Table
Channels 3
Number of entries per channel 4096
Color Look Up Table
Grid Steps 33
Entries 35937
Output Table
Channels 3
Number of entries per channel 256
PCS to device: Intent 0
Matrix 3.1394 -0.7487 -0.3373
-1.3070 3.1691 0.1104
0.0690 -0.0581 2.4142
Input Table
Channels 3
Number of entries per channel 4096
Color Look Up Table
Grid Steps 33
Entries 35937
Output Table
Channels 3
Number of entries per channel 256
Characterization target [24683 Bytes]
Characterization device values [24683 Bytes]
Characterization measurement values [24683 Bytes]
Chromaticity (illuminant-relative)
Channel 1 (R) xy 0.6812 0.3182
Channel 2 (G) xy 0.2350 0.7167
Channel 3 (B) xy 0.1400 0.0453
Make and model
Manufacturer 0x4C83
Model 0x4142
Metadata
prefix EDID_
CMF_
DATA_
MEASUREMENT_
OPENICC_
ACCURACY_
GAMUT_
EDID_mnft SDC
EDID_mnft_id 19587
EDID_model_id 16706
EDID_date 2019-T19
EDID_red_x 0.6796875
EDID_red_y 0.3193359375
EDID_green_x 0.232421875
EDID_green_y 0.71875
EDID_blue_x 0.1396484375
EDID_blue_y 0.0439453125
EDID_white_x 0.3125
EDID_white_y 0.3291015625
EDID_gamma 2.2
EDID_md5 f1075cfad448ffc9df400579752af06b
CMF_binary DisplayCAL
CMF_version 3.8.9.3
CMF_product DisplayCAL
License Public Domain
Quality high
OPENICC_automatic_generated 0
DATA_source calib
MEASUREMENT_device i1 displaypro, colormunki display
ACCURACY_dE76_avg 0.124121
ACCURACY_dE76_max 2.335873
ACCURACY_dE76_rms 0.286254
GAMUT_volume 1.71706184818
GAMUT_coverage(dci-p3) 0.9997
GAMUT_coverage(srgb) 1.0001
GAMUT_coverage(adobe-rgb) 0.955- This reply was modified 4 years, 1 month ago by Ender.
2020-02-20 at 16:32 #23037DispayCAL, verification tab (verify icon) on the right.
For color managed apps just check if display & profile match and if whitepopint and grey range are OK to your requirements.
For validating HW calibration of stuff like that laptop gamut emulation to some colorspace just do the same and set simulation colorspace to whatever you tried to emulate + use simulation profile as display profile.
For validating HW calibration or stuff like that laptop gamut emulation to some colorspace PLUS some further whitepoint or gamma or grey correction done with DisplayCAL you may want to just validate if Displaycal profile matches display and/or use HCFR or tools like that.
2020-02-24 at 18:29 #23158DispayCAL, verification tab (verify icon) on the right.
For color managed apps just check if display & profile match and if whitepopint and grey range are OK to your requirements.
For validating HW calibration of stuff like that laptop gamut emulation to some colorspace just do the same and set simulation colorspace to whatever you tried to emulate + use simulation profile as display profile.
For validating HW calibration or stuff like that laptop gamut emulation to some colorspace PLUS some further whitepoint or gamma or grey correction done with DisplayCAL you may want to just validate if Displaycal profile matches display and/or use HCFR or tools like that.Well, this is from when the HP control was set to default, look pretty bad isn’t it?
However whenever I tried to load a DisplayCal profile it overwrites HP’s original and made things worse (the whole screen looks yellow), am I missing something?
Attachments:
You must be logged in to view attached files.2020-02-24 at 19:16 #23160Report shows that with that correction white in not white but somehow green. Also shows that grey is not grey, has “color” relative to its white, pikish on some greys, greenish in others. It should be visible in a non color managed gradient.
So choose the lesser evil, banding or that grey. With that results I think that it’s better to have these grey issues solved. Color tint because of banding in greys is going to be less noticieable than such huge grey range.
2020-03-04 at 17:40 #23458Report shows that with that correction white in not white but somehow green. Also shows that grey is not grey, has “color” relative to its white, pikish on some greys, greenish in others. It should be visible in a non color managed gradient.
So choose the lesser evil, banding or that grey. With that results I think that it’s better to have these grey issues solved. Color tint because of banding in greys is going to be less noticieable than such huge grey range.Well, I set the HP control to native and run a calibration/profile. After applying profile (while HP control is still set to native) this seems much better?
Though I don’t understand why it thinks the Measured vs. assumed target whitepoint is bad as it’s only 6379K vs 6400K?
- This reply was modified 4 years ago by Ender.
Attachments:
You must be logged in to view attached files.2020-03-04 at 17:59 #23461Report shows that with that correction white in not white but somehow green.
Though I don’t understand why it thinks the Measured vs. assumed target whitepoint is bad as it’s only 6379K vs 6400K?
Because as you may see in other threads o even wikipedia color correlated temperature is not a valid mean for measuring color distance. It could be 6500K CCT and be be 10dE00 off
2020-03-04 at 18:35 #23462Report shows that with that correction white in not white but somehow green.
Though I don’t understand why it thinks the Measured vs. assumed target whitepoint is bad as it’s only 6379K vs 6400K?
Because as you may see in other threads o even wikipedia color correlated temperature is not a valid mean for measuring color distance. It could be 6500K CCT and be be 10dE00 off
OK…so does the new report show a better result?
2020-03-04 at 19:20 #23463It says white is not white and grey has severe oscillations for a calibrated screen. Since there is no other “calibrated” report to compare it is not better or worse.
It is not good IMHO even if we assume that that white is “white” to your eyes, grey is not good (combined Δa*00 and Δb*00 range). Fast calibration configurations and XYZLUT at the same time is a mostly useless combination if display is not very good from the start, but YMMV.Also that report does not compare your display to sRGB. It test how Photoshop (or other color managed app) will behave showing sRGB images if we suppose high precision calculations & dither (which PS does not have in all systems).
2020-03-11 at 20:18 #23596It says white is not white and grey has severe oscillations for a calibrated screen. Since there is no other “calibrated” report to compare it is not better or worse.<br>
It is not good IMHO even if we assume that that white is “white” to your eyes, grey is not good (combined Δa*00 and Δb*00 range). Fast calibration configurations and XYZLUT at the same time is a mostly useless combination if display is not very good from the start, but YMMV.
Also that report does not compare your display to sRGB. It test how Photoshop (or other color managed app) will behave showing sRGB images if we suppose high precision calculations & dither (which PS does not have in all systems).I have managed to adjust the RGB manually using intel’s graphics control panel, now the report shows whitepoint OK. I think now it’s better?
- This reply was modified 4 years ago by Ender.
Attachments:
You must be logged in to view attached files.2020-03-11 at 21:03 #23599Yes… but because you have full GPU calibration on that report, so no need to use intel control panel at all, just a visual whitepoint editor or a named white like D65.
Also fast calibration configurations and XYZLUT at the same time is a mostly useless combination if display is not very good from the start, but YMMV.
2020-03-14 at 3:39 #23627Yes… but because you have full GPU calibration on that report, so no need to use intel control panel at all, just a visual whitepoint editor or a named white like D65.
Also fast calibration configurations and XYZLUT at the same time is a mostly useless combination if display is not very good from the start, but YMMV.
Could you elaborate more? I used the control panel to adjust the RGB in the interactive monitor part, which you usually use OSD control to make sure they are balanced.
Without that just running calibration via DisplayCal only results in the greenish white. I am not aware how to adjust R G B individually on a laptop in another way
2020-03-14 at 13:49 #23629That control panel implies no modification of “inber behavior” of laptop’s display panel, it’s just GPU trick. DisplayCAL can do/ actually does more or less the same using GPU LUT in several ways when it calculates calibration: visual white point editor (read doc) or some color coordinates (which may render tint if colorimeter correction does not match, or if there is some observer metameric failure)
- This reply was modified 4 years ago by Vincent.
2020-11-27 at 16:03 #27045@Ender, did you get this to work?
I am considering using DisplayCAL to profile my 13″ spectre x360 OLED as well.
The HP profiles are just so grossly inaccurate. Right now I have some approximately correct settings that I manually set in the intel app to correct the horrendous yellow-green whites.
I tried using the HDR mode which works well now for the most part, but the grayscale is magenta on one step and green on the next step that the HDR mode is unusable without a proper profiling / calibration.
-
AuthorPosts