#5720 (Bug) Report on uncalibrated display device – dispcal: Error – Got bad color temperature conversion
+1 0
Closed as Won't Fix
Component: ArgyllCMS
Created by Asimov
Last modified
Clicked on report for uncalibrated machine, ran patches 1 to 3, and an error message appeared – Error – Got bad color temperature conversion
I’ve tried running report several times and get the same error.
Windows 8.1 on a lenovo g510s
Spyder5 Pro
DisplayCAL 3.2.3
Log file contents
13:53:23,085 Report on uncalibrated display device
13:53:24,786 ——————————————————————————–
13:53:24,786 Command line:
13:53:24,786 dispcal.exe
13:53:24,788 -v2
13:53:24,788 -d1
13:53:24,788 -c1
13:53:24,789 -yn
13:53:24,789 “-P0.477508650519,0.5,1.97989949749”
13:53:24,789 -R
13:53:24,789
13:53:25,940 DisplayCAL: Starting interaction with subprocess
13:53:25,953 Setting up the instrument
13:53:27,385 Instrument Type: Datacolor Spyder5
13:53:27,387 Serial Number: 50152567
13:53:27,388 Hardware version: 0x0a0f
13:53:27,661 Place instrument on test window.
13:53:27,667 DisplayCAL: Waiting for send buffer
13:53:29,164 DisplayCAL: Skipping place instrument on screen message…
13:53:29,187 DisplayCAL: Sending buffer: ‘ ‘
13:53:29,194 Hit Esc or Q to give up, any other key to continue:
13:54:28,015 Patch 3 of 3
13:54:31,279 dispcal: Error – Got bad color temperature conversion
13:54:31,279
13:54:31,384 DisplayCAL: Reached EOF (OK)
13:54:31,384 …aborted.
14:13:16,373
14:15:05,408
This is not technically a bug – if the measured chromaticity for white is sufficiently far away from the daylight or blackbody locus, then it may become impossible to calculate a correlated color temperature. The Spyders are notorious for their relatively low accuracy (compared to more capable instruments), so that increases the chance of this particular issue. The work-around is to use a suitable measurement mode or colorimeter correction, or using a higher quality instrument.