I created a cross-platform calibrator at https://github.com/bson/displaycraft/, with releases for macOS, Windows 11, and Linux (KDE+Wayland, KDE or GNOME + Xorg). The reason was my i1Display Pro spectro was getting completely obsoleted - the old software no longer runs on either Windows OR macOS, and the minimal support on Linux required Xorg, with nothing working with Wayland. (GNOME doesn't work on Wayland, because it can't have color management completely disabled.)
There's a list of spectros and colorimeters supported... I'd love to get some feedback on it. It's uses the same toolkits and ui libraries as the recent ArtCraft software, for a reasonably similar look and feel. Under the hood it uses the crossplatform ArgyllCMS, although it's a modified fork (because the author made it clear he had no plans to add support for Wayland).
It's a pretty straightforward profiler. Pick an instrument, pick a monitor, set intent parameters, measure and build profile, then verify the corrected display with the new profile installed. It does have a small trick up its sleeve: it tags the ICC profiles with a custom tag to remember the intent, and can later measure and create a profile to match the previous one; this is part to correct for drift, and part to be able to match a group of displays (probably best done for a batch of the same make and model for a small shop).
Anyway, if you have a suitable display measurement device (ColorMunki and i1Display Pro are the same, more or less) I'd love to hear some feedback.
Beware that modern "Art" LCDs often have such extremely dark blacks that measurement of black or close to black can take a long time.
It can create either Matrix or LUT profiles. With a modern, quality LCD, it's likely already going to be so linear that a Matrix profile performs exactly the same if not better.
There's also an adjustment mode where it cycles the spectro through black-mid-white and updates three bar graphs. The center line is the specified brightness for that point, and the number underneath is temp deviation in K. The purpose of this is mainly to manually adjust the monitor to be as close as possible to reduce the amount of "work" the profile has to perform.
Jan Brittenson wrote:
I created a cross-platform calibrator [...]
I have the Photomunki device and it works well here using it with Windows 11 and CCStudio software. I would have thought the CCStudio supported i1 Display pro as well?!
Anyway, I can check this out tomorrow sometime (I'm in Europe).
It's modeled on DisplayCAL and does pretty much the same thing. I just always found DisplayCAL a bit problematic and kinda spotty in what it run on (platform wise).
Jan Brittenson wrote:
It's modeled on DisplayCAL and does pretty much the same thing. I just always found DisplayCAL a bit problematic and kinda spotty in what it run on (platform wise).
Great, I will check it out later!
Most of my Eizos have the aurocalivration, but there is one ColorEdge offsite that has the USB hockey puck that came with it in ~2019. I think it is some kind of i1 Display device, but not sure of the model and if it works with your software.
Mostly I use DisplayCal on laptops lately since I have an i1 Display Pro, but sometimes it does not load the profile and I have to do it manually. I recall it was not an issue with the older natural W10 laptops, but more with the W11 and newer chipsets. I hope it works reliably on a Strix Halo APU.
At first everything went well. The instrument (Colormunki) was found.
At the next step, somewhat unclear instructions on screen about setting the screen controls, there was no Next button but instead a button on the current window "Parameters": The device was lost and couldn't be found again by the software when I went back to the previous step.
Giving up.
This was on an old laptop running Windows 10 Home 22H2, I haven't tried it on my main win11Pro.
You don't need to use the on-screen controls at all. Maybe I should move it and some of the other settings into an "Advanced" section. The only thing that matters is picking color temp, e.g. D65, then the rest can be display native.
The rest is just optimizations. For example, the display native black (assuming there is some backlight leak-through) and native white aren't going to be 6500K for D65. Changing the color of white requires losing brightness, and changing the color of black requires adding to it, making it less black. A display with separate RGB gain controls will allow setting the whitepoint. But then this also affects the midpoint, and calibrating for it shrinks the gamut where it matters most - around the midpoint. So the wording is difficult because it's about tradeoffs, and for solving specific problems. If there are no problems, and nothing needs optimizing, it can just be ignored...
So maybe a simple and a more elaborate advanced flow is a good idea. The basic flow could have next/back buttons that move up and down the steps on the ladder to the left, or it can remove the ladder altogether.
The devices, all of them that I've seen, are pretty funky and unreliable, so requires the software to keep reconnecting and resetting to resume.
Jan Brittenson wrote:
You don't need to use the on-screen controls at all. Maybe I should move it and some of the other settings into an "Advanced" section. The only thing that matters is picking color temp, e.g. D65, then the rest can be display native.
The rest is just optimizations. For example, the display native black (assuming there is some backlight leak-through) and native white aren't going to be 6500K for D65. Changing the color of white requires losing brightness, and changing the color of black requires adding to it, making it less black. A display with separate RGB gain controls will allow setting the whitepoint. But then this also affects the midpoint, and calibrating for it shrinks the gamut where it matters most - around the midpoint. So the wording is difficult because it's about tradeoffs, and for solving specific problems. If there are no problems, and nothing needs optimizing, it can just be ignored...
So maybe a simple and a more elaborate advanced flow is a good idea. The basic flow could have next/back buttons that move up and down the steps on the ladder to the left, or it can remove the ladder altogether.
The devices, all of them that I've seen, are pretty funky and unreliable, so requires the software to keep reconnecting and resetting to resume. ...Show more →
An interface that is more intuitive and possibly including a choice between simple and advanced mode is a good idea!
Your last sentence... I don't know... when using the Photomunki and ccSudio I never run into any need of connecting or reconnecting. The same with Dispalycal/Argyll. The old original software when going to Windows 10 however, that is another story.
Now I run a Benq monitor as my main monitor and use the Palette Master software and again, the Photomunki stays connected all the time.