I spent a good 20 minutes trying to figure out the right google search words to no luck. Hence the search-friendly subject, in case this yields good answers
Airwindows on M1 apple silicon?
-
- KVRer
- 13 posts since 18 Dec, 2018
I see Chris is working on compiling native versions of the Airwindows plugs, so I'm not really nagging about that, but I'm trying to figure out how and if I should install the Airwindows stuff on my new M1 mac, anyone got experience?
I spent a good 20 minutes trying to figure out the right google search words to no luck. Hence the search-friendly subject, in case this yields good answers
I spent a good 20 minutes trying to figure out the right google search words to no luck. Hence the search-friendly subject, in case this yields good answers
- KVRAF
- 2035 posts since 30 Mar, 2008 from MN, USA
Copy the VSTs to /Library/Audio/Plug-ins/VST
Copy the AUs to /Library/Audio/Plug-ins/Components
If you are on Big Sur, you will need to dequarantine them from Terminal first:
Copy the AUs to /Library/Audio/Plug-ins/Components
If you are on Big Sur, you will need to dequarantine them from Terminal first:
Code: Select all
xattr -d com.apple.quarantine <path to plugin file>CLAP Software Database: https://clapdb.tech. KVR Discussion Topic.
-
- KVRer
- Topic Starter
- 13 posts since 18 Dec, 2018
do you run the quarantine command for each file? any way to automate that? appart from using the up button and the tab buttonteilo wrote: Sat Apr 03, 2021 1:27 pm Copy the VSTs to /Library/Audio/Plug-ins/VST
Copy the AUs to /Library/Audio/Plug-ins/Components
If you are on Big Sur, you will need to dequarantine them from Terminal first:
Code: Select all
xattr -d com.apple.quarantine <path to plugin file>
-
- KVRer
- Topic Starter
- 13 posts since 18 Dec, 2018
Nevermind, did the up and tab thing, only took a couple of minutes. Thanks!
-
- KVRian
- 1482 posts since 7 Apr, 2007 from Bellows Falls, VT
For future reference: Here’s my collection of Catalina gatekeeper instructions 
I’ve got one report that says you can do a re-scan within Logic’s plugin manager, and then as you run ‘reset and re-scan selection’ you can go to system prefs/security and it’ll show that Gatekeeper stopped the plugin from opening but there was an option for ‘open anyway’. If you’re able to do it that way the plugin will pass validation in Logic.
If that doesn’t work, the Terminal command to run will be like this (if you have the NewUpdates folder open on your desktop):
sudo xattr -d -r com.apple.quarantine ~/Desktop/NewUpdates/*
sudo (you’ll supply your password) lets you do administrator stuff
xattr -d removes the attribute ‘com.apple.quarantine’ from things,
the -r means recursive so it will go into subfolders and anything in NewUpdates, so don’t point this at your whole hard drive
and THAT is what will automate it.
I'll keep ya posted on the M1 thing. Bear in mind that I have more than 200 plugins to do. I can hardly be expected to pop out with the entire collection all at once
I’ve got one report that says you can do a re-scan within Logic’s plugin manager, and then as you run ‘reset and re-scan selection’ you can go to system prefs/security and it’ll show that Gatekeeper stopped the plugin from opening but there was an option for ‘open anyway’. If you’re able to do it that way the plugin will pass validation in Logic.
If that doesn’t work, the Terminal command to run will be like this (if you have the NewUpdates folder open on your desktop):
sudo xattr -d -r com.apple.quarantine ~/Desktop/NewUpdates/*
sudo (you’ll supply your password) lets you do administrator stuff
xattr -d removes the attribute ‘com.apple.quarantine’ from things,
the -r means recursive so it will go into subfolders and anything in NewUpdates, so don’t point this at your whole hard drive
I'll keep ya posted on the M1 thing. Bear in mind that I have more than 200 plugins to do. I can hardly be expected to pop out with the entire collection all at once
- KVRAF
- 2035 posts since 30 Mar, 2008 from MN, USA
Yes. Change to the directory in question and use a wildcard:sveinbjorn wrote: Sun Apr 04, 2021 7:03 amdo you run the quarantine command for each file? any way to automate that? appart from using the up button and the tab buttonteilo wrote: Sat Apr 03, 2021 1:27 pm Copy the VSTs to /Library/Audio/Plug-ins/VST
Copy the AUs to /Library/Audio/Plug-ins/Components
If you are on Big Sur, you will need to dequarantine them from Terminal first:
Code: Select all
xattr -d com.apple.quarantine <path to plugin file>![]()
Code: Select all
xattr -d com.apple.quarantine *Code: Select all
xattr -r -d com.apple.quarantine <path to directory>
Last edited by teilo on Mon Apr 05, 2021 3:22 pm, edited 2 times in total.
CLAP Software Database: https://clapdb.tech. KVR Discussion Topic.
- KVRAF
- 2035 posts since 30 Mar, 2008 from MN, USA
That doesn't work on Big Sur. There's no "Anywhere" option.Tronam wrote: Mon Apr 05, 2021 3:31 am I don't even bother with GateKeeper. I rock it old school.
.
Screen Shot 2021-04-04 at 8.27.35 PM.png
CLAP Software Database: https://clapdb.tech. KVR Discussion Topic.
- KVRAF
- 2036 posts since 15 Mar, 2002 from Seattle, WA - USA
Restoring the option requires a terminal command:
Code: Select all
sudo spctl --master-disable-
- KVRAF
- 9528 posts since 6 Oct, 2004
@Tronam, just curious, did you have BSD/linux in your arsenal before Apple
made the switch, or did you teach yourself as the new OS unfolded?
Commands are
Thanks for sharing the knowlege!
made the switch, or did you teach yourself as the new OS unfolded?
Commands are
Thanks for sharing the knowlege!
- KVRAF
- 2035 posts since 30 Mar, 2008 from MN, USA
Huh. I was aware of this command, but for some reason I thought Apple had locked it down in Big Sur. Thanks for that.Tronam wrote: Mon Apr 05, 2021 5:35 pmRestoring the option requires a terminal command:Code: Select all
sudo spctl --master-disable
CLAP Software Database: https://clapdb.tech. KVR Discussion Topic.
-
- KVRian
- 1482 posts since 7 Apr, 2007 from Bellows Falls, VT
- KVRAF
- 2036 posts since 15 Mar, 2002 from Seattle, WA - USA
Even though fewer of these options are visible by default, I’m glad they continue to support tinkerers who may want to disable things like GateKeeper, allow traditional kernel extensions or even disable SIP (system integrity protection) altogether. I’m personally fine with removing all the safety nets, but crank them up to maximum on my mother’s Mac.
-
- KVRian
- 1482 posts since 7 Apr, 2007 from Bellows Falls, VT
I'll repeat that more explicitly, as it is a direct answer to the whole purpose of the thread:
MackityARM.zip(98k)
That's the most recent plugin, using my best shot at a process to support direct native M1 Audio Unit compiling.
It'll unzip into an Audio Unit file, which IS code signed and won't require use of Terminal or anything like that. I had to pay Apple to get the upgrade to my developer profile that allowed me to get that, and I'll have to continue to pay Apple every year to maintain it. It's a native M1 build, and if it works that means the answer to the thread question is "YES, NATIVELY, RIGHT NOW".
And the rest is just a LOT of work recompiling everything… work I've already begun. I'll skip new plugins coming out, until I have the entire library, 249 individual plugins, available. I probably won't skip sleep and eating: depends on how quickly it goes
I didn't have the new XCode compiling stuff for me before, it was impenetrable: and I didn't have the for-pay Apple distribution certificate before yesterday. I'm going as fast as I can, and now what I need is confirmation from one person who isn't me, that it worked. Preferably, several people. You'll have to have an M1 Mac because there's no Intel code in there (I'm thinking hard about leaving it in the PPC/32/64 build, which I will also continue to do going forward)
I also have a universal binary in MackityUniversal.zip(198k)
Let me know if this worked. If it did, things are going to get real busy around here, real quickly. I'm going to grab some sleep as it might be the last sleep I get for a while…
MackityARM.zip(98k)
That's the most recent plugin, using my best shot at a process to support direct native M1 Audio Unit compiling.
It'll unzip into an Audio Unit file, which IS code signed and won't require use of Terminal or anything like that. I had to pay Apple to get the upgrade to my developer profile that allowed me to get that, and I'll have to continue to pay Apple every year to maintain it. It's a native M1 build, and if it works that means the answer to the thread question is "YES, NATIVELY, RIGHT NOW".
And the rest is just a LOT of work recompiling everything… work I've already begun. I'll skip new plugins coming out, until I have the entire library, 249 individual plugins, available. I probably won't skip sleep and eating: depends on how quickly it goes
I didn't have the new XCode compiling stuff for me before, it was impenetrable: and I didn't have the for-pay Apple distribution certificate before yesterday. I'm going as fast as I can, and now what I need is confirmation from one person who isn't me, that it worked. Preferably, several people. You'll have to have an M1 Mac because there's no Intel code in there (I'm thinking hard about leaving it in the PPC/32/64 build, which I will also continue to do going forward)
I also have a universal binary in MackityUniversal.zip(198k)
Let me know if this worked. If it did, things are going to get real busy around here, real quickly. I'm going to grab some sleep as it might be the last sleep I get for a while…
