Great writing, I didn't know about it. It follows the same path I used (only that I used DisplayCal's GUI), so it saves me from writing it ;)
My config on DisplayCal (and some comments): --Display & instrument: In the particular case of the SpyderColor5 you should first use the menu "Tools/Import colorimeter corrections from...", and extract those corrections from the SypderColor software (pointing DisplayCal to the windows installer should be enough). These proprietary corrections match the color response of the colorimeter to the particular light source of the monitor. Then: - chose the instrument mode that correspond to your monitor technology (for your Benq GW2765 it should be White LED if I'm not mistaken). - optionally enable white and black level compensation (not strictly necessary for a LED IPS panel, it's a trade-off of longer times for a marginally better profile in this case) - leave correction at Auto, it knows what to do (if you used a proprietary mode for the instrument it will use None, as the correction is already done by the colorimeter itself). --Calibration: As mentioned in Pascal's post, you can use "Tools/Report on uncalibrated device" to check the base properties of the monitor (remember to reset all color/contrast options before). This will give you an idea of how far the monitor is from your objective: the farther it is, the more artifacts you'll get in the end. For example, trying to calibrate a monitor with a natural color temperature of 8500K (very bad laptops) down to 6500K will probably result in horrible color banding. - color temperature = 6500K (unless you have some specific needs) - white level = as measured - tone curve = gamma 2.2 (unless it's a Mac or other monitor with gamma close to 1.8) - calibration speed = high For a desktop monitor with color/gamma controls the best procedure is to first use those hardware controls to get as close as possible to the objective, and only latter do the calibration. In order to do that, check the option "Interactive display adjustment": before starting the calibration DisplayCal will show you a real time estimation of color temperature and brightness. Use the RGB controls of the on-screen monitor menu to get close to 6500K, and use the brightness controls to get close to 130cd (you'll need to iterate as one affects the other). Once you get something reasonably close, start the calibration. This ensures that the software corrections will be smaller, reducing the chances of artifacts. Very important: note down all the values of the on-screen monitor menu, the calibration is only valid for those values (change them and you'll need to recalibrate). --Profiling: -profile quality = high -test chart = auto optimized -amount of patches = 425 These settings are a good compromise of a moderately long profiling session (a couple of hours) for a high quality profile. I hope this helps! Regards, Guillermo On Tue, Apr 25, 2017 at 2:55 PM, johannes hanika <[email protected]> wrote: > you've seen pascal's old writeup about display colour profiling, right? > > https://encrypted.pcode.nl/blog/2013/11/24/display-color-profiling-on-linux/ > > -jo > > On Wed, Apr 26, 2017 at 5:35 AM, Guillermo Rozas <[email protected]> wrote: >>> As per https://wiki.archlinux.org/index.php/ICC_profiles >>> >>> "Note that the system on which the profile is generated must host the exact >>> same video card and monitor for which the profile is to be used" >>> >>> And this contradicts to some extend with >>> >>> http://www.colorwiki.com/wiki/Cross_Platform_Color >>> >>> "They will function the same way on any operating system, and can be easily >>> moved from machine to machine." >>> >>> I am actually using 2 different machines with 2 very different cards (one >>> windows and one linux). I think one item that changes the behavior a lot is >>> the color temperature. I set it manually to 6500K. Windows would set to this >>> value by default while Linux would try to set to 7600K by default. On sRGB - >>> windows came at 100% and linux came at 99.9 while Adobe RGB came at 81% >>> windows vs 79% linux. >> >> Yes, I think the colorwiki link was referring mainly to printers, is a >> bit misleading (my bad to include it here). Is the same discussion as >> with the driver: in principle the graphic card should not affect the >> colors that are sent to the monitor, but graphic cards can be so >> different between them that in practice it does matter. Same >> generation of the same vendor may be OK, two completely different GPU >> is probably not safe. >> >> And yes, color temperature is very important: the profile tries to >> match the color temperature you ask for, so a profile with a target of >> 7600K will look a lot bluer than one with a target of 6500K. You >> probably want 6500K, as that is the standard for monitor viewing. >> Brightness is also important, to a lesser degree. >> >>> There are just a lot of options in Display Cal and even there is >>> documentation - some areas are lacking detailed explanation for a beginner. >> >> Yeah, it also took me a while to understand which options to use, and >> even after deciding I was second guessing my configuration all the >> time. I'll post tonight the options that I found the most "sane", >> maybe it's helpful for you as a start point. If I find the time I'll >> try to also write a small walk-through of what I did when I calibrated >> my monitor (including the color temperature options). >> >> Regards, >> Guillermo >> ____________________________________________________________________________ >> darktable user mailing list >> to unsubscribe send a mail to [email protected] >> > ____________________________________________________________________________ > darktable user mailing list > to unsubscribe send a mail to [email protected] > ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
