Home › Forums › Help and Support › Spyder 3
- This topic has 10 replies, 2 voices, and was last updated 6 years, 7 months ago by SunMaster.
-
AuthorPosts
-
2017-08-25 at 17:24 #8575
Hi.
I’ve an old Spyder 3. The installation of the device and software went as it should, but when I come to the point of installing “Import colorimeter corrections from other display profiling software” I can’t get it to work. I get the error message “No colorimetger corrections could be imported” when I select the install .exe downloaded from the manufacturer. As I don’t even know which file it’s supposed to find, I don’t know what to look for elsewhere. Any hints?
2017-08-30 at 0:37 #8624Hi,
when I come to the point of installing “Import colorimeter corrections from other display profiling software” I can’t get it to work. I get the error message “No colorimetger corrections could be imported” when I select the install .exe downloaded from the manufacturer.
You’re not supposed to select the manufacturer exe as it doesn’t provide any corrections. Instead, make sure “iColor Display” is ticked and click “Auto”.
2017-08-30 at 18:39 #8646When I choose “Auto” (making sure iColor Display is ticked) and choose Auto it ends very quickly with “No colorimeter corrections could be imported”. The same result for current-user-only or system-wide. The same result whether it’s run as current user or administrator. It’s as it tries to download something then very quickly aborts (like <0.1s) and displays the error message. I have no connectivity nor firewall issues I’m aware of.
2017-08-31 at 21:02 #8663Which version of DisplayCAL are you using and which operating system?
2017-09-01 at 5:22 #8685I’m using windows 10 and Displaycal 3.3.3
2017-09-01 at 8:29 #8687Attach logs please.
2017-09-01 at 13:12 #869013:08:03,282 DisplayCAL.exe 3.3.3.0 2017-08-08T18:45:19.543Z
13:08:03,286 Windows 10 Pro x86_64
13:08:03,286 Python 2.7.12 (v2.7.12:d33e0cf91556, Jun 27 2016, 15:19:22) [MSC v.1500 32 bit
13:08:03,286 (Intel)]
13:08:03,286 Faulthandler 2.6
13:08:03,463 Imported existing <module ‘comtypes.gen’ from ‘C:\Program Files
13:08:03,463 (x86)\DisplayCAL\lib\library.zip\comtypes\gen\__init__.pyc’>
13:08:03,467 Using writeable comtypes cache directory:
13:08:03,467 ‘c:\users\gunnar~1.gmb\appdata\local\temp\comtypes_cache\DisplayCAL-27’
13:08:03,469 wxPython 3.0.2.0 msw (classic)
13:08:03,470 Encoding: cp850
13:08:03,470 File system encoding: mbcs
13:08:03,598 Starting up…
13:08:03,723 Audio module: pyglet 1.2.2
13:08:05,326 Enumerating display devices and communication ports…
13:08:05,331 C:\Users\gunnar.GMBJELL\Downloads\Argyll_V1.9.2\bin
13:08:07,203 ArgyllCMS 1.9.2
13:08:07,204 …ok.
13:08:07,342 Checking video card gamma table access for display 1…
13:08:07,479 Verify: ‘test.cal’ IS loaded (discrepancy 0.0%)
13:08:07,519 …ok.
13:08:07,519 Checking video card gamma table access for display 2…
13:08:07,653 Verify: ‘test.cal’ IS loaded (discrepancy 0.0%)
13:08:07,694 …ok.
13:08:07,694 Initializing GUI…
13:08:07,934
13:08:09,032 …ok.
13:08:09,035 Ready.
13:08:09,306 Setting up scripting host at 127.0.0.1:9829
13:08:09,496 Check for application update…
13:08:09,592 DisplayCAL is up-to-date.
13:08:09,799 ArgyllCMS is up-to-date.2017-09-01 at 15:24 #8695I need a log after trying the automatic import.
2017-09-01 at 17:02 #8699This is actually the log after trying to import. I’ve just done it again to make sure. The log shows no sign of trying to import anything. Is is possible to set loglevel somewhere? I looked around but didn’t find anything looking like it.
2017-09-01 at 17:54 #8700Ok, this was a server configuration issue. As there was no error message from the server, it failed without further info. Please try again now.
2017-09-01 at 18:24 #8703Now it’s fixed. Excellent – thanks 🙂
-
AuthorPosts