Everything I Know About Optimizing Ableton Live For Apple Silicon

my mind is blown by the buffer size tip alone cuz i always just had mine at the highest until i had to record stuff ... ahhhh this video is so great thank u <3

lmao my cpu usage went from 30% to 6& thank u so much man! God bless!

Great video Will ! Love the community you founded!

Amazing video, thank you so much!

This video is GENIUS ! I just changed my buffer size from 512 to 256 and voila ! it lowered my cpu usage from 39% to a blowing 13%... Thanks for the info ! :-)

This was such a valuable video! I had been wondering why i was having disk error messages and dropouts after having added locators. Collect all and save on everything has also worked flawlessly for me. Using an M1 Max MBP 16”

As the locators are fairly small in Live, I tend to create an empty MIDI track at the top of my session and add separate MIDI clips with a colour code for each section of my track. Visually at least, it’s far easier to see what’s going on than using the standard locators.

Would have never thought to lower buffer for better performance, been doing the opposite forever (PC's, Intel Macs). Why is this not in Ableton docs?! Thanks - you're the man!

this is legit the best youtube channel for ableton anything thank you youre a treasure Will

Hey man! you really blow my mind by the buffer size... I recently buy a Mac Studio M2 Max and it's been HEEEELLL!!! I don't know why Ableton 12 doesn't work with plugins (and I assure you that I've payed for them!) so I don't know what to do. In my old Macbookpro I used to use AU but now I read that it's better if I use VST3 but no matter what I do, my session crashed at minimal use. I'm using Ableton with Rosseta by the way... PLEASE CAN YOU HELP ME??!!!

I still run live 10 on an intel based mac. rock solid. want to make the switch to apple silicon and live 11 soon. thanks for the info!

You have a lot of valuable info and a great channel, keep up the good work! Respectfully, I disagree with the part that says to set the cpu metering on average. If our goal is to have zero dropouts, then current cpu is all that matters. Once you go beyond 100% even as a momentary spike you will have a buffer error. This can be easily tested by creating an artificial heavy cpu load in a single point of time. For example, playing a lot of voices simultaneously on a VST like Serum with high unison count while using a low buffer size. The transient will crackle, even though the average meter stays within safe limits.

That sorted my problems i couldn't run NI and Keyscape whilst running tracks and now i an doing it without problems...thanks a million ,great information.

Any word on using Apple Silicon and Paralells/Bootcamp for Ableton?

I thought it was supposed to be lower than 512.. I feel like lower than 256 will definitively cause popping

Takeaway: 256 or lower

I think this might be the opposite on Live 12, because if I go to 32 samples, i get 72% and when I go 256 samples, I get 32% CPU.

Both the Locators and Collect all and Save issues should not make any performance difference in theory and really sound like nasty bugs in Live. Any feedback on this from the Ableton folks?

Hi, I'm doing MIDI zoning via Ableton with my Yamaha MODX and I'm getting MIDI hangs. Have a M2 Pro. Do you have a solution for that? If you have, that would be a great help.

what about m2 pro chips that uses more effeciency cores than performance core?