2020-12-18 at 19:17 #27468
So when M1 macs came out, displaycal didnt really work on M1 Macs, displays wouldnt be recognized in display cal. a month later i cant find any thing about new updates. are there any plans for M1 macs in this regard? i feel like it should be important since in 2-3 years all macs will be M1 macs.2020-12-18 at 19:21 #27469
I don’t have an M1 mac. Does ArgyllCMS work on it? If not, then it needs updating.2020-12-18 at 19:46 #27470
The initial problem seems to be that DisplayCAL does not recognize the monitor.
Not sure if that is an issue with ArgyllCMS or not, but we can’t get further into the calibration process than launching DispayCAL2020-12-18 at 19:50 #27471
Test it then. Does
dispcal -?give you a list of displays and instruments or not?2020-12-18 at 19:56 #27472
I confess I am not an expert with DisplayCAL nor ArgyllCMS, or the inner workings of MacOS or code in general
dispcal -?a terminal command? I will check if you help me through it2020-12-18 at 20:10 #27473
Yes, run it in Terminal.
cd ~/Library/Application Support/Argyll_V2.1.2/bin dispcal -?2020-12-18 at 20:30 #27474
I’m seeing this:
** No displays found **2020-12-18 at 20:34 #27475
Ok, so ArgyllCMS would need an update.2020-12-18 at 20:43 #27476
Thanks for your help narrowing that down
Does anyone know if Graeme Gill is still actively maintaining ArgyllCMS or how responsive he is? Just wondering if it will be awhile, if I need to start looking at other solutions. Would happily donate to his efforts if he’s working on it2020-12-18 at 20:49 #27477
I just found this in the Argyll CMS support threads:
I am just trying to run Argyll on a new MacBook M1 2020.
Always get the error message “No displays found”.
that’s sad 🙁
I guess Apple have once again changed/deprecated API’s, wrecking
compatibility with existing applications. Or maybe Rosetta 2 doesn’t
work that well. I don’t have an M1 (nor am I likely to get access to one
any time soon), so it might be difficult to fix. Best bet would be at
least to gather a -D8 debug log and email it to me, to see if there is
anything obvious in there.
Graeme Gill.2020-12-18 at 21:34 #27478
Xrite and spyder themselves having trouble too, they say expected compatibility for M1 is Q1 2021…2020-12-27 at 18:10 #27567
so we cannot calibrate the m1 MacBook Pro at all then as of now? I have a yellow tint on mine and yes True Tone is off. My 2016 Touch Bar mb pro has a better display and I am extremely disappointed. May just end up returning it if Im downgrading display which is sad2020-12-31 at 17:00 #27656
I cannot get my Mac Mini (late 2012) to find any displays. I am on Mac OS 10.15.7 (19H114) . My Argyll is in a different path ~/Library/Application Support/DisplayCal/dl/Argyll_v2.1.2/Bin ) this is where DisplayCal downloaded and installed it. I run the dispcal -? the -? does not seem to be a valid argument.
bin % ./dispcal -D
get_a_display called with ix 0
Found 3 screens
CGDisplayIOServicePort returned error
dispcal: Error – Unable to open the default display
But DisplayCal does not show any of my 3 displays. One is displayport, one HMDI and one is USB to HDMI (displaylink chipset). I have calibrated with DisplayCal before, but I cannot today. I have uninstalled and re-installed.
NOTE: move this if it should be in another thread
2020-12-31 at 18:58 #27660
- This reply was modified 3 weeks, 3 days ago by Don Smith.
If you need to calibrate an external display, I found a workaround that works on M1 Macs: https://hub.displaycal.net/forums/topic/displaycal-and-big-sur-on-m1/#post-27658