Serious CPU utilisation problems in Live 7.0.1

[Amaury]

Try changing your "Plugin Buffer" settings in Live 7. I noticed that in Live 6.10 it does not seem to have any effect at all aka seems to be fixed. Maybe your settings in Live 7 are giving you the bad performance (like it's too high or too low). The default setting is "As Audio Buffers", try using something else. Unfortunately there seems to be a bug in 7.01 that will keep Latency Compensation from recognizing any changes to this setting unless you restart Live or restart a Set.

Hi Timur,

Please be careful in your statements, as we'd have to communicate before coming to conclusion. For instance, in our experience, and in the experience of many other users, plugin buffer size has the expected effect, in Live 6. I'll read the corresponding thread again now, and try to come with a meaningful answer.

Regards,
Amaury

[forge]

Try changing your "Plugin Buffer" settings in Live 7. I noticed that in Live 6.10 it does not seem to have any effect at all aka seems to be fixed. Maybe your settings in Live 7 are giving you the bad performance (like it's too high or too low). The default setting is "As Audio Buffers", try using something else. Unfortunately there seems to be a bug in 7.01 that will keep Latency Compensation from recognizing any changes to this setting unless you restart Live or restart a Set.

Hi Timur,

Please be careful in your statements, as we'd have to communicate before coming to conclusion. For instance, in our experience, and in the experience of many other users, plugin buffer size has the expected effect, in Live 6. I'll read the corresponding thread again now, and try to come with a meaningful answer.

Regards,
Amaury

funny enough I just read this and it reminded me abou thte plug-in buffers and I set it to double the audio driver (1024 - the audio is 512) and now my CPU meter is hovering around 54% - still seems stupidly high for a project with one track and one Tension, but it's way better than it was here:
http://www.ableton.com/forum/viewtopic. ... 190#602190

[Amaury]

Try changing your "Plugin Buffer" settings in Live 7. I noticed that in Live 6.10 it does not seem to have any effect at all aka seems to be fixed. Maybe your settings in Live 7 are giving you the bad performance (like it's too high or too low). The default setting is "As Audio Buffers", try using something else. Unfortunately there seems to be a bug in 7.01 that will keep Latency Compensation from recognizing any changes to this setting unless you restart Live or restart a Set.

Hi Timur,

Please be careful in your statements, as we'd have to communicate before coming to conclusion. For instance, in our experience, and in the experience of many other users, plugin buffer size has the expected effect, in Live 6. I'll read the corresponding thread again now, and try to come with a meaningful answer.

Regards,
Amaury

funny enough I just read this and it reminded me abou thte plug-in buffers and I set it to double the audio driver (1024 - the audio is 512) and now my CPU meter is hovering around 54% - still seems stupidly high for a project with one track and one Tension, but it's way better than it was here:
http://www.ableton.com/forum/viewtopic. ... 190#602190

Hi,

As in the beta forum, it's much easier to keep a problem per thread, for clarity. I'm saying this, because the problem described in that thread comes from a problem with a plugin, that allocates an infinite number of voice with a super long envelope, which of course would drain any CPU.

If you experience other issues, or find solutions for a problem, or make investigation that you think make sense, please keep it in one place! (just so that it is not forgotten, and doesn't freak out other users)

Kind regards,
Amaury

[Timur]

Hi Timur,

Please be careful in your statements, as we'd have to communicate before coming to conclusion. For instance, in our experience, and in the experience of many other users, plugin buffer size has the expected effect, in Live 6. I'll read the corresponding thread again now, and try to come with a meaningful answer.

Regards,
Amaury

Sorry Amaury, but when thinking about "What could make Simmo's Live 6 perform different to his Live 7 when opening the very same project" this was one of the differences that I recognized when it comes to using external plugins. I very well understood that using an infinite number of voices was the source of the CPU drain, but obviously his Live 6 installation is well capable of handling that drain, so there still seems to be something at odd.

Concerning the different experiences concerning Live 6's Plugin Buffers you are absolutely correct, that is why usually I write "seems to", "may", "could" etc... My tests with Plugin Buffers in Live 6 where somewhat restricted to testing audible performance with external Plugin, I did not check for CPU load at all, but obviously Live behaves audible worse (jerky playback, failing compensation) with higher buffer settings than Live 6 (where no difference is heard at all). This lead me to believe that Buffers don't make a difference in 6, but maybe they do and just work better than in 7. I will gladly discuss this in detail with you and already offered to send you audio-files to demonstrate the issues. But that's not part of this thread anyway. The possibility that changing Plugin Buffers may solve Simmo's issue on the other hand is part of this thread.

[Amaury]

Hi Timur,

Please be careful in your statements, as we'd have to communicate before coming to conclusion. For instance, in our experience, and in the experience of many other users, plugin buffer size has the expected effect, in Live 6. I'll read the corresponding thread again now, and try to come with a meaningful answer.

Regards,
Amaury

Sorry Amaury, but when thinking about "What could make Simmo's Live 6 perform different to his Live 7 when opening the very same project" this was one of the differences that I recognized when it comes to using external plugins. I very well understood that using an infinite number of voices was the source of the CPU drain, but obviously his Live 6 installation is well capable of handling that drain, so there still seems to be something at odd.

Concerning the different experiences concerning Live 6's Plugin Buffers you are absolutely correct, that is why usually I write "seems to", "may", "could" etc... My tests with Plugin Buffers in Live 6 where somewhat restricted to testing audible performance with external Plugin, I did not check for CPU load at all, but obviously Live behaves audible worse (jerky playback, failing compensation) with higher buffer settings than Live 6 (where no difference is heard at all). This lead me to believe that Buffers don't make a difference in 6, but maybe they do and just work better than in 7. I will gladly discuss this in detail with you and already offered to send you audio-files to demonstrate the issues. But that's not part of this thread anyway. The possibility that changing Plugin Buffers may solve Simmo's issue on the other hand is part of this thread.

Thanks for trying to help, it's appreciated. But again, we did test the same set in Live 6 and Live 7, with the same plugin, and the problem is the same, in our experience.

Regards,
Amaury

[Shoden]

I Have big CPU spikes in 7.0.1 everytime the playtime of my track change, like when i click on the timeline (change on start quantization). The spikes nearly double the cpu usage, so it's a leak somewhere i guess, so if my project is at 40% i will have spikes at 90% or so witch on start witch is unacceptable.

this happens even if i only have one minimoog vstis open, with 20% normal cpu usage i get 50% peak on start (50% of a dual core for one vstis hehe)

Also i have the same spike on the start of song loop, so everytime my track reloop i have tons of crackle and pops

anybody have this kind of bug??

i decided to check and delete everything leaving just one empty midi track and i get a 13% cpu peak on play with nothing in the project, afterwards the cpu go back down to 0%. The problem is really those stupid peaks

I decided to save the project once empty, restart live 7 and reload the empty project, now the peak go to 4% on start, I wonder what is the difference between both. I believe something was leaking in memory and draning cpu in the background.

I decided to reimport from the live browser the important tracks that was enabled in my original project and no problem now I don't have spikes anymore, I will wait to see if they reappear and post the reason here if i find it.

Anybody with cracking because of spikes start with an empty project and reimport yours tracks to this one and resave it should work at least.

just hope those fuc... pops and crackle didnt break my dynaudio speakers

[ewistrand]

A denormal issue perhaps, Amaury? I noticed the first poster was using a Core2 Quad...

I'm seeing a lot of reports of CPU behavior like that with the Core2s and lots of hosts when using multiple plugins. And, Core2s might be even more sensitive to denormal issues than the original P4s were from what I've seen...

ew