AU Compiles but not visible

[ulrik]

@d-healey said in AU Compiles but not visible:

I believe a 2013 intel mini Mac running monterey.

That's probably why it takes so long. Older system.

Monterey is the latest system :)

[d.healey]

@ulrik said in AU Compiles but not visible:

Monterey is the latest system

I meant the hardware

[ulrik]

@d-healey Ok

[orange]

@trillbilly Have you tried clearing Audio Unit cache?

You can follow this quick tutorial: https://noiseash.com/knowledge-base/i-cant-see-my-plugins-in-logic-pro-x/

[trillbilly]

@d-healey Ok, Ill try another DAW. I believe I have an install of Cubase available.

EDIT: Just learned AU is not compatible with Cubase. Ill be searching for Reaper or another.

@orange Thanks! I looked for the file in the video but do not have an "AudioUnitCache" folder in my "Caches" folder. Nor do I have a file "com.apple.audiounit.cache" file. I have all invisible folders visible as well. Maybe Im missing something.

[orange]

@trillbilly said in AU Compiles but not visible:

Ill be searching for Reaper or another.

If you don't have Logic Pro X, you can install GarageBand, which is a free DAW in Mac. It also uses AU plugins too.

[trillbilly]

@orange Thanks. I downloaded Reaper (Evaluation License) and can confirm the 2 AU Plugins still do not show. May be nice to still download GarageBand just for future tests.

I am exporting again with another unique plugin code. This takes forever so lets cross our fingers!

The file you were explaining in the video, is this kind of like the "appdata" file in windows?

[orange]

@trillbilly said in AU Compiles but not visible:

The file you were explaining in the video, is this kind of like the "appdata" file in windows?

Not the same thing actually. It is a cache file which is AU plugins specific and it needs to be written on every new AU plugin installation, but sometimes it doesn't happen. Are you sure that you looked at the correct folder? AU cache folder should be there.

[trillbilly]

@orange This is the correct "Caches" location?

[trillbilly]

I have completed another compile with a new unique VST code but still no luck. Very strange as 7 others exported and show fine but 2 will not show at all.

@orange Ill keep digging for the AU Cache Folder. That is my only lead now lol

[Dan Korneff]

@trillbilly Go to the Logic Plug-ins Manager and see if those AU failed validation

[trillbilly]

@dustbro I dont have Logic. Is this something I can use outside of the DAW?

I checked via the terminal to ensure they were validated and received this back.

"valid on disk - satisfies its Designated Requirement"

[d.healey]

@trillbilly Did you give them a unique bundle identifier?

[trillbilly]

@d-healey Are you referring to the "Plugin Code" within HISE Preferences? If so, yes and I have tried multiple times to ensure this isnt the case.

[Dan Korneff]

@trillbilly If you don't have Logic, you can use auvaltool

[d.healey]

@trillbilly Bundle identifier

[trillbilly]

@d-healey ahhhh, here we go again. I didnt change this on any of them.

[trillbilly]

@d-healey You were right, it was the bundle identifier.

[d.healey]

@trillbilly Glad we solved the mystery :)