3.2 is nothing but crashes at launch.

So I have another audio app on my Mac — iZotope RX. It supports both Audio Units and VST plugins. When I hit “Rescan,” I see a ton of CPU activity for “tccd” which means that the scans are passing through Apple’s Transparency, Consent and Control interface. It also scans the UAD plugins without issue. The only notice is a warning from the plugin itself that the UA interface is not connected. The plugin UI still appears.

The 0x1 exceptions in Audacity appear to be simple access exceptions, where macOS is blocking this at the security layer. I suspect Audacity is not asking for permission “in the right way” to scan or load these plugins. It could be a simple file access issue where the app needs “full disk access,” or it could require a special entitlement to load CoreAudio plugins. I’m not entirely sure since I’m not a developer; I’m a Mac sysadmin who follows this stuff pretty closely.

There was a Black Hat presentation last year where someone exploited coreaudiod and tccd via a audio plugin, gaining root-equivalent access to the system. Apple closed that loophole. So Audacity may need to update their code to “ask” to use the UAD plugins in a more secure manner.

Just a wild guess.

Still updating to new version its not crashing but will no longer allow me to monitor audio through my Yeti micaphone? Have all the setting used that I did for previous version. So frustrating. Why do they have to keep adding and editing a program that is working fine.

There is nothing in the new version that should affect that. Try increasing the volume on the playback level meters.

Older versions of Audacity are available here: Old Audacity versions download

I tested a fresh build of Audacity that was generated by a pull request. It seems to fix the issue with UAD plugins.

I’d suggest everyone wait for at least the nightly or beta build, because the unsigned code doesn’t run on arm64, and some other weird things happen.

Thanks for your favorable report. Yes, the developers seem to have made some significant progress on this issue - and they are still testing these changes. If you wish to test you can download the latest nightly 3.2.2 beta here: nightly.link | Repository audacity/audacity | Workflow build.yml | Branch release-3.2.2

Disclaimer: Do not use alpha or beta builds for production work.

This issue has been addressed in Audacity 3.2.2 which is now available here: Audacity ® | Downloads

This issue has been addressed in Audacity 3.2.2 which is now available here: Audacity ® | Downloads