but you are measuring average cpu usage by default. you need to measure current cpu usage. you will experience small spikes after just 5 instances of any plugin, native, vst or audio-unit. at 10-15 tracks your cpu usage will increase to 500 percent and more and audio will crackle if you start and stop playback successively.

 

It's not top-tier neither was, every producer doesn't need i9's or beasty computers for music production and don't have projects with 100+ tracks. For people need a budget choice that still has enough processing power for their need. I think an m1 around $600 will still be the best choice.

Did you turn on AU setting in plug-in preferences? Only natively supported plugins will show under universal mode.

 

Yes I did, on and off even twice to make sure. Rebooted computer. Rescan. Deep scan again. Still no effect.

Unless I missed a new AU button in settings in Ableton 11.1, what worries me is that everything worked fine until Ableton 11.0.12 yesterday.

All my AUs were working fine until yesterday. Surely 11.1 is bringing something new to the table that I missed out. I guess I need to do some digging in the change log and lurk reddit forums to find out.

https://www.ableton.com/en/release-notes/live-11/

New features and improvements:

• Native Apple Silicon Support
  • Live 11.1 adds native support for Apple M1 computers.

I would have thought that 11.1 was only bringing NEW FEATURES (native M1 support), not LESS FEATURES (getting rid of .AUs).

My bad I updated too fast...

 

Okay I found it: https://www.dropbox.com/s/h3wc0bip8v3c4lw/OS x validate all AUs.zip?dl=0

I don't know what I did, but a combination of all the steps above finally worked! I think OSX Validate all AUs might have done the trick (after a few minutes though, by reindexing my plugin folder 100%).

Let's bring the awesomeness of the 11.1!

 

Ableton 11 seems to work fine, but my Serum is broken now. Keeps hanging on a midi note when I stop playing.

Besides my Spire is running in demo mode now, but not sure it it comes trough the update.

 

Come one guys ... you know Apple fanboys said M1 was the sh*t, killing EVERYTHING
As usual with Apple fanboys ...

So stop saying anything negative about M1 : you are hurting them

 

Ya smells like a win-azzed fanboy. Definitely m1 isn't the sh*t. Much better than sh*t.

 

It's the usual nature that early versions of major updates have some issues.Try running under rosetta and see if issue still exists.

 

Quick question of a beginner, suppose, (in Live 11.1) I’ve a plugin showing up both under AU and VST3, is it better to use native AU or VST3 version? Which one would really benefit from M1?

 

Nothing will benefit from m1 unless they are natively supported. Vst3 and AUs are almost same, use whatever works for you.

But i had an issue with waves au plugins in ableton live (before 11.1). Plugins loaded but didn't apply any processing to audio, then switched to Vst3 and it worked. Maybe now it may be fixed.

 

Come on Artic, wake up !!

 

Macbook air M1 here , and I'm a Windows user for all my life ... Got an M1 on sale last year on Christmas , and oh boy there is a difference ... Having the possibility to make music , edit 4k video in Resolve , process photo in Lightroom, all very fast and all under 900 $ ... Big difference

I didn't try new Ableton with 100 tracks, and I don't have 200 plugins to scan , but from what I see and hear Ableton for M1 right now is much better ... From what I see everybody adapt their software for Apple M1 ...

 

From the horses mouth:
LINK

 

I would like to point out a bizarre behavior that I think is important to know about the new Live 11 (macOS): Start-up is now faster, you no longer have to wait for the plugin scan as it now takes place in the background. The downside is that in the first few minutes of using the app, the list of VST's is empty.
At first I thought it was a bug but it is not, in fact this behavior is also confirmed by the official website:

 

I don't consider it bizarre, just perhaps not a good design choice. They should have a small text box in the bottom bar [Scanning Plugins] and have it flash on a slow period rate as its doing the job. That way User will know there is an active task but it doesn't occlude with a pop up box, etc. Clicking it could perhaps cancel the task as well.

 

So where do things stand with it using AU's correctly (after forcing validation again)? It doesn't matter if it only sees them in your plugin manager, and @recycle's post does not mention them. Do they work?

 

Both ARM and Intel AUs working fine without any extra steps here.

 

Thanks for pointing this out, this is what happened to me yesterday, it took 30 minutes before my .AU were properly scanned and reappeared all fine xD

On the other end I will add that in some instances I also had to reinstall (or update/re-codesign) some VSTs/VST3s that would no longer show up.