Ableton Live 11

[WatchTheGuitar]

use 48kHz while playing, switch to 96kHz for renders.

That's useless. Upscaling won't make it better.

I’m saying if you’re playing, not recording, use 48kHz

[3dsmatt]

Your computer isn't up to it. Live 11 is running on Rosetta which uses more CPU, 96k and 128 sample buffer is crazy intensive, especially in Live which as a DAW optimised for live performance, uses more CPU (since it can't employ behind the scenes trickery to save CPU cycles, like Reaper, Cubase, Studio One et al can) and on top of that you are using a plugin that is notorious for being CPU heavy.

Even my monster PC would struggle to cope with the same load in Live 11...

Your monster PC would struggle with an 808 drum rack/VintageVerb/TIMP ??

Nebula 4 .... Live 11 ....These are all sold as consumer goods. Not to be used with super computers necessarily. The system requirements for all of these plugins are pretty modest. And we are talking about one channel with one instance of n4 and one instance of Valhalla. It runs equally when I raise the sample rate anyhow. Also, if it's designed for live use , wouldn't it be desireble that it function with low latency and its' corresponding low sample rate.

I don't know. I think Live is not solely marketed as a live music DAW. I think it is also intended as a studio daw. Had they stated in their sales pitch that Live is only really for live performance and wont handle either 96khz, low sample rates or running on a mac (my i5 2017 had the same problems) with 16gb.... then I obviously wouldn't have bought it.

[3dsmatt]

Are these the kind of comprises you should be forced to make though when using a professional digital audio workstation ?? Working in 96khz is not unheard of. And when it comes to sample buffer, the latency is terrible.... I literally can't play. It feels like it's about a second late! Even at 128 , when there are five or six tracks it is just awful.

....what I mean to say is that these things (which I have obviously considered) are not fixes, they are papering over cracks.

There are limitations to everything, it depends what you feel is most important.
Maybe not a great move to leap straight into using a brand new and to an extent untried processor, let other people endure the frustrations and work out the kinks, come to it when it’s been out and used professionally for over a year. NASA’s 10 years is probably overkill
Yes M1 is promising, but you’re only going to see the real benefit of it when people have created all the DAWs and plugins you use in native form. Until then there will be a translation overhead which may hamstring performance.

Personally I’ve adapted my workflow to lower sample buffers and latency for recording only, freeze tracks when I’ve finished making changes for now etc. It’s actually a good way to move forward on a track, ultimate tweakability at any time can ramp up the procrastination factor.

Thing is. My non m1 2017 mbp 16gb had the same issues. Overheating, maxing CPU. So its' not an M1 issue.

Freezing tracks, reducing sample rate and buffer ..... you might see them as reasonable and workable compromises. I see them as stifling creativity and quality.

Anyway. I can't believe anyone thinks that one track of an 808 rack- Valhalla -N4 @96khz 128 sample buffer with one pattern , one channel producing a CPU load of 60-70% is normal .There is definitely something else afoot. I pretty sure its the fkin graphics or something.

[antic604]

Anyway. I can't believe anyone thinks that one track of an 808 rack- Valhalla -N4 @96khz 128 sample buffer with one pattern , one channel producing a CPU load of 60-70% is normal .There is definitely something else afoot. I pretty sure its the fkin graphics or something.

Try contacting support about it.

Also, because it's just one track it doesn't mean you can't add more stuff to the project - new tracks will be spread to other CPU cores and you might - for quite some time - see no increase in CPU utilisation. Only after all the other cores have been filled to 60-70% it should start growing.

I'm not saying it's normal, but it's nothing unusual with a heavy, serial device chain.

[PieBerger]

From the M1 thread on the beta forum

Drum racks render the whole DAW useless. CPU usage spikes over 90-95% adding all kind of delays and crackles to the sound. Mac Book Pro M1, 259Gb, 16Gb.

Are these comments being taken into account? The drum rack problem has been described since months ago and non of the betas have addressed it. It's quite a huge problem I'd say. What are the plans with the development of a native version? Can we have any more info?

