Copy link to clipboard
Copied
Due to plug-in problems I need to install the Intel version of InDesign 2021 (and InCopy 2021) on a MacBook Air M1. The installer states that this version of ID does not work on this Mac. We fixed this problem on ID and IC CC 2019 but need new instructions for 2021.
For those who want to know, we have a plug in that has not moved to the M1 and when tested at first appears to work but won't connect to our K4 server. InDesign is worthless to us without this plug in.
Copy link to clipboard
Copied
Copy link to clipboard
Copied
The developer says to wait for K4 v12r2 in 3 months. I've heard from someone else that having the Intel version of ID/IC 2021 on an M1 with the K4 plugins is working great at one of his offices and he will get back to me on Tuesday.
I can't start replacing our iMacs from 2010 until this is resolved. We are not buying any more Intel Macs. We are only buying laptops.
Copy link to clipboard
Copied
Copy link to clipboard
Copied
"I can't start replacing our iMacs from 2010 until this is resolved."
Absolutely! What do the developers of K4 say? When will they be ready with a plug-in for InDesign 16.3.2 that will run natively on M1?
EDIT: Ah. You already answered that:
"The developer says to wait for K4 v12r2 in 3 months."
Thanks,
Uwe Laubender
( ACP )
Copy link to clipboard
Copied
On Apple Silicon-based Macs, a menu called Open (Intel) appears in the menu next to the app's open button on the CC desktop app, and you can open it directly in the Rosetta environment.
Copy link to clipboard
Copied
True but irrelevant information. This is information about universal apps. So if InDesign were an universal app this would be a way to force InDesign to run as an Intel app under Rosetta 2.
InDesign is not a universal app. Adobe has 2 separate apps, one for Intel, one for the M1 chip. The Adobe Intel installer refuses to install on a Mac with the Intel chip. Adobe used to provide a solution to this problem but have since pulled this technical information.
Copy link to clipboard
Copied
Turned out to be super simple. It occurred to me that rather than delete the InstallationCheck filed in the installation package to open it and poke around. I just had to make the results of an else statement to be the same as the then statement and installation went smoothly.
Copy link to clipboard
Copied