2016-07-26 at 23:46 #3662
I just noticed that I replied to a closed (Not a Bug) issue (link) instead of a topic, so here I am re-posting it as a topic:
I have just updated from Win 8.1 Pro to Win 10 Pro (64 bit) and I have the same exact issue. Before I used the Datacolor app (Spyder 5 Pro) for calibrating, but now on Win10 it returns a bad profile (gray seems more like green). So I decided to try out DisplayCAL since I’ve always heard good things of it.
I am using Argyll 1.8.3 (Argyll_V1.8.3_win64_exe.zip) with displayCAL 3.1.4 but no matter how many times I try to re-install the driver or everything else no monitors (I have 2) nor the Spyder instrument is detected. It took me some time to install properly the Argyll driver but I managed it in the end, still nothing appears. I also went ahead and removed the Datacolor driver and application in case they were somehow interfering.
My DisplayCAL window is the same exact one seen in the linked issue above. Logs have nothing in them:
2016-07-26 23:25:10,713 ================================================================================ 2016-07-26 23:25:10,713 DisplayCAL.exe 188.8.131.52 2016-07-11T00:19:04.559Z 2016-07-26 23:25:10,746 Windows 10 Pro x86_64 2016-07-26 23:25:10,746 Python 2.7.10 (default, May 23 2015, 09:40:32) [MSC v.1500 32 bit (Intel)] 2016-07-26 23:25:10,746 wxPython 184.108.40.206 msw (classic) 2016-07-26 23:25:10,746 Encoding: cp850 2016-07-26 23:25:10,746 File system encoding: mbcs 2016-07-26 23:25:11,209 Starting up... 2016-07-26 23:25:11,490 Audio module: pyglet 1.2.2 2016-07-26 23:25:13,387 Enumerating display devices and communication ports... 2016-07-26 23:25:13,388 C:\Users\XXX\Downloads\Argyll_V1.8.3\bin 2016-07-26 23:25:16,079 ...ok. 2016-07-26 23:25:16,079 Initializing GUI... 2016-07-26 23:25:16,719 2016-07-26 23:25:19,505 ...ok. 2016-07-26 23:25:19,505 Ready. 2016-07-26 23:25:19,775 Setting up scripting host at 127.0.0.1:15411 2016-07-26 23:25:59,648 Enumerating display devices and communication ports... 2016-07-26 23:26:02,292 ...ok. 2016-07-26 23:31:17,221 Executing BaseApp.OnExit() 2016-07-26 23:31:17,221 Running application exit handlers 2016-07-26 23:31:17,223 Waiting for thread ScriptingHost.ConnectionHandler to exit 2016-07-26 23:31:17,569 Exiting DisplayCAL2016-07-27 at 0:09 #3663
I was reading around and noticed the USB connectivity issues topic. Let me add that I am using USB 2.0, rather my motherboard is so old (5+ years) that I have no 3.0 ports at all 😀2016-07-28 at 14:53 #3673
No ideas anyone? I removed the other calibration profiles and my monitors are looking really bad right now, I need to fix them 🙁
I guess I should at least go back and use the bad calibration profile for now at least, it’s still better than nothing.2016-07-29 at 12:01 #3682
Please open a command prompt and run the following:
Then attach the output. Thanks.2016-07-29 at 15:44 #3692
This is what I get:
C:\WINDOWS\system32>C:\Users\XXX\Downloads\Argyll_V1.8.3\bin\dispcal -? Calibrate a Display, Version 1.8.3 Author: Graeme W. Gill, licensed under the AGPL Version 3 Diagnostic: Usage requested usage: dispcal [options] outfile -v [n] Verbose mode -d n Choose the display from the following list (default 1) 1 = 'DISPLAY1, at 0, 0, width 1920, height 1080 (Primary Display)' 2 = 'DISPLAY2, at -1920, 0, width 1920, height 1080' -dweb[:port] Display via a web server at port (default 8080) -dcc[:n] Display via n'th ChromeCast (default 1, ? for list) -dmadvr Display via MadVR Video Renderer -c listno Set communication port from the following list (default 1) 1 = 'libusb0-0001 (Datacolor Spyder5)' 2 = 'COM1' -r Report on the calibrated display then exit -R Report on the uncalibrated display then exit -m Skip adjustment of the monitor controls -o [profile.icm] Create fast matrix/shaper profile [different filename to outfile.icm] -O "description" Fast ICC Profile Description string (Default "outfile") -u Update previous calibration and (if -o used) ICC profile VideoLUTs -q [vlmh] Quality - Very Low, Low, Medium (def), High -p Use telephoto mode (ie. for a projector) (if available) -y n|l Spyder5: Generic Non-Refresh Display [Default,CB1] r|c Spyder5: Generic Refresh Display [CB2] l|c Other: l = LCD, c = CRT -t [temp] White Daylight locus target, optional target temperaturee in deg. K (deflt.) -T [temp] White Black Body locus target, optional target temperaturee in deg. K -w x,y Set the target white point as chromaticity coordinates -b bright Set the target white brightness in cd/m^2 -g gamma Set the target response curve advertised gamma (Def. 2.4) Use "-gl" for L*a*b* curve Use "-gs" for sRGB curve Use "-g709" for REC 709 curve (should use -a as well!) Use "-g240" for SMPTE 240M curve (should use -a as well!) Use "-G2.4 -f0" for BT.1886 -G gamma Set the target response curve actual technical gamma -f [degree] Amount of black level accounted for with output offset (default all output offset) -a ambient Use viewing condition adjustment for ambient in Lux -k factor Amount to correct black hue, 0 = none, 1 = full, Default = Automatic -A rate Rate of blending from neutral to black point. Default 4.0 -b Use forced black point hack -B blkbright Set the target black brightness in cd/m^2 -e [n] Run n verify passes on final curves -z Run only verify pass on installed calibration curves -P ho,vo,ss[,vs] Position test window and scale it ho,vi: 0.0 = left/top, 0.5 = center, 1.0 = right/bottom etc. ss: 0.5 = half, 1.0 = normal, 2.0 = double etc. -F Fill whole screen with black background -E Encode the test values for video range 16..235/255 -J Run instrument calibration first (used rarely) -N Disable initial calibration of instrument if possible -H Use high resolution spectrum mode (if available) -X file.ccmx Apply Colorimeter Correction Matrix -X file.ccss Use Colorimeter Calibration Spectral Samples for calibration -Q observ Choose CIE Observer for spectrometer or CCSS colorimeter data: 1931_2 (def), 1964_10, S&B 1955_2, shaw, J&V 1978_2, 1964_10c -I b|w Drift compensation, Black: -Ib, White: -Iw, Both: -Ibw -Y R:rate Override measured refresh rate with rate Hz -Y A Use non-adaptive integration time mode (if available). -Y p Don't wait for the instrument to be placed on the display -C "command" Invoke shell "command" each time a color is set -M "command" Invoke shell "command" each time a color is measured -W n|h|x Override serial port flow control: n = none, h = HW, x = Xon/Xoff -D [level] Print debug diagnostics to stderr inoutfile Base name for created or updated .cal and .icm output files C:\WINDOWS\system32>
Looking at that text it seems to detect both monitors and the spyder properly, but then why is displayCAL not listing them? 🙁2016-07-29 at 15:56 #3693
Okay, after you had me run that command a popup from my firewall (Comodo Firewall) came up. That made me think for a while and then I figured out that when DisplayCAL was searching for monitors and instruments my firewall was silently sandboxing it. After adding The Argyll folder to the ignored folders in my firewall rules DisplayCAL now properly finds that I have 2 monitors. But it still won’t list the Spyder 5 as usable instrument.
Is there anything else I should add to my firewall ignore list perhaps? Or am I missing another step to make the Spyder 5 show up in DisplayCAL? I have already run also the option “Import colorimeter corrections from other display profiling software…”, I choose “Spyder 4/5 – Install for current user only”.
EDIT: restarting windows seems to have fixed it now, the Spyder 5 is properly showing up in the instruments dropdown. Unfortunately I have to go out for a while now, as soon as I’m back I’ll try a calibration and let you know how it goes 🙂
2016-07-30 at 12:37 #3701
- This reply was modified 4 years, 1 month ago by Terabyte.
All solved, I was able to calibrate properly both monitor and the green-ish effect on my main monitor is completely gone after using DisplayCAL. This is indeed an awesome program, thanks again!2020-09-11 at 10:23 #26057
I am currently running into Problem where Display cal is not reading my TV, receiver or devices just like the user in the thread.
I am running OSX 10.9.5 in a late 13 retina display Macbook pro
Display Cal version is 220.127.116.11
Just wondering if you might be able to tell why Display Devices are not showing up. The only thing that shows up is my Macbook Pro Display as MacbookPro11,[email protected],0,1280×800 (primary)
THanks if you can help please just shoot!2020-09-11 at 23:11 #26069
Did you try manual detection with menu Tools / Detect display & instruments?2020-09-12 at 2:09 #26071
yeah I checked that out, i also tried the little refresh option which does the same thing.
I checked out this thread and Florian gave options for PC USers to change through Command Prompt
THe Mac option would have to be through the terminal I guess.
I really need help with this