|
Live is using 80% CPU idling? WTF
|
View this Thread in Original format
| MindsDesire |
So, I'm working on an uber project right now.. you know, the project that I'm going to win grammys on, and fly to the top of the club charts for six months straight.
Yeah, that one.
Anyways, all of the sudden, I notice that Live is using 80% CPU IDLE. This is idle. Nothing playing, nothing rendering, nothing crazy going on in the background. Just sitting. I've rebooted to check this, and it's just the same.
The SECOND I hit start on anything, even 1 measly track, my CPU jumps past 100% and its completely unplayable. It takes me a good 20 minutes to render a 5 minute track.
Here's a screenshot I took: http://mindsdesire.net/kai/liveidle.png
Notice that live is using 92% of my overall CPU power, also.
Any idea what could possibly be going on? I'm running a MacBook Pro, 1.83ghz, 1.5 gigs of quality RAM, and I've got about 5 gigs harddrive space free.
My other projects are just fine, and running normally. This one though, is the biggest project I've undertaken, and has plugins out the ASS all over the place, so it's no suprise that it takes a lot of CPU. But IDLE? I don't get it. |
|
|
| Fledz |
Have you got an insane amount of delay, reeverb etc on all of your VSTs that it just takes ages for them to die down. If you leave your mac on for 10min, is it still at 80% or does it slowly die down?
Maybe your release on some VSTs is set to max so they never die down? |
|
|
| Fledz |
Have you got an insane amount of delay, reeverb etc on all of your VSTs that it just takes ages for them to die down. If you leave your mac on for 10min, is it still at 80% or does it slowly die down?
Maybe your release on some VSTs is set to max so they never die down? |
|
|
| MindsDesire |
| That's not it, because when I close and reopen the program, it sits there at 80% soon as I load my project. |
|
|
| richg101 |
i had this problem recently.
have you recently installed any new vst's or anything else that works within your sequencer? i couldnt run one of my new projects. but i deleted a recent vst i had used in the project and it worked fine.... |
|
|
| MindsDesire |
| Absynth and FM8 by NI. Those are the only two I've added. I'll try adding them to another project and see if it does the same thing. If it's the VST, then it should lag up the other project also. |
|
|
| thecYrus |
| usually synths and effects process sound even while not playing... so nothing wrong with that.. |
|
|
| DigiNut |
Absynth is a CPU hog, I'm not sure about FM8, and as Cyrus pointed out, most plugins continue to operate whether they're receiving any MIDI data or not. Of course some plugins are smarter than this and will disable themselves when they're idle, which is why it jumps up when you actually start playing.
There are lots of ways to deal with CPU issues. Check the thread that's linked in the FAQ. |
|
|
| Low Profile |
| you have 4 or more instances of ambience running, right?? Ambience is an EVIL plugin, it's the worst CPU hog you'll ever find, so use another reverb plugin, lower the CPU usage inside the plugin (it's a knob in the plugin), or set up ambience as a send effect. That's most definately your problem :) |
|
|
| MindsDesire |
So, I was under the impression that Live shut off effects and generators if they weren't in use (AKA, idle). What you're saying is that regardless of if the generator is actually running, it's still going to take CPU like that?
And yeah, I usually solo my ambiance until I get it how I like it, then bounce it down and disable the original tracks.
I'll try freezing the FM8 and Absynth tracks and see if that improves performance at all. |
|
|
| MrJiveBoJingles |
| Turn off all the generators, effects, and synths manually (by pressing the circular "Power On / Off" button on each VST) and then see what the CPU usage is. That should determine whether you have a bigger problem. |
|
|
| MindsDesire |
I think I found it!
As you guys were saying, effects are always "on", that is, waiting for input to process.
I'm in the final parts of the song, which means EQ and effects processing, and I have laid over quite a few CPU-intensive effects processors over multiple channels. Turning those off saves me about 5% CPU each one. So it wasn't one single thing, it was just the addition of so much more in the final stages that caused it to start overloading like that.
And I bounced down the ambiance and froze about 10 tracks, that helped too.
Well, I guess the only question I have left then is, is it possible to assign multiple buttons to a single MIDI input? I'm talking about assigning the power buttons of multiple effects processors to a single button on my MIDI controller, so I can turn them all on and off at once. |
|
|
|
|
