Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Won't appear as a plugin in Garageband on Macbook Pro #152

Open
ApexBrother opened this issue Mar 28, 2023 · 7 comments
Open

Won't appear as a plugin in Garageband on Macbook Pro #152

ApexBrother opened this issue Mar 28, 2023 · 7 comments

Comments

@ApexBrother
Copy link

Hello,

I can't get the NAM to appear as a plugin for Garageband 10.4.6 running on an M1 Macbook Pro OSX Monterey 12.4. I can run the app as a standalone application but I can't find it inside my plugins in Garegaband. I can see that the plugin is in the directory Library-Audio-Plugins-Components and I can see all my other plugins that are running in Garageband. Does anyone know how to fix this?

Thanks

@segmeno
Copy link

segmeno commented Mar 29, 2023

Hello,

I can confirm that. I am running Garageband 10.4.6 on Monterey 12.6.3 (Macbook Pro with Intel chipset). I installed NAM version 0.7.1.

The plugins menu in Garageband is just showing my other installed plugins, but not the NAM. Standalone application is working and I also checked that the .component and vst3 files are existing in /Library/Audio/Plug-Ins.

I also downgraded to an older NAM release to check for a possible regression issue, cleaned the au cache, changed file permissions, but it still is not showing up in Garageband.

@ghost
Copy link

ghost commented Mar 31, 2023

Same Problem with GB 10.4.8 with M1 MacBook Air OS Ventura 13.3.
The NAM AU is not visible in Garageband. I tested reaper and NAM is there as a VST plugin and as a AU plugin.

@latencynone
Copy link

Same for me, NAM doesn't appear on Mac Mini OS Catalina 10.15.7 and Garageband 10.3.5. Works in my other daws Reaper and Tracktion Waveform.

@JudgeGroovyman
Copy link

JudgeGroovyman commented May 8, 2023

Same here
Macbook air M1 2020
MacOS Ventura 13.2.1
Nam 0.7.2
Garageband 10.4.8

@JudgeGroovyman
Copy link

Update: A workaround is it works great within element. I have been using the free version of Kushview's element with nam inside it and it works perfectly. Element shows up as a plugin in garageband and within element nam shows up as a plugin and just connect the inputs and outputs and voila. Element gives other advantages about creating flexible plugin chains and I was going to do this anyway so this really is no disadvantage to me. Let me know if you have any questions about this workaround.

Even if this isn't the ideal long term solution this should let basically everyone use nam in garageband.

@olilarkin
Copy link
Contributor

possibly related to #365

@metart93
Copy link

metart93 commented Jan 9, 2025

Having the same issue.
Macbook Pro 2018 Intel i7
Mac OS 15.2
NAM 0.7.13
Garageband 10.4.11
Checked that the AU is in the correct folder, reset all cache etc.

If anyone has a fix for this would be super helpful! I know other people have managed to get NAM running on GarageBand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants