[teilo]

Why would they want to support AU? The only reason to use AU is Logic. Everything else (Protools excepted) supports VST, and all the plugin devs release in VST and AU, so it would be a waste of time. Bitwig is putting their time into CLAP, and for good reason. It's cross-platform, much easier to develop against, and much more advanced that all the alternatives. Even Avid has shown interest in CLAP. So has Image Line. I expect Studio One to support it in v7.

[jonpalmisc]

For starters, AUs are "easier" to run under Roestta than VSTs since AUs run out-of-process by default. This means you can use a x86_64 AU without running the entire DAW under Rosetta on Apple Silicon.

[tomduncalf]

It hadn’t occurred to me that AU run out of process, but this makes sense. Does this mean an AU crashing in theory won’t take down your DAW? (The same thing that Bitwig has it’s own isolation feature for)

I always default to AU just because I’m on a Mac and I arbitrarily decided to do so long ago. The Rosetta thing has been a nice bonus. Not sure what the other (dis)advantages are, these days I try to focus on using native Ableton and M4L stuff anyway!

[jonpalmisc]

> Does this mean an AU crashing in theory won’t take down your DAW?

Yes, this has been my experience with AUs in Logic Pro, at least. You simply get a message saying a plugin failed and that you can try reloading it if you'd like.

[teilo]

In other words, just like VSTs on Bitwig. Even if the entire audio engine crashes, you just restart it with a click.

[yungporko]

bitwig already does this with vsts because plugins are sandboxed