This was from last week, I noticed that there were similar reports of poor performance using Drum Racks in older replies too (circa 3 months). It's possible you are suffering from the same problem.

It's definitely worth getting in touch with Live and or joining the beta, so that you can report your problems and help fix them!

[Atlatnesiti]

So Bitwig ver.4 is macOS M1 native and yet we still have no idea about Ableton..?!

[WatchTheGuitar]

Got to love entitled early adopters “but meh benchmarks!!!”

[SLiC]

So Bitwig ver.4 is macOS M1 native and yet we still have no idea about Ableton..?!

Also BWS did a better job of both comping (in clips and linear session modes) and adding probability etc. V4 is a very nice update, and it can now also import Ableton and FL Studio data!!

Chances are you have more than one music program on your computer. (We do.) So on the import side, you can now import data from your FL Studio (FLP) and Ableton Live (ALS) files into Bitwig. Your clips and arrangements should make it over pretty cleanly, as well as VST plug-ins. And if you are coming from Auxy, you can now export your work directly as a Bitwig Studio project. Because maybe the best demo song is one you already made.

[Double Tap]

I think the CPU meter on Live 11 is unreliable, at least for M1 silicon Macs. Mine will hover around 30pc from the first tracks but there's very little incremental increase as I add more, and I can have a good 25+ hungry synths going without any audio issues at 44.1.

When it does eventually fall over, the CPU load on Activity Monitor is usually only around 50pc, so there's a whole load of unused processing power.

That said, I'm very disappointed that it's been so many months without even a beta. And Logic runs almost twice as many Divas in native.

[jonljacobi]

So Bitwig ver.4 is macOS M1 native and yet we still have no idea about Ableton..?!

Yeah, M1's been out for a whole 5 months. WTF is wrong with Ableton! And Steinberg. And... It runs fine on M1 as is. That's good and bad as it means you can use it now, but they don't have to be in a hurry to update it. I'm talking all vendors. I will give Bitwig credit for one thing, they're all over new tech. For better or worse.

[SLiC]

So Bitwig ver.4 is macOS M1 native and yet we still have no idea about Ableton..?!

Yeah, M1's been out for a whole 5 months. WTF is wrong with Ableton! And Steinberg. And... It runs fine on M1 as is. That's good and bad as it means you can use it now, but they don't have to be in a hurry to update it. I'm talking all vendors. I will give Bitwig credit for one thing, they're all over new tech. For better or worse.

Logic (obviously) , Reaper and FL Studio went first, now Bitwig...so not that early an adaptor!
Live is always slow but it gets there in the end!

[rod_zero]

Computer company changes OS, people are angry at small developers xD

I guess that's why you people love paying for adapters for using USB peripherals xD , al hail the big apple

[SLiC]

Computer company changes OS, people are angry at small developers xD

I guess that's why you people love paying for adapters for using USB peripherals xD , al hail the big apple

Actually I think small developers like Bitwig (30 Vs 300 staff) see early adoption of new Apple tech as a possible way to gain publicity and a few converts...Ableton have a big user base that on the whole will wait...they may grumble, but they will probably just wait...

[pdxindy]

So Bitwig ver.4 is macOS M1 native and yet we still have no idea about Ableton..?!

Yeah, M1's been out for a whole 5 months. WTF is wrong with Ableton! And Steinberg. And... It runs fine on M1 as is. That's good and bad as it means you can use it now, but they don't have to be in a hurry to update it. I'm talking all vendors. I will give Bitwig credit for one thing, they're all over new tech. For better or worse.

Logic (obviously) , Reaper and FL Studio went first, now Bitwig...so not that early an adaptor!
Live is always slow but it gets there in the end!

Live has more 3rd party components... so it will take longer.

[zoidkirb]

Honest question: Do most people really need low latency on the DAW side for recording things like vocals and acoustic instruments? I've always done fine using my hardware's zero latency direct monitoring.
And when it comes to VSTi's there's some level of latency compensation going on DAW side to help out there.