- This topic has 40 replies, 5 voices, and was last updated 11 months, 1 week ago by
.
-
Posts
-
- Offline
It’s an spectrophotometer… but a cheap one. It creates corrections for other devices if you take this device measurements as “reference”. Not my recomendation, even for printing.
Than this is not for calibration the whole display, just to create corrections for other devices like i1, do i understand it correct? That is never said in the argyllcms documentation about this device! How should one know this?
If you do not want to spend money, and since you have a visual “Valid” (by your judment) white D65 reference… just use the Spyder with an alternative whitepoint as instructed at the start of page 2 (-w param for target whitepoint). That’s all
Not in the next few months, but maybe in a half a year! My question was for the future! But honestly i don’t want to gbuy a i1 and rely on others correction profile. Do you see how much correction profiles for the i1 and my display in combination are avaiable in the database? then i have to worry which is correct now? no thanks! When i open this files, i see different correction values.
I really tought i could buy this spectrometer and be happy without worry about anything and it just works fine… looks like i was wrong…
- Offline
I just use the factory calibrated display mode for the display, and load the gamut profile icc in wayland. AS mentioned before from DaniJ!
Incidentally, my original question for today was which profile I need to load into the operating system: the genuine “original color space profile” or the one with primary colors modified for BenQ. DaniJ said primary colors. I also asked you, but I didn’t receive an answer or didn’t understand it due to the language barrier.
Do i need to load the Display P3 color profile form the international color consortion downloaded or from apple itself that publishes this color space gamut, or the Display P3 from BenQ with special primaries changed for the monitor?
CCSS, which i1d3 can use, store only display information. “colorimeter” information about its “raw inaccuracy” is in i1d3 firmware, that’s why we can share them for similar displays.
Everyone here recommends the i1, but to be honest, I don’t want to buy a new device and then have to rely on correction profiles for colorimetri uploaded by others. Not at this price for 300 or more. I’d rather use another device that works without a correction profile, if possible, and spend a little more on it. That way, I won’t have any more headaches!
Does the Calibrite Colorchecker Studio also need to load a correction file for each different display technology, or does it also require ccss or ccmx or something similar? Which device do I need if I simply want to calibrate without having to think about what type of monitor I have and to ensure that everything is completely correct?
Here the product link:
https://calibrite.com/us/product/colorchecker-studio/You were given multiple avenues toward the goal of simplicity+accuracy+budget already. If nothing else, I’ll leave with this: The colorimeter needs to know the spectrum of the panel. There are specific PFS corrections for i1D3 which are independently vetted, and the hardware is viable for almost any future panel tech. The corrections for Spyder X are factory locked and lack parity with panel types on the market today. You can use your Spyder X around a visually derived white-point if you don’t want to make an additional purchas now. A spectrometer has different limitations, slow operation and near black accuracy drops, it’s not a smart investment.
SpyderX Pro on Amazon Calibrite ColorChecker Studio on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.
- Offline
If you do not want to spend money, and since you have a visual “Valid” (by your judment) white D65 reference… just use the Spyder with an alternative whitepoint as instructed at the start of page 2 (-w param for target whitepoint). That’s all
I know you mean well, but I’m not going to do something I don’t understand and then possibly do it wrong! Also my judgment can also be wrong, i only said, the SpyderX is definitely wrong, i never said that the factory profile is fully correct! And i just don’t understand this whole whitepoint adjustment and what this exactly does!
I just use the factory calibrated display mode for the display, and load the gamut profile icc in wayland. AS mentioned before from DaniJ!
Incidentally, my original question for today was which profile I need to load into the operating system: the genuine “original color space profile” or the one with primary colors modified for BenQ. DaniJ said primary colors. I also asked you, but I didn’t receive an answer or didn’t understand it due to the language barrier.
Do i need to load the Display P3 color profile form the international color consortion downloaded or from apple itself that publishes this color space gamut, or the Display P3 from BenQ with special primaries changed for the monitor?
Not worth bothering with those. You will be better off setting the display to sRGB mode in OSD, and the OS and apps to assume an sRGB display,
- Offline
You were given multiple avenues toward the goal of simplicity+accuracy+budget already. If nothing else, I’ll leave with this: The colorimeter needs to know the spectrum of the panel. There are specific PFS corrections for i1D3 which are independently vetted, and the hardware is viable for almost any future panel tech. The corrections for Spyder X are factory locked and lack parity with panel types on the market today. You can use your Spyder X around a visually derived white-point if you don’t want to make an additional purchas now. A spectrometer has different limitations, slow operation and near black accuracy drops, it’s not a smart investment.
All talks about the i1D3, but in my country there is only one device that looks like something the same, the Display Pro HL from Calibrite. Is it exactly a i1D3? https://calibrite.com/product/display-pro-hl/
If you do not want to spend money, and since you have a visual “Valid” (by your judment) white D65 reference… just use the Spyder with an alternative whitepoint as instructed at the start of page 2 (-w param for target whitepoint). That’s all
And i just don’t understand this whole whitepoint adjustment and what this exactly does!
Imagine that you have a perfect colorimeter. You may want to calibrate to D65… or maybe you want to calibrate to D50 or other value.
Calibration app, let be it ARgyllcms or someother app will measure current whitepoint difference to your target (d65 or whatever) and guide you with 3 RGB gain bars to achieve it.
Right?
Using alt whiteopoint you are saying to caibration app = I want to keep MY curent white point (in your OSD preset scenario) or I want to aim to something else that is not D65.
Calibration app will say, OK, the 3 RGB bars are aligned, white is ok, go to next step.The next step not matter if you aim to D65 or D50 or some arbitrary “xy” whitepoint is to make grey the same color as white and behave going from blacl to white with certain gamma, so for a set of greys it will correct them individually in a table, VCGT, “grey calibration” that is loaded into GPU.
That’s all.
Color managed apps do not care at all about using alt whitepoints, and “as long as colorimeter error on each primari is not so big” (in an oversimplification this is what photoshop is going to read in a profile)… all is OK.
That’s why visual whitepoint editor exist in DisplayCAL or high end Hardware calibration like Eizo, to do visually matching to some non standarized booth for print evaluation or to deal with these kind of color differences.So using alt wp is the 2nd easiest solution. The 1st easy one is using the standard profile that each OSD preset is simulation as display profile (REMEMBER, standard profile for each preset, NOT Benq factory profile), but this 1st one assumes that grey is perfect and may be not. Your spyder is able to measure this to a high degree even if it measures white wrongly.
You were given multiple avenues toward the goal of simplicity+accuracy+budget already. If nothing else, I’ll leave with this: The colorimeter needs to know the spectrum of the panel. There are specific PFS corrections for i1D3 which are independently vetted, and the hardware is viable for almost any future panel tech. The corrections for Spyder X are factory locked and lack parity with panel types on the market today. You can use your Spyder X around a visually derived white-point if you don’t want to make an additional purchas now. A spectrometer has different limitations, slow operation and near black accuracy drops, it’s not a smart investment.
All talks about the i1D3, but in my country there is only one device that looks like something the same, the Display Pro HL from Calibrite. Is it exactly a i1D3? https://calibrite.com/product/display-pro-hl/
i1d3 is a family of products created by Xrite and licensed to some others, all using the same or very close HW principes, and they are commercialized with some variations in HW or being able to work with some 3rd party commercial software
– xrite colormunki display / calibrite colorchecker display / display sl —> the “lite” version, some commercial software will refuse to run with them by some firmware check
-i1display pro, calibrite colorchecker display pro, display Pro HL / Plus HL —> teh different “Pro” versions
-NEC/Wacom/HP/Asus/Quato versions of i1displaypro —> the vendor labeled Pro versions, equal to the retail pro above
-Calman C6 and C6 HDR variants… —> same as the “pro” but whiel in calman app recognizes it and unlocks some “software only” capabilities in calman app, thus not related to i1d3 hardwareAll the same hardware with minimal variations. All the same “physical form”. If you see one i1d3 you have seen all the others.
I’d start with assigning to each OSD a standard profile like ArgyllCMS “ref/DisplayP3.icm”. Even if white point measures off by spyder, there are lots of things that you can check this way.
If grey is not OK in that setting, visually by seeing color tint in some greys, or by measurement (a*b* deviated from 0 in greyscale) proceed with calibrating to an alternative whitepoint that maches your “visually good whitepoint” at Display P3 preset. Do full profilling after calibrating and live with it till you can rent an i1Pro, or get an i1d3 or something else
- Offline
The next step not matter if you aim to D65 or D50 or some arbitrary “xy” whitepoint is to make grey the same color as white and behave going from blacl to white with certain gamma, so for a set of greys it will correct them individually in a table, VCGT, “grey calibration” that is loaded into GPU.
Thank you, i do understand now, and it is important, than now i can say you this: I use Wayland on Linux, and in Wayland, the argyllcms and also DisplayCAL can’t load a VCGT during calibration. That means, in Wayland, you can only set the whitepint by manual, then abort the calibration process and go directly to profiling! For DisplayCAL, it is all describen from the desktop environment developer itself iirc: https://planet.kde.org/xavers-blog-2024-07-15-how-to-profile-your-display-in-the-plasma-wayland-session/
This also means maybe, i can’t check the greys cause this process is maybe performed during calibration, not curing profiling?
Remember that the steps in ArgyllCMS are:
1. Whitepoint and brightness setting with dispcal in OSD, then calibration afterward with dispcal (this last step don’t work in Wayland)
2. Generating testcharts with targen
3. Read testcharts with dispread (IF a calibration is done, load the calibration during this process)
4. Generating the ICC ProfileBy the way this issue is already well known for Wayland Linux. You can’t calibrate in Wayland, only profiling the monitor! But my question is, does this affect the 2nd solution? And is in this case a i1d3 also worth?
And thanks for the explanation of the different branding names for the i1d3!
Do full profilling after calibrating and live with it till you can rent an i1Pro, or get an i1d3 or something else
This devices aren’t available via renting or as used here. I have to buy a new one i if i want one. And importing is no solution cause big taxes!
If we trust the primaries stored in the manufacturer provided BenQ PD2725U.icc, it shows the green within the P3 triangle, far from the AdobeRGB green. If you paint a full red and full green patch and change between the native and P3 OSD modes, do you see any difference? Does the saturation change? This will help determine if the profile primaries are the native ones or the P3 “simulated” ones.
