Excited to receive my incoming mba but just saw that most calibration apps even displaycal are incompatible for now
There is currently a known profiling issue on newer M1 Macintosh computers where the software can't detect a monitor on the system.
Our developers are working on an update but have only had the hardware to test the software for the last week.
Please keep looking at the downloads page or just run the application and it will inform you when an update is available
Kind Regards
On behalf of X-Rite Photo Europe
Just got my base model MBA today and tried my luck:Interested in DisplayCAL, anyone tried? Thanks.
Just to say that (almost) a year later this is still the fix...thank you.Figured out a way to have Displaycal Recognize the external monitors:
A common DisplayCAL issue is that on M1 Macs, the software cannot detect any external monitors connected.
Found out that the new version ofArgyllCMS v2.2.0 actually works with M1 Mac and allows detection of external monitors today thanks to the user [5425642 on the displaycal forums](https://hub.displaycal.net/forums/topic/displaycal-does-not-recognize-my-monitor/page/3/#post-30239). Here are the approximate instructions to get it working:
1. Download Displaycal from https://displaycal.net/ and install
2. Open up the display cal app, and plug in your calibration tool, in my case Spyder4
3. It will prompt me to download the latest Argyll (which is a lie. It's downloading v2.1.2), click ok and let it
4. Go to https://www.argyllcms.com/downloadmac.html and click on "Intel OS X 10.6 64 bit or later" , it will download a tgz zip file, unzip it and make note of its location, we will need to move it later.
5. Go back to the DisplayCal app. Click on "File" up top, click "Locate ArgyllCMS Executables", it should open a bin folder with a bunch of files in it. Navigate to the Library>Download folder where your unzipped ArgyllCMS folder is located (from step 4), and select the "bin" folder
6. Displaycal will automatically try to run a bunch of files in that bin folder, and the MacOS will try to stop you because the files came from an unidentified developer. So everytime the "warning: Can't open up file because the developer is unknown" popup shows up, you need to go to that bin folder and do a CTRL+ Right click to force run the file. Then cancel the popup windows. Repeat this a few times until all the files DisplayCal need is not showing the "unknown dev" popup anymore.
7. Reboot Displaycal and you should see your monitor being recognized, yay. Pic for proof:
This workaround is applicable until Displaycal auto downloads Argyll 2.2.0, which should be soon I hope?
PS: If you want to put the Argyll folder in its intended place, it is located at User->yourusername->Library->Application Support -> Displaycal-> dl
Figured out a way to have Displaycal Recognize the external monitors:
A common DisplayCAL issue is that on M1 Macs, the software cannot detect any external monitors connected.
Found out that the new version ofArgyllCMS v2.2.0 actually works with M1 Mac and allows detection of external monitors today thanks to the user [5425642 on the displaycal forums](https://hub.displaycal.net/forums/topic/displaycal-does-not-recognize-my-monitor/page/3/#post-30239). Here are the approximate instructions to get it working:
1. Download Displaycal from https://displaycal.net/ and install
2. Open up the display cal app, and plug in your calibration tool, in my case Spyder4
3. It will prompt me to download the latest Argyll (which is a lie. It's downloading v2.1.2), click ok and let it
4. Go to https://www.argyllcms.com/downloadmac.html and click on "Intel OS X 10.6 64 bit or later" , it will download a tgz zip file, unzip it and make note of its location, we will need to move it later.
5. Go back to the DisplayCal app. Click on "File" up top, click "Locate ArgyllCMS Executables", it should open a bin folder with a bunch of files in it. Navigate to the Library>Download folder where your unzipped ArgyllCMS folder is located (from step 4), and select the "bin" folder
6. Displaycal will automatically try to run a bunch of files in that bin folder, and the MacOS will try to stop you because the files came from an unidentified developer. So everytime the "warning: Can't open up file because the developer is unknown" popup shows up, you need to go to that bin folder and do a CTRL+ Right click to force run the file. Then cancel the popup windows. Repeat this a few times until all the files DisplayCal need is not showing the "unknown dev" popup anymore.
7. Reboot Displaycal and you should see your monitor being recognized, yay. Pic for proof:
This workaround is applicable until Displaycal auto downloads Argyll 2.2.0, which should be soon I hope?
PS: If you want to put the Argyll folder in its intended place, it is located at User->yourusername->Library->Application Support -> Displaycal-> dl
What you're missing: it sounds like you're right clicking the folder. You want to right-click an application icon, not the folder it's inside.I'm getting stuck at the "go to that bin folder and do a CTRL+ Right click to force run the file. Then cancel the popup windows. Repeat this a few times until all the files DisplayCal need is not showing the "unknown dev" popup anymore."
When I go back to the bin folder and CTRL+Rigiht click the bin folder, I don't see any option to force run anything. I'm missing something clearly.
What you're missing: it sounds like you're right clicking the folder. You want to right-click an application icon, not the folder it's inside.
It may help to know what you're doing here. macOS has a malware protection system called Gatekeeper which requires apps to be signed by the developer and notarized by Apple, otherwise it blocks them from running. Lots of old apps released before Apple created Gatekeeper aren't signed or notarized, even though they're perfectly OK to run, so Apple includes a simple (but not well documented) user interface backdoor to run them anyways. If you open the app by right clicking it and selecting Open, you'll get the normal Gatekeeper rejection dialog box, but there will be an extra button there letting you choose to run the app anyways. Clicking it not only runs it this time, it also records that you authorized using the app, so you won't have to go through these extra steps in the future.
There's no need to use the Control key unless you're doing this with a mouse or trackpad that has no way to right click, in which case you can do Control+left click to generate a right click.