- This topic has 8 replies, 3 voices, and was last updated 7 months, 2 weeks ago by
.
-
Posts
-
Just installed Windows 11 after buying a larger harddrive.
Trying to calibrate my display with a efi ES-1000 (GretagMacbeth) freezes the displaycal software at various times during the process. (Typically at the end of a calibration epoch, when the color window is closing / when “calibrating new calibration curve”, or one time I arrived at a later step).
Having spent the last 1.5 hours trying to get a calibration done, I’m not sure what else I can try.
Trying to run “as administrator” now.
Will try a further USB cable, but it does not look like a cable failure to me.
I already switched to as USB 2.0 Port, but that did not remedy the problem.It would be nice if the software would give me more info about what is happening / check it’s own state and if in an unresponsive state, at least give the option to exit gracefully and have some information / a log file to get the chance to understand what went wrong.
Thankful for any help / ideas.
Now it hangs on “Measuring color swatches for characterization…” / “Re-seeding”.
Symptom: I see that the “Elapsed time” is not increasing anymore. If I use the mouse to interact with the displaycal window, it will show me “Measuring color swatches for characterization… (Not Responding)” in the titlebar.
New cable did not help – but it ran longer than before. Nevertheless: The “not responding” happens in situation where the device is not moved. I don’t believe it’s the cable.
Trying: Generic LCD device (instead of Generic HighRes LCD device), using Win7 Compatibility mode as administratior. No White and Black point drift compensation.
If that’s not working, I’m giving up :/
Which displaycal version?
What type of install did you do? A clean install is best. Backup everything to old drive and install fresh to the new. Troubleshoot Windows. Could be the pagefile or systemfile are messed up. Did all the updates? Video drivers updated? Windows Event viewer is a troubleshooting tool. What process’s failed? A version conflict? Accidental loosend or dusted dirt on memory chips? That is grasping straws but it could be anything. Run chkdsk /R. And use the dism tool to check for system corruption. Reinstall Displaycal 3.8.9.3 .
Did you run a test on the CPU and GPU like Cinebench? Monitor your cpu temp and voltages with HWINFO x64.
I do not have that device so I do not know.
Update:
I was able to get SOME profile back yesterday. I am not convinved that this was somethign other than sheer luck because:
When saving the profile, the program froze again! There was a window where the only button was to allow me to “Cancel” the saving process.
That window was frozen.Fortunately, something was already saved to disc.
Unfortunately, for all (or most or some?) other runs before, SOMETHING was already saved too, so I’m not 100% that what I have as a profile now is what displaycal intended for me to have in the end – or if I got some intermediate state.To your questions:
Installed completely from scratch via
winget install FlorianHoech.DisplayCAL. That resulted in version 3.8.9.3.
All windows updates are done (only required, not functional upgrades).
Latest NVIDIA driver is running (it’s a computer I use for gaming, too).
“What process’s failed?” Nothing, as far as I can tel, except DisplayCAL freezing / not responding.
“Run chkdsk /R.”. The drive is a factory new Samsung 990 EVO Plus. Samsung Magician reports no problems. I did not runchkdskbut I highly doubt that’s the problem…Still: If there’s anything I can do to investigate / improve this situation, please let me know how.
I’m gratefulll for the existance of DisplayCAL and have repeatedly donated a few bucks in the past.
I’d be glad to help – within my means – to improve the situation where I reasonably can.Further Update:
The Calibration profile I obtained is uselessly wrong: Compared just now using a test-print I have from a highly respected printing service (Fotocommunity Prints) that I have used for years and I know how close the monitor image gets to the print version:
It is uselessly / obviosuly wrong :/.
I will try to re-do the calibration from a Macbook now. Maybe that helps.
Installed completely from scratch via
winget install FlorianHoech.DisplayCAL. That resulted in version 3.8.9.3.Just unzip the official version and test it, no installers. If not, try the “other” official py3 3.9.17.
“What process’s failed?” Nothing, as far as I can tel, except DisplayCAL freezing / not responding.
Do a full calibration + profilling from command line (ArgyllCMS) to discard other issues with you computer. DisplayCAL is a GUI for ArgyllCMS
https://www.argyllcms.com/doc/Scenarios.html#PM1c
Having spent the last 1.5 hours trying to get a calibration done, I’m not sure what else I can try.
That’s one of the reasons nobody uses spectrophotometers to calibrate and profile displays, a waste of time with 0 improvemenst over a custom profiled colorimeter (since you have the i1Pro), even an SpyderX or newer.
Also aim for a simpler profile & calibration like 24 patch greyscale (fast speed) + simple curvae & matrix profile with BPC enabled, just to check if it’s a time/memory issue.
Use latest ArgyllCMS, try 32 or 64 versions to discard some incompatibility issues or instability on your system.SpyderX Pro on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.calibration on macOS worked flawlessly.
Not sure if the problem was the
wingetinstaller. (Can’t imagine why, though).Update to my post above “The Calibration profile I obtained is uselessly wrong […]”
I might have to take that back (did not explicitly test after I discovered my error) but the obviously wrong-looking calibration was due to the viewing software (DxO Photolab).
