- This topic has 12 replies, 2 voices, and was last updated 8 years, 2 months ago by
.
-
Posts
-
Hi Folks,
After calibrating my main monitor (out of 3) with success, I tried to calibrate my second and got this error:
“object has no attribute device key” when I tried to install the profile after the long process.
I got this error repeatedly, but now I setup my whole system with a clean Windows 10 64bit install again and it appeared again.
What can I do?
Pequi
Hi,
go to “Tools” > “Show log” after the error appeared and click the “Create compressed archive…” button. Attach the created log archive. Thanks.
Hi,
Thanks for your fast reply, but I restarted DispCal multiple times, so it seems the errorlog is overwritten meantime.
I have to recalibrate the whole thing, *sigh*
Pequi,
P.S.: Ist deutsch im Forum auch erlaubt?
Edith: I installed a monitor driver for these really old monitor, which I use beside my main monitor. Starting now to recalibrate. Hope that works….
Thanks for your fast reply, but I restarted DispCal multiple times, so it seems the errorlog is overwritten meantime.
No, when creating an archive it’ll include the last seven logs.
P.S.: Ist deutsch im Forum auch erlaubt?
Zurzeit würde ich das Forum lieber auf englisch belassen. Eventuell kommt ein deutsches Unter-Forum ab einem gewissen Zeitpunkt hinzu, steht aber noch nicht fest.
After installing the monitor driver, the installation of the profile was successful.
For the third really old monitor I don’t have any driver, so only “Display 2” is recognized from DispCal. I’ll give it a try to calibrate it…
After installing the monitor driver, the installation of the profile was successful.
I’d still like to learn about the nature of the error you got initially, so if you could attach the logs archive it would be very helpful, thanks.
It isn’t as comprehensive as you might think, it was overwritten:
04:29:49,743 DisplayCAL.pyw 3.1.2.0 2016-03-03T23:20:20.448Z 04:29:49,747 Windows 10 Pro x86_64 04:29:49,747 Python 2.7.6 (default, Nov 10 2013, 19:24:18) [MSC v.1500 32 bit (Intel)] 04:29:49,747 wxPython 3.0.1.0.b20140104 msw (classic) 04:29:49,747 Encoding: cp850 04:29:49,749 File system encoding: mbcs 04:29:51,170 Starte... 04:29:51,535 Audio-Modul: pyglet 1.2.2 04:29:53,934 C:\Users\mp\Downloads\Argyll_V1.8.3\bin 04:29:55,325 Argyll CMS 1.8.3 04:29:55,651 Verify: 'test.cal' IS loaded (discrepancy 0.0%) 04:29:55,848 Verify: 'test.cal' IS loaded (discrepancy 0.0%) 04:29:56,071 Verify: 'test.cal' IS loaded (discrepancy 0.0%) 04:29:56,115 Initialisiere GUI... 04:29:56,523 04:29:59,161 ...ok. 04:29:59,171 Bereit. 04:29:59,440 Starte Skript-Host unter 127.0.0.1:49807 04:29:59,598 Auf Programmaktualisierung überprüfen... 04:29:59,671 DisplayCAL ist auf dem neuesten Stand. 04:29:59,720 Argyll CMS ist auf dem neuesten Stand.
As I said, you have to use the “Create archive” button on the log window. The archive will contain all accumulated logs (up to seven days).
It seems the display in question did not have an entry in the registry, which I wasn’t even aware that this could be an actual condition in Windows. You said it’s an older display, what type of display is this and how is it connected? What was the entry in device manager before you installed the driver for it as you said?
There’s nothing I can do about the underlying problem other than improving the error message or ignoring the error altogether it seems.The driver can’t be installed for the just plain PnP-Monitor. After I installed the driver for the Acer- and LG-Monitor I could install the profiles. While I don’t have any driver for the PnP-Mon. I can’t install a profile. All Monitors are LCD: the LG is my main for photoediting (1920×1200), the Acer is 1280×1024 and the PnP is a HP with 1366×768.
