Help for Editor installation and use
Generally applies to all my editors
For MAC User
Attention Ableton Live 11.1 and higher users on MAC M1 -> in order for the editor to be displayed in the VST folder, Live must be started with Rosetta 2
Plug-ins on Mac M1 in Live 11.1
- Live Versions: 11.1 and above
- Operating System: Mac
Note: It's important to allow Live to index the new devices by waiting a few minutes after launching Live 11.1 for the first time. If the device don't show up after a restart, please try to reset the database as explained here.
Plug-in scan (all builds)
In Live 11.1, VST2 plug-in scanning will operate in the background; no plug-in scanning will appear in Live's startup window. While plug-in scanning is in progress, plug-ins may temporarily appear missing.
Missing plug-ins (Universal/Silicon-native build)
When used on an Apple Silicon computer, the Universal build of Live 11.1 only recognizes VST2 and VST3 plug-ins natively compiled for Apple Silicon. However, many Intel-based Audio Unit plug-ins will display and load, thanks to the macOS feature AUHostingCompatibilityService.
If you notice AU plug-ins appearing in Live 11.1 whose VST2 and VST3 counterparts are missing, it's likely that Live is hosting an Intel AU via the AUHostingCompatibilityService translation tool. Please note that some specific AU involve Intel-compiled processes, and that these will require Live to be run as an intel application via Rosetta 2 as explained below.
Note: We recommend checking if your plug-ins are available natively compiled for Apple silicon and keeping a list of plug-ins which still require Rosetta, so that when a Silicon native version becomes available from the manufacturer you can install them.
How to open Live using Rosetta
To use VST2 plug-ins not yet updated/compiled for Silicon, you can force Live to run as an Intel application via Rosetta 2, as explained below.
Important: The steps below are not needed if all plug-ins are already updated for Apple Silicon. When in doubt, check the latest Apple Silicon and macOS compatibility information provided by each plug-in's developer.
- Find and select the Live icon in your Applications folder.
- Press Command – I, or right-click / access the File menu, and select “Get Info.”
- In the Info window that opens, check the box for “Open using Rosetta.”
- Close the Info window and re-launch Live
MAC M1 with Logic -> If the Editor is not visible in the Instrument folder of Logic.
The Editor run on MAC M1 and Logic if you use Rosetta:
How to open Logic using Rosetta
To use AU plug-ins not yet updated/compiled for Silicon on an Apple Silicon Mac, you can force Logic to run as an Intel application via Rosetta 2, as explained below.
Important: These directions are not needed if all plug-ins are already updated for Apple Silicon. When in doubt, check the latest Apple Silicon and macOS compatibility information provided by each plug-in's developer.
- Find and select Logic in your Applications folder.
- Press Command-I, or right-click / access the File menu, and select "Get Info."
- In the Info window that opens, check the box for “Open using Rosetta."
- Close the Info window and re-launch Logic.
If the warning message appears:
Standalone Editor:
You have to open the Editor App via the right mouse button and then select "open" at the window.
Standalone and VST plugin Editor -> When the warning message appears:
Click on "Cancel", then open the "General" tab of "Security & Privacy" under "System Settings" and click on the padlock in the lower left corner,
the component will appear in the "Allowed Applications" section - click "Allow" and Ableton / Logic will give the same warning, but this time with an "Open anyway" button ....Click and all is well.
If that doesn't work, you can overcome the Gatekeeper with another method:
Here is the video link below.
Here the first part describes how to open the "Plugin Version"
and the second part how to open the "Standalone Version".
You have problems with plugins in the new
systems (Mojave and higher) from Apple !?
"The editor plugin does not start in DAW and an error
message is displayed"
Here is the solution:
(Applies to VST and AU (Component) plugins.)
1. Rescan the plugins with problem from your DAW.
This will force OSX to give you this fail message:
"... cannot be opened because the developer cannot be verified.
macOS cannot verify that this app is free from malware"
The error message may also read:
"... isn't allowed as it was downloaded from the internet. …
Or so:
Click „Cancel“ then:
2. Go to System Preferences > Security & Privacy > General tab the
last line with "was blocked from use because it is not from an identified developer",
click "Open Anyway".
3. Rescan the plugin from the DAW. You will get this message:
"macOS cannot verify the developer of... Are you sure you want to open it?"
4. Click Open, that's it
You have problems with Apps in the new
systems (Mojave and higher) from Apple !?
Here is the solution if the Editor App does not start.
Below are the error messages that the MAC can display.
View the app security
settings on your Mac
By default, your Mac's security and privacy settings are set to allow apps from the
App Store and from identified developers.
If this is not the case, please change it.
How to open an app that hasn’t been notarized
or is from an unidentified developer
Launch the Editor app.
This or a similar error message appears.
In macOS Mojave and higher, when an app fails to install because it hasn’t been notarized
or is from an unidentified developer, it will appear in System Preferences > Security & Privacy,
under the General tab. Click "Open Anyway" to confirm your intent to open or install the app.
Restart Editor App:
The warning prompt reappears, and you can click Open.
Click "Open"
The app is now saved as an exception to your security settings, and you can
open it in the future by double-clicking it, just as you can any authorized app.
Here are described the error
messages that the MAC can display.
Open a developer-signed or notarized app
If your Mac is set to allow apps from the App Store and identified developers,
the first time that you launch a new app, your Mac asks if you’re sure you want to
open it.
An app that has been notarized by Apple indicates that Apple checked it for malicious
software and none was detected:
Prior to macOS Catalina, opening an app that hasn't been notarized shows a
yellow warning icon and asks if you're sure you want to open it:
If you see a warning message and can’t install an app
If you have set your Mac to allow apps only from the App Store and you try to
install an app from elsewhere, your Mac will say that the app can't be opened
because it was not downloaded from the App Store.
If your Mac is set to allow apps from the App Store and identified developers,
and you try to install an app that isn’t signed by an identified developer
and—in macOS Catalina and later—notarized by Apple, you also see a warning
that the app cannot be opened.
If you see this warning, it means that the app was not notarized, and Apple could
not scan the app for known malicious software.
You may want to look for an updated version of the app in the App Store or
look for an alternative app.
If macOS detects a malicious app
If macOS detects that an app has malicious content, it will notify you when
you try to
open it and ask you to move it to the Trash.
Support from Apple on this: