For some reasons the latest version of MG3 is giving me the problem where AU are scanned but VST3 are not and don’t appear in the stand alone version. I tried a few things but can not figure it out . I tried to point at the VST3 folder via custom folders, checked permissions, still nothing. Any suggestion on what I could try ?
On a different note I have been using MG3 live on stage for months now (including the last update) and it has been super reliable.
1 Like
Right, so at the moment the MG3 Windows version does VST and VST3 but the Mac version only loads AU and AUv3. This is mainly motivated by much faster and reliable plugin scanning. But we might have to support VST3 too… Is it a plugin which doesn’t have an AU or do you have any particular reason for using the VST3?
1 Like
Thank you for the reply. At least I know It’s not my system. To be honest I don’t mind having only AU on Mac if that means better performances.
In the past I installed some plugins only as VST3 and not AU to avoid duplicates (taking space for no reasons on the hard drive) because of the way they perform in some DAW (I like VST3 better in Reaper for example).
Knowing what you mentioned I can simply install AU versions. Thank you again
1 Like