dboy wrote:It appears as if this issue is being ignored. Anyone at Ableton working on this or even sees this behavior?

I'm getting similar vibes, to be honest. It's a tool I need for my upcoming live performances, so it is a bit of a pain.
A reply from the support email said my set is too large, uses too many plugins, etc, but all I can say is it did not happen before so their response isn't valid, in my opinion.
I've always offered my fullest support for Live and I'm all up for helping Ableton make it the best piece of software there is but I'm feeling a bit let down at the moment.

More and more users are reporting this all the time so I'm a little surprised by how it's being handled. I'd love some sort of reply regarding whether it's being worked on or acknowledged or if they just write it off by saying all our sets are too heavy (and I doubt that's the case).

dboy wrote:It appears as if this issue is being ignored. Anyone at Ableton working on this or even sees this behavior?

I'm getting similar vibes, to be honest. It's a tool I need for my upcoming live performances, so it is a bit of a pain.
A reply from the support email said my set is too large, uses too many plugins, etc, but all I can say is it did not happen before so their response isn't valid, in my opinion.
I've always offered my fullest support for Live and I'm all up for helping Ableton make it the best piece of software there is but I'm feeling a bit let down at the moment.

More and more users are reporting this all the time so I'm a little surprised by how it's being handled. I'd love some sort of reply regarding whether it's being worked on or acknowledged or if they just write it off by saying all our sets are too heavy (and I doubt that's the case).

Not only that, but in my case, for instance, I'll get spikes to 110% on a part of the project that just played through fine (sometimes looping) several times before. Correct me if I'm wrong, but I would expect the exact same passage to play through multiple times with roughly the same CPU load. What I'm seeing is a consistent 30-35% load, that then spikes between 70-110% with the attendant dropouts, only to "recover" and go back to normal. Anyone from Ableton care to comment on what could cause that?

Same thing here. Heavy load in idle, spikes and fans going crazy on a very small project. Definitely something wrong in the way this is coded for OSX. Some feedback from Ableton on this would be appreciated at this point.

The more data we have from you, the easier we have tracking and fixing it. We have located a few bottlenecks, but to make sure this also benefits you send us projects showing issues to make sure our fix will solve your performance problems. Rest assured we find it very concerning that some of you experience quite fatal performance dips.

Ideally please save out the live set so it is loadable in both Live 8 and 9
When sending it, also attach a status report

Hm, in the most recent project where I was having horrible spikes, the situation seems to have resolved itself, and the entire project plays straight through, only hitting ~35% at the most. Granted, I haven't worked with it all day (will try that this weekend). The only configuration change I made was unplugging my backup drive that Time Machine uses. I also restarted my machine fairly recently, but I've done that before and the issue persisted.

I thought it might be the latest 9.0.5 beta that did it, but I opened the project back up in 9.0.4, and it runs smoothly there too.

Mal, maybe you can answer this for me (and I think I already know the answer)... when Live shows you the percentage of CPU in the meter, is that basically an aggregated metric telling you how much of the wall clock time the audio engine took to process the buffer of samples, vs the amount of time it had to do it? So, for instance, if we're at 44.1kHz at a 512 sample buffer, if all 512 samples are ready to go in 4ms, on the busiest processor, that would read about 35% on the CPU meter, correct?

Now, if there are other processes on the machine, stealing cycles, and my previous assertion is true, that percentage would go up, right? Basically what I'm getting at is, it's possible that CPU spikes observed in Live aren't actually caused by Live itself but a different program using up CPU on the same cores?

Still this problem with Ableton index when you launch Live:
I had folders under the "Places" lane, pointing to files located on external drive.
Had to delete those folders because when the external drive is not connected, the wheel of "Places" kept on spinning and trying to locate the drive with result Ableton index to climb to a 100% value and not dropping after a little while as expected..
I had to precise, this is with Live 9.0.5

I tried adding folders to places and removing the drive, the label in the sidebar is correctly greyed out.
When I delete the folder from the drive, the label will stay there but will not show any files.

I did at no point see the ableton index consume 100% CPU, nor that it was trying to rebuild the DB with missing files.

Thom Nagy wrote:I'm experiencing the same issues and it is highly frustrating.

A 2.7GHz i7 with 16GB of RAM should be able to handle almost anything, that I throw at it, yet I get CPU spikes (and audio crackle) of 62% when running this test here: viewtopic.php?f=1&t=191549

I'm thinking, it could also be Komplete 7 that's slowing down the system, as I had this issue on an older iMac.

Anyway: Ableton, please take care of this.

I don't think it's because of Komplete.

I do sound to picture and thus use Live everyday, and I don't use any 3rd party plugins or very very rarely; only Live and m4l, it can't be more "clean".
Powerfull quad i7 laptop on osx 6.8, and I also encounter a lot of performance hiccups since L9, fans crazyness... And best of all, it's quite random from day to day within same sets. And, as you said, those machines should be able to handle a fucking lot of almost anything.