Home › Forums › Help and Support › Sypder 4 not being seen
- This topic has 18 replies, 3 voices, and was last updated 7 years, 4 months ago by Skaarj.
-
AuthorPosts
-
2016-08-16 at 0:17 #3791
Just updated to 3.1.5 from some old version and Argyll 1.8.3 and for some reason Displaycal doesn’t see my Sypder 4. Swapped the usb ports and still nothing.
The device manager shows it as Argyll LibUSB-win32 devices [Sypder4 (Argyll)].
Here’s the log
17:02:58,062 DisplayCAL.exe 3.1.5.0 2016-08-02T23:38:19.43Z 17:02:58,076 Windows 10 Pro x86_64 17:02:58,076 Python 2.7.10 (default, May 23 2015, 09:40:32) [MSC v.1500 32 bit (Intel)] 17:02:58,076 wxPython 3.0.1.1 msw (classic) 17:02:58,076 Encoding: cp437 17:02:58,078 File system encoding: mbcs 17:02:58,443 Starting up... 17:02:58,611 Audio module: pyglet 1.2.2 17:03:00,308 Enumerating display devices and communication ports... 17:03:00,308 D:\Argyll_V1.8.3\bin 17:03:02,553 Argyll CMS 1.8.3 17:03:02,555 ...ok. 17:03:02,786 Checking video card gamma table access for display 1... 17:03:04,296 Verify: 'test.cal' IS loaded (discrepancy 0.0%) 17:03:04,680 ...ok. 17:03:04,680 Checking video card gamma table access for display 2... 17:03:06,032 Verify: 'test.cal' IS loaded (discrepancy 0.0%) 17:03:06,427 ...ok. 17:03:06,427 Checking video card gamma table access for display 3... 17:03:07,657 Verify: 'test.cal' IS loaded (discrepancy 0.0%) 17:03:08,063 ...ok. 17:03:08,063 Initializing GUI... 17:03:08,737 17:03:11,424 ...ok. 17:03:11,431 Ready. 17:03:11,687 Setting up scripting host at 127.0.0.1:52583 17:03:11,881 Check for application update... 17:03:12,349 DisplayCAL is up-to-date. 17:03:12,647 Argyll CMS is up-to-date. 17:03:25,809 Enumerating display devices and communication ports... 17:03:27,541 ...ok. 17:12:42,909 Enumerating display devices and communication ports... 17:12:44,090 ...ok.
2016-08-16 at 13:20 #3793Hi,
Just updated to 3.1.5 from some old version and Argyll 1.8.3 and for some reason Displaycal doesn’t see my Sypder 4. Swapped the usb ports and still nothing.
Please run
D:\Argyll_V1.8.3\bin\dispcal.exe -v -D8 -?
and attach the output as a text file (don’t paste the text inline).
The device manager shows it as Argyll LibUSB-win32 devices [Sypder4 (Argyll)].
That looks normal.
2016-08-17 at 3:29 #38032016-08-17 at 12:06 #3806One additional log coming up.
Thanks. The vendor and product id doesn’t even appear in the debug output. Have you tried removing and re-installing the Argyll driver?
Weird that it doesn’t support piping aka >log.txt
It needs stderr redirection as well, i.e.
2>&1 >log.txt
2016-08-18 at 1:02 #3814Yup already tried that, do you know where I can grab an older version of Argyll? Perhaps the newer version is the problem?
2016-08-18 at 11:48 #3816do you know where I can grab an older version of Argyll?
Just changing the version number of the download link should work e.g. http://argyllcms.com/Argyll_V1.7.0_win64.zip
2016-08-19 at 0:16 #3821Hmmm nope no go either. I know the device still works, installed the Datacolor’s software and it works. Even nuked the drivers from the DriverStore folder.
What info are you looking for in the output log? I can keep an eye out to see if there’s any changes
2016-08-20 at 7:47 #3822This is really weird…. I’m using virtualBox and neither a clean Windows 8 nor Ubuntu are recongizing it (log shows the same Enumerating display devices and then ….ok)
2016-08-20 at 15:44 #3824What info are you looking for in the output log?
Only if Argyll sees the instrument. It doesn’t.
I’m using virtualBox and neither a clean Windows 8 nor Ubuntu are recongizing it
I wouldn’t expect Argyll running in a guest OS somehow being able to detect it if can’t detect it when running on the host. Have you another physical machine that you can try?
2016-08-21 at 5:14 #3829Sadly no, although I think I could use a cd boot ubuntu. It’ll probably be a few days though…
I wonder if one of the windows 10 updates borked something up with
- This reply was modified 7 years, 8 months ago by Skaarj.
2016-08-21 at 12:00 #3836What’s weird is that Argyll enumerates 16 libusb (virtual?) devices, but none of them seem to be related to the Spyder.
2016-08-22 at 7:14 #3858Are there any registery entries pretaining to Argyll? I did a quick search “Argyll” and found nothing really interesting. Perhaps that’s where those 16 entries are coming from.
2016-08-23 at 9:12 #3860No, the 16 entries are normal, but one of them should be the Spyder (in my case, it’s the first one).
2016-09-26 at 8:06 #4331Finally got time to try it out… unfortunately you can’t seem to install software from a CD boot, course now that I think about it duh…
So I have no idea what to do now :-\
2016-09-29 at 14:18 #4398I have the same problem. On my Surface Pro 4, the DisplayCAL utility detects the Spyder 4 without any issues, but on my new Desktop not, no matter what USB Port. I even tried using a USB 2 port, but that also didn’t help. In Device manager the Sypder 4 seems to be installed ok with the Argyll drivers.
-
AuthorPosts