Home › Forums › Help and Support › Same monitor and colorimeter as before, but very bad results on
- This topic has 9 replies, 4 voices, and was last updated 4 months ago by
Vincent.
-
AuthorPosts
-
2026-01-27 at 19:42 #145409
When running Displaycal on my old PC (Nvidia GTX680, Windows 10) about 14 months ago it gave me decent results. Whitepoint was reported to be around 6600K (the monitor is set to its native 6500K), the RGB settings only had to be slightly adjusted on the monitor, and profiling worked.
But on my new PC (RTX 5060, Windows 11) I get very bad results. The whitepoint differs between 7000 and 7800, green has to be lowered to 40 and red and blue increased to around 55, and something goes very wrong during profiling creating a really bad result. I get a lot of “inverting Jacobian failed”. Something seems to happen when dark red colors are being measured.
I still have the same monitor (PA278CV) and the same Colormunki Display as I had with my old pc.
If I try the software that came with the Colormunki Display I get decent results, so it seems that the colorimeter is not broken?
Any ideas what I can try to do to make Displaycal work? Other Argyll drivers, downgrading Displaycal, whatever. I’m not sure what to try.
Calibrite Display SL on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.2026-01-27 at 20:42 #145410Im thinking Windows 11 problem. Your display video settings not on hdr or ACM ? Version of displaycal? 3.8.9.3 is working for Windows 10 and 11.
2026-01-28 at 8:38 #145411It seems that you are not applying a the same colorimeter correction than in your previous setup, or the default one in munki software (likely to be White LED)
2026-01-29 at 9:39 #145412If your whitescreen calibration looks wrong (whitepoint too high and colors off), it’s likely a DisplayCAL + RTX/Windows 11 driver issue, not the sensor. Try disabling HDR/Night Light, resetting NVIDIA color settings, and using updated Argyll drivers
2026-01-29 at 14:44 #145413Thanks for your replies!
ACM, HDR etc. is all disabled in Windows.
I also realized that I have an old HTPC connected to my TV (with integrated Intel graphics and Windows 10) so I tried connecting my monitor to it and measured the color temperature and RGB values with the Colormunki and I get the exact same readings (see attached jpg) as on my new PC. Red and blue is a bit low and the green way too high, and the color temp is pretty far from 6500K. If those readings where correct it feels like there would be a clear green tint?
So I guess it’s either the colorimeter or the monitor that’s broken?
The monitor looks good to the naked eye. At least there are no obvious weird things going on. Looking at test images (like http://www.lagom.nl/lcd-test/all_tests.php) everything looks fine. All I can see is a little bit of black crush.
I forgot to mention in the original post that the Colormunki is quite old. It says 03/2016 on the label so almost ten years old. I don’t know how much or how fast these models wear out?
Maybe I’ll just have to take a chance and buy a new one.
Attachments:
You must be logged in to view attached files.2026-01-29 at 19:41 #145418It seems that you are not applying a the same colorimeter correction than in your previous setup, or the default one in munki software (likely to be White LED)
Let me tap the sign again ^^^^^^
2026-01-30 at 3:09 #145419I do not think a ColorMunki Display has a limited life. some Colormunki are spectrometers and some are colorimeters. A spectrometer does require certification every year. Is there a spectrometer that does not ?
“If I try the software that came with the Colormunki Display I get decent results, so it seems that the colorimeter is not broken?” . This indicates it is not the meter.
-
This reply was modified 4 months ago by
Ben.
2026-01-30 at 12:03 #145421It seems that you are not applying a the same colorimeter correction than in your previous setup, or the default one in munki software (likely to be White LED)
Let me tap the sign again ^^^^^^
I’m pretty sure I used the LCD White LED Family correction the last time, since that’s what it says in the verification file that I saved back then. But it doesn’t seem to work now. I’ve also tried I handful of random corrections from the list just to see what happens, but it doesn’t change much. The RGB bars look pretty much the same, and the color temp differs with a few hundred K ( roughly 7100 – 7500).
I do not think a ColorMunki Display has a limited life. some Colormunki are spectrometers and some are colorimeters. A spectrometer does require certification every year. Is there a spectrometer that does not ?
“If I try the software that came with the Colormunki Display I get decent results, so it seems that the colorimeter is not broken?” . This indicates it is not the meter.
Yeah, I find that a bit odd as well. But the problem with the Colormunki software is that it’s very primitive. It doesn’t measure many patches (only takes a few minute to complete a full calibration/profiling) and there’s no way to see what readings (R-G-B and color temp) it gets. I also noticed that it had changed the monitor OSD setting to 5500K, maybe in an attempt to get closer to 6500K.
Is there any other free software I could try? I’ve been googling a bit but haven’t found anything yet.
2026-01-30 at 15:35 #145422HCFR is very popular. Unfamiliar with ColorMunki but HCFR does work with it. https://github.com/arthur-liberman/hcfr-code/releases
ARGYIICMS should be able to compare them both to.
2026-01-30 at 22:56 #145423An easy test is to open notepad.exe, place muki over its white window (on the center to avoid uniformity errors), then on command line and assuming it’s on PATH
sportead -X path_to_ccss_correction.ccss
plus the additional parameters you want to play with
https://www.argyllcms.com/doc/spotread.html“-x” may be an interesting option to add since it outputs CIE xyY instead of CIE XYZ, so you can make comparisions with other tools easier.
DisplayCAL is calling ArgyllCMS under teh hood so to discard any issues in new DisplayCAL py3 or the ond one (3.8.9.3) a command line test should be mandatory.
*IF* there is a mismatch with another tool using the same CCSS/EDR, report it to ArgyllCMS mail list-
This reply was modified 4 months ago by
Vincent.
-
This reply was modified 4 months ago by
-
AuthorPosts