You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user of hundreds of plugins to Logic Pro I would need to know what plugins are native Apple Silicon and who are not.
I found that dropping a .component or .vst3 file on Silicons window will tell if its native or not. But there isn't a way to get Silicon to parse this folders automatically.
So two suggestions:
add a checkbox to scan "Audio plugin" in the main window. Easy for the end user.
and/or, add support for dropping more than one file/directory on to the main window. And presenting the result in the same way as a normal scan. Less intuitive, but could probably be useful for other types of plugin also (Final cut?)
The text was updated successfully, but these errors were encountered:
I made some changes in the project and got it to work. It basically already does if you remove the check for .app extension in the findApps(in:) method. It will then display any files that have an executable architecture, like plugins and other code resources.
But you have to to a full scan of the drives and it will find basically anything that could be an issue.
It's quite a bit of information so I added support for dropping a folder on the main window so it was easier to select what I wanted to scan.
The audio plugin reside under Library/Audio/Plug-ins, and then you various different folders for different standards. Components being the macOS AudioUnit standard.
If you don't have anything there, I think you can find some here: https://www.audiopluginsforfree.com/mac/audiounit/
Though I'm not sure if anything on that is M1 native yet.
As a user of hundreds of plugins to Logic Pro I would need to know what plugins are native Apple Silicon and who are not.
I found that dropping a .component or .vst3 file on Silicons window will tell if its native or not. But there isn't a way to get Silicon to parse this folders automatically.
So two suggestions:
The text was updated successfully, but these errors were encountered: