Home › Forums › Help and Support › I CANT USE THE COLOR CHECKER DISPLAY?
- This topic has 4 replies, 2 voices, and was last updated 9 months, 3 weeks ago by
Luisfelipe.
-
AuthorPosts
-
2025-08-08 at 21:22 #144148
i dont know why but i used to calibrate my monitor with the Colorchecker Display and when i use it on my mini pc with intel graphics is not working anymore could you guys help me out ?
Attachments:
You must be logged in to view attached files.Calibrite Display SL on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.2025-08-09 at 21:31 #144163Which OS. Which Color Checker diplay is it? Check drivers. Read the readme notes argyii. Get argyii to work standalone with the spotread command. Perhaps a LED driver is in the new mini pc. Disable startups to test. Some LED drivers interfere with colorimeters drivers.
2025-08-11 at 21:02 #144234Hi Ben I read what u write and this is my answer to ur questions
OS:windows 11 pro 24H2.
Color checker display: is the basic one from CALIBRITE not the pro and not the 123 version the basic before the pro one.
the read me notes from argyle is something I don’t know how to find it also I don’t know how to make it work standalone with the spot read command.
how do I know if I have a LED driver installed in the mini pc. If you could guide through that I’ll be very happy or give me the links so I can look up by my self.
-
This reply was modified 9 months, 3 weeks ago by
Luisfelipe.
2025-08-12 at 14:09 #144237We know it can work with that. Just type start ups in search and the system settings will there. Disable what might be a bad startup. windows security is fine to keep on. You Antivirus should not interfere either so keep that. Realtek HD audio service is fine. https://hub.displaycal.net/forums/topic/argyllcms-issues-with-windows-11-24h2-26100/ I am just not familar with the problem. Unfortunately get other program problems. I wonder what is hogging your driver. Not the xrite software? Disable the xrite software.
2025-08-12 at 17:02 #144238Indeed, it was Logitech LampArray Service that caused the issue.
If someone encounter similar issue: you need to run services.msc, find “Logitech LampArray Service” and stop it (to check) and disable it (for more-or-less permanent fix). i found this answer in the link that you left here its crazy that Logitech Driver was causing all the problem…… Thanks Ben !!
-
This reply was modified 9 months, 3 weeks ago by
-
AuthorPosts