Ableton Forum

A HERO OF THE PEOPLE!!!!

THANK YOU!!!!

This has happened for me too, CPU lagging seriously with the new update! Will try and reinstall 10.0.1. Fingers crossed.

Some perspective and potentially some good advice from 2016, "Insane CPU (since upgrade 9.6)".

I ran Live 8.42 until last christmas, where I upgraded to 9 and 10 at once. I noticed that on startup while the wav samples are loaded into the project the GUI freezes and even my APC20 does not work. Had to double the audio buffer to get a decent performance regarding controllers. Never had any issues with 8x. I could record up to 4 wav tracks and 16 midi tracks at once. Now I'm happy if I can record the master sum.
Can live with that but since 10.01 I am experiencing system crashes out of nowhere. Never had this issue and I cannot trace the source.
I am running 10.01 with Reason 6.01 in ReWire. In Live I only use some Ableton effects. No VSTs, no Max for Live. Everything is done out of the box and sound generation is done completely in Reason. So I consider there is an immense performance loss in 10 and some really nasty bugs in things that worked like a charm before

Stromkraft wrote:Some perspective and potentially some good advice from 2016, "Insane CPU (since upgrade 9.6)".

The link takes to a thread called "Annoying pitch" ?

But yeah, uhhh, so far everything works quite good on 10.0.1 over here, so from the looks of it... I'll just skip this x.x.2 and see what sort of reports the next one gets

Nokatus wrote: The link takes to a thread called "Annoying pitch" ? :)

Link corrected. Thanks!

I can report I see no change in performance so far going from 10.0.1 to 10.0.2 release, not did I see any issues in the beta.

I believe it's possible certain third party instruments are at a disadvantage, as have been the case in the past. My current instruments without issues are Softube Heartbeat, Madrona Labs Aalto, Waves Element 2 and U-he TyrellN6. All but the last are very demanding instruments, so I'm counting on that. I can't run many instances, but my machine is from 2011 so…

Generally, I strongly believe Ableton should drop everything else and focus on performance only for the rest of 2018! If there are grave performance issues for anyone with any instrument or effect chains, what's the point?

Some passed on advice by Urs from U-he, "Use VSTs, not AU!".

daizok wrote:

cane creek music wrote:10.0.2 is very troublesome for me, is there anywhere i can download 10.0.1?,
I went into my account and looked at the download archive but there were only versions of live 9.

http://downloads.ableton.com/channels/1 ... 0.1_64.dmg

Thank you, but do you have a link for the Standard/Mac 10.0.1 version.

daizok wrote:

cane creek music wrote:10.0.2 is very troublesome for me, is there anywhere i can download 10.0.1?,
I went into my account and looked at the download archive but there were only versions of live 9.

http://downloads.ableton.com/channels/1 ... 0.1_64.dmg

Is there 10.0.1 for Windows ?

10.0.2 is most laggy update i ever seen, im using ableton from 8 version, and its never been so laggy as now.

I am having real lag problems with 10.2. To the extent that wavetable has become unusable. It just locks everything up and the beach ball of hell appears. I am on OSX 10.11.

If people are having issues with 10.0.2 performance, please remember to contact [email protected] so we can get some more info on which systems are having the issues. That definitely helps us narrow down problems, thanks!

I'm back on 10.0.1 and the project that wouldn't open now opens, and i don't have all CPU issues i had.

Support did say theres a known Audio Unit problem their looking into on 10.0.2

cane creek music wrote:I'm back on 10.0.1 and the project that wouldn't open now opens, and i don't have all CPU issues i had.

Support did say theres a known Audio Unit problem their looking into on 10.0.2

unusual that it's noted as an AU issue, because I'm on Windows 7 and I have projects which won't open in L10.0.2. They just crash Live as soon as I attempt to load them. I've never had that issue before.