how to add an AU plugin and locate the AU/component AudioUnit folder with Waveform on mac ?

[thejba]

Hi there !

I've been having some problems – multiple crashes as soon as I open the project – with a fave vsti of mine (Cassette Drums 909) and wanted to try with the AU version instead to see if that could solve the issues, but I don't see how to add (in OSX Mojave) an AU folder within Waveform. The folder is here (Mac HD/library/Audio/plugins/components), but I don't see within the "file locations" or "plugins" tabs how to add it (so the only AU instruments that Waveform see are the stock ones, included with OSX, and buried in i don't know which hidden folder somewhere).

Can anybody help me here ? Thanks !

[tovokas]

All of my AU’s are located in Mac HD/Library/Audio/Plug-Ins/Components as well, and Waveform discovers them as expected. I don’t think there is any way to change where Mojave or Waveform looks for 3rd party AU’s, but perhaps in your case it’s a permission issue for the folder, or the individual plugin within the folder? Do you see other plugins in the Components folder that Waveform is also not recognizing?

[Lutin mutin]

Same problem here, on Waveform 11 pro, v11.0.24 (but is exactly the same problematic since the first Waveform 11 pro in public access...)

In my program, when you go to the settings page > File locations, in the section regarding the plugins path locations, there is no AU plugins access defined...


But what is very strange, is that in the settings page > Plugins > Scanning and sorting, in the little window there, as always in the other versions of Traktion, the AU plugins are indicated...


So, in my case, when I click on "process to scan AU plugins", the Waveform program "knows" the path location access, and it scans all my AU plugins...
Is that not very strange ?

So, I hope the TSC guys will correct this king of bug in a future version... or in W12 ?

[thejba]

Ok, problem solved as far as I'm concerned.
The components folder (the one where the non-stock AU are stored) in the library/audio folder was marked as "forbidden" (with the little no entry sign) and I unlocked it, to no avail, but just a few minutes ago I ticked (in OSX, not waveform) an "apply to everything in this folder" kind of box, and here we are, the 3rd party AU are showing in Waveform.
Weird thing is I have to, for some of them, install them again for Waveform to see them - but not all of them, for some reason.
And I can't have Waveform ignore the "stock" (included for Garageband, I guess) AU plugins, too.

[tovokas]

So, in my case, when I click on "process to scan AU plugins", the Waveform program "knows" the path location access, and it scans all my AU plugins...
Is that not very strange ?

I just think that's how most music apps on MacOS work: Studio One and Reaper don't give me the option to choose another AU directory either, only VST directories. The AU directory is set by the OS.

[dRowAudio]

Yes, AUs aren't loaded by file like other plugin formats. You ask the OS for a list of them and then load them through system calls. You can't open an actual AU file.
This also means you can't install them to anywhere other than the system directories. These are:
"/Library/Audio/Plug-Ins/Components"
and (but not usually)
"~/Library/Audio/Plug-Ins/Components"

[Lutin mutin]

I was not aware that the actual macOS is so inflexible concerning the AU plugins location folder, because all my other musical applications indicates the AU plugins file location.
So now, with the above explanation of 'dRowAudio', I can understand the choice of TSC relatively to the "no Path necessity" for the AU plugins files location.
I'm a little less stupid than this morning...