Anyone else dealing with Live 11 issues?

[dubdub]

I'm getting random CPU spikes, frequent freezing, crashes etc. ... I didn't have those issues with Live 10. According to the Ableton forums, quite a few people on Windows seem to have similar issues. Not sure if I should wait for the 11.1 patch or just go back to 10. Weirdly enough, the first few 11 patches worked fine for me. I've already fully re-installed Ableton (deleted cache etc.) multiple times but the issues persist.

[Mslwte]

tbh I have had a few crashes and I've put it down to SoundID crapping out after an update. There was a follow up SoundID patch that seemed to cure my problems.

Saying that I have just opened live and it crashed on start up

[Críoch]

I've found live 11 rock solid.

Problems updating it though. There's a 11.0.10 update or something atm.. and it's failing every time. Took about 2wks to finally get it on 11.0.6.

[mervv]

I'm getting random CPU spikes, frequent freezing, crashes etc. ... I didn't have those issues with Live 10. According to the Ableton forums, quite a few people on Windows seem to have similar issues. Not sure if I should wait for the 11.1 patch or just go back to 10. Weirdly enough, the first few 11 patches worked fine for me. I've already fully re-installed Ableton (deleted cache etc.) multiple times but the issues persist.

I'm on windows, and while I haven't had many issues with freezing or crashing (at least no more than with Live 10, which was occasional), I have noticed a lot of CPU spikes. Is it causing drop-outs, or are you just noticing it on the CPU usage meter? Apparently, CPU monitoring works differently in Live 11; the measurement interval is much shorter. Hence why it now includes a slower, average usage percentage and a faster, peak usage percentage.

[Duffdeal]

Lots of crashes here, particularly on rendering.

[Amøbe]

I have seen on Reddit that quite a few have had issues. I haven't been hit personally and are using Mac (I don't know if that has anything to do with the issues)

[Críoch]

finally on 11.0.10 today. Waiting for it to jump to 11.0.11 next.

[Lost to the Void]

OK maybe I will wait to install it then.
I mean at this point a few more months is nothing.

[dubdub]

I have seen on Reddit that quite a few have had issues. I haven't been hit personally and are using Mac (I don't know if that has anything to do with the issues)

The issues seem to mostly affect windows users.

[dubdub]

I'm getting random CPU spikes, frequent freezing, crashes etc. ... I didn't have those issues with Live 10. According to the Ableton forums, quite a few people on Windows seem to have similar issues. Not sure if I should wait for the 11.1 patch or just go back to 10. Weirdly enough, the first few 11 patches worked fine for me. I've already fully re-installed Ableton (deleted cache etc.) multiple times but the issues persist.

I'm on windows, and while I haven't had many issues with freezing or crashing (at least no more than with Live 10, which was occasional), I have noticed a lot of CPU spikes. Is it causing drop-outs, or are you just noticing it on the CPU usage meter? Apparently, CPU monitoring works differently in Live 11; the measurement interval is much shorter. Hence why it now includes a slower, average usage percentage and a faster, peak usage percentage.

I'm getting actual drop outs. I've had projects become unusable that would've run fine on prior versions.

[speen]

has anyone joined an ableton beta program before?

i'm sortof tempted to stepin to make use of 11.1's native use of the Apple M1 processor, which probably makes it run much better on a new MBP

not sure how many iterations of the beta version they usually go through, they are now in 11.1b7.

[mindstuff]

Mine crashes all the time if I'm using 3rd party plugins...no offense to Kush Audio but they seem to be the culprit most of the time.
Whenever you get the screen that tells you why Ableton crashed (on mac only, don't know how windows does it) you'll see a bunch of text. In there it will show what thread created the crash (See: "Crashed Thread"). Scroll down till you find that thread and often times you'll see the name of the offending plugin. I reported these crash reports to Kush Audio and they ended up patching the plugin. Sucks to lose time like that but software is like this sometimes.

Example:

Code: Select all

Process: Live [24729]
Path: /Applications/Ableton Live 11 Suite.app/Contents/MacOS/Live
Identifier: com.ableton.live
Version: 11.0.6 [2021-08-09_daefd4db27] (11.0.6 [2021-08-09_daefd4db27])
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Live [24729]
User ID: 501

Date/Time: 2021-09-03 21:10:38.735 -0700
OS Version: macOS 11.4 (20F71)
Report Version: 12
Bridge OS Version: 5.4 (18P4663)
Anonymous UUID: F2FE0895-9352-71D1-BFEE-4528404F7AA0

Sleep/Wake UUID: 234B20A2-4010-4BAB-9BE7-F42FD04554AE

Time Awake Since Boot: 280000 seconds
Time Since Wake: 6900 seconds

System Integrity Protection: enabled

Crashed Thread: 52 PXDKThread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [24729]

Thread 52 Crashed:: PXDKThread
0 com.apple.CoreFoundation 0x00007fff20645165 CFStringGetCString + 57
1 com.kush.silika 0x0000000188910e40 ACFShutdown + 462991
2 com.kush.silika 0x0000000188910e9f ACFShutdown + 463086
3 com.kush.silika 0x000000018891216b ACFShutdown + 467898
4 com.kush.silika 0x0000000188a30710 ACFShutdown + 1640799
5 com.kush.silika 0x0000000188a9d048 ACFShutdown + 2085527
6 com.kush.silika 0x0000000188804342 0x1887c0000 + 279362
7 com.kush.silika 0x000000018880b55d 0x1887c0000 + 308573
8 libsystem_pthread.dylib 0x00007fff205c48fc _pthread_start + 224
9 libsystem_pthread.dylib 0x00007fff205c0443 thread_start + 15

[Críoch]

Annoying especially when it's stuff you really like..

I can use the korg ms20 vst no probs.. but the MonoPoly vst is a total fucking disaster. Crashing on save. It saves.. but there's a crash report. It works regardless of that, but it feels wrong using it when you are waiting for the conflict to occur.

[Lost to the Void]

Finally upgraded. Seems to work less efficiently, CPU load is higher for me. Not impressed.

[FvH]

I'll stick with v10. Tried 11 suite, not impressed beside Granulator 2.

[msl]

I'm starting to get really pissed off with 11. Fails to load and hangs ALL the fucking time. Delete prefs, rinse repeat. Great idea including M4L native, but why fuck up the file paths to the old plugins, all my old tracks don't see them! After much frustration I had to put a second copy of Convolution in a new folder and re-link to that every time I open an old project, as I could not do it with the one in the new v11 location. FFS

Been using Live since '09 but I'm honestly starting to consider maybe switching to Bitwig.

[Lost to the Void]

Well I`ve been using it for a little while now.
I`m finding it to be very good, the early issues are ironed out, the new fx are really nice, love the spectral resonator, it`s very powerful.
Absolutely adore the Ableton wavetable synth, it has crazy manipulation options, and it has totally gotten me into wavetable. To the point where I am considering getting the Korg wavetable synth. It (ableton wavetable) needs more LFO`s though (only has 2), but adding max for live LFO`s is simple enough.
I`m still getting used to the rearranged audio clip window, which is frustrating me a little.
Overall though, I like it, have made a few releases with it and it`s all doing what I want it to do.

[dubdub]

I'm starting to get really pissed off with 11. Fails to load and hangs ALL the fucking time. Delete prefs, rinse repeat. Great idea including M4L native, but why fuck up the file paths to the old plugins, all my old tracks don't see them! After much frustration I had to put a second copy of Convolution in a new folder and re-link to that every time I open an old project, as I could not do it with the one in the new v11 location. FFS

Been using Live since '09 but I'm honestly starting to consider maybe switching to Bitwig.

Same, my Live 11 is still extremely crash happy. It's getting annoying.

Main thing that's keeping me from switching to Bitwig is that it's sooo ugly and overloaded GUI wise. That and the superb Push2 integration. Might just go back to 10 or something.

[jordanneke]

Finally upgraded my PC and to live 11.

Have to say, I've had no issues at all and I love it.

Mind you, I was running Live 9 on a 12 year old PC before, so there is that.

[Amøbe]

Well I`ve been using it for a little while now.
I`m finding it to be very good, the early issues are ironed out, the new fx are really nice, love the spectral resonator, it`s very powerful.
Absolutely adore the Ableton wavetable synth, it has crazy manipulation options, and it has totally gotten me into wavetable. To the point where I am considering getting the Korg wavetable synth. It (ableton wavetable) needs more LFO`s though (only has 2), but adding max for live LFO`s is simple enough.
I`m still getting used to the rearranged audio clip window, which is frustrating me a little.
Overall though, I like it, have made a few releases with it and it`s all doing what I want it to do.

Just out of curiosity - what are some of its strengths that you find? I find it kind of hard to use outside of pads, but Jordan just posted a track with a lovely lead from it, so I'd like to hear how others utilizes it?