- This topic has 15 replies, 9 voices, and was last updated 3 months, 3 weeks ago by
.
-
Posts
-
I just got the Calibrite Display Pro HL. I’m on an M1 Mac.
Tried to calibrate with DisplayCAL and the latest ArgyllCMS (3.0.1). Received the infamous:
Error – new_disprd() failed with ‘Instrument Access Failed’
Rebooting, reinstalling…nothing worked.
Here’s the solution: Even though you may not be using Calibrite Profiler at all, you have install Calibrite Profiler AND open it up and initiate a measurement. Otherwise DisplayCAL can’t access the colorimeter.
https://calibrite.com/us/calibrite-profiler/
The software unlocks the Display Pro HL and then DisplayCAL can use it without issue.
Hope this keeps someone else sane! I was about to go crazy.
Calibrite Display Pro HL on Amazon Calibrite Display SL on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.Interesting. Well at least I can launch Calibrite Profiler and get around the lock file that way.
I was really, really hoping this fix would work for me. Glad to hear it worked for the OP—gives me some hope I can get this sorted.
I’m on a 2017 iMac, OS 13.6, using the Calibrite Display Plus HL. After installing the Calibrite Profiler and running a full calibration, I relaunched DisplayCal, but no luck. Deleted the app and its contents in the ~/Library/ directory and reinstalled. Still getting the error: Error – new_disprd() failed with ‘Instrument Access Failed’
I’m sorry to ask such a newbie question, but I’ve been searching all day and evening for a way to revert to a previous version of ArgyllCMS for Mac, but haven’t found anywhere I can download a prior release. Any ideas?
Any help is greatly appreciated!
edit: grammar
Calibrite Display Plus HL on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.Happy to report I was able to locate Argyll v2.3.1 in a system backup. Deleted v3.0.1 and replaced it. Was able to calibrate my primary and reference displays with no issues. Though it looks like Graeme has released v3.0.2, so I’ll be doing some testing with that.
Something I have also found after disabling all motherboard and led bloatware, is to disable this service if it is present, “Logitech LampArray Service”. I hope this helps. I was the only thing that worked for me.
Something I have also found after disabling all motherboard and led bloatware, is to disable this service if it is present, “Logitech LampArray Service”. I hope this helps. I was the only thing that worked for me.
I created an account just to tell you THANK YOU. I tried 2.3.0 and 2.3.1 and still got the error. Stopped the “Logitech LampArray Service” and it worked immediately. Appreciate you coming back to report this – internet superhero!
I am very glad that my own findings could help you too. All the very best with your calibrations. Take care.
oh my lord Simon this worked! It was the logitech service.. How the hell did you figure that out? haha. Thank you so much.
what’s weird is that your solution worked, BUT Displaycal seems convinced that my Calibrite Display Plus HL is the equivalent to an i1 DisplayPro. But they aren’t one-to-one, because the Display Plus HL, at least from what I’ve read online, has a more sensitive and accurate sensor, and it’s supposed to read even higher brightness values. Were you able to get DisplayCal to actually detect the model as a Plus or Pro HL, or was it stuck on the i1 DisplayPro setting for you too?
what’s weird is that your solution worked, BUT Displaycal seems convinced that my Calibrite Display Plus HL is the equivalent to an i1 DisplayPro.
Because it is. Even equivalent to a cheap colormunki display in terms of API and device commands
But they aren’t one-to-one, because the Display Plus HL, at least from what I’ve read online, has a more sensitive and accurate sensor, and it’s supposed to read even higher brightness values. Were you able to get DisplayCal to actually detect the model as a Plus or Pro HL, or was it stuck on the i1 DisplayPro setting for you too?
It’s the same device, same protocol, same “blackbox” even if the HW capabilities are slightly different.
