OSX Yosemite – displayGUI hangs after first calibration step

[mafl2k SourceForge]

Hi,
I have a problem with diplayGUI.
It begins the calibration:
Patch 9/9
Patch 64/64
Doing iteration 1/3 with 16 sample points and repeat threshold of 1.200000 DE
Doing iteration 2/3 with 32 sample points and repeat threshold of 0.848528 DE
Doing iteration 3/3 with 64 sample points and repeat threshold of 0.600000 DE

After the last patch I get:

15:32:13,371 Brightness error = 0.182753 cd/m^2 (is 100.182753, should be 100.000000)
15:32:13,373 White point error = 0.301712 deltaE
15:32:13,375 Maximum neutral error (@ 0.338295) = 0.622058 deltaE
15:32:13,377 Average neutral error = 0.350910 deltaE
15:32:13,379 Failed to meet target 0.600000 delta E, got worst case 0.364016
15:32:13,381 Number of measurements taken = 352
15:32:13,383 Computing update to calibration curves…
15:32:13,649 The instrument can be removed from the screen.

But no message about a CAL file written.

At this point the calibration hangs.
Last message in the displayGUI window is “The instrument can be removed from the screen.”
Clock is ticking, remaining time –.–.–

If I start dispcal from the command line without displaygui it works and writes the CAL file.

Here is the complete log:
http://pastebin.com/VEts7uSa

Any ideas?

Tnx
Matt

• This topic was modified on 2015-09-17 14:45:37 by mafl2k.

[Florian Höch]

Hi,

If I start dispcal from the command line without displaygui it works and writes the CAL file.

Possibly coincidence. Did you use the exact same comamnd line? If you can, please try to reproduce the problem on the command line with -D8 debug output for dispcal.

[mafl2k SourceForge]

Yes, it was with the command line arguments extracted from the displaygui log.
I´ll try.

Which program (at which point) creates the working directory?
Library/Application Support/dispcalGUI exists, but is empty.

[Florian Höch]

Which program (at which point) creates the working directory?

dispcalGUI creates the temporary working directory (and copies files there) before a specific Argyll command line tool is launched as a subprocess (in a pseudo-terminal to facilitate reading its output unbuffered). It then waits for the process to exit, while reading continually from the pseudo-terminal to give status information or prompt for user interaction if required.
After the Argyll command line tool finishes successfully and exits, all created files are moved to the “storage” directory which is created if it doesn’t exist, and the temporary working directory is removed.

Library/Application Support/dispcalGUI exists, but is empty.

In your case the Argyll CMS ‘dispcal’ never finished, so you had to cancel, in which case any temporary files are discarded.
If on the other hand an Argyll command line tool exits with an error, dispcalGUI compares the files in the temporary directory to what they were before the subprocess launched. If there are any newly created or changed files, these would be moved to the “incomplete” directory.

[Author]

Posts