Hey guys, I am workin in ableton live 9. I've been getting these serious cpu spikes over 100% and the audio playback often starts glitching when I re-play back the project multiple times within a short period(e.g. when I am composing). ALso, when I turn off ALL channels, eventhough I can not hear anything, I can still see the CPU spike to over 100%. I have tried everything talked about in the following thread:
Neither of those things worked. I ruled out my interface, it is not a latency issue because the DPC thing only showed green bars, I re-installed live, updated my bios, did bunch of other stuff that supposedly are supposed to optimize my pc for audio production, I defragged my HD, trying different buffer sizes in Asio4All, etc.. neither of those things worked.
Another thing I just noticed is the Asio4all icon in the bottom right toolbar turns red with a yellow exclamation sign on it when my audio starts to clip. Is it something with Asio that I can do?
My machine: i7, 8gb ram, 7200rpm HD
Please help! this really sucks
Last edited by iliveinmyguitar; 21-05-2014 at 04:17 AM..
Sorry I can't be very helpful here but I want to just add I've always had problems with ASIO's clipping and bad handling of audio, it's likely something in that respect - maybe something you can tweak? (ASIO-Heads, chime in)
I stopped using ASIO, it was recommended and came with Traktor, but always gave me problems and now I just use my laptop's Realtek or Traktor S2's built in.
I was going to suggest maybe there was too much automation going on, but with 8gb of ram that seems slightly out of the question
Can I add (ASIO?) to the thread title maybe? It might generate more specific advice.
This happens to me with ASIO all the time. Make sure your buffer is set right, and that you don't have 2 inputs or 2 outputs selected (or something similar). If all else fails, use direct sound or whatever you have for the time being
I have the same exact problems. I'll get CPU spikes in Live 9 even with one track. No IRQ conflicts or DPC latency problems on my end either. Not a fucking clue as to why this still happens. If you find a solution for this I would love to hear it.
My bad, I am using the Alesis iO2 Express. It actually uses the Asio4All driver since its a plug and play device. But I think I ruled it out because when I disconnect it and run ableton through the mobo sound the same issue occurs. Another thing I noticed is the project runs smoothly for the first few minutes but than it gets progressively worse to the point where its impossible to work. Oh and I am using PC
Last edited by iliveinmyguitar; 21-05-2014 at 09:58 PM..
I really don't want to switch to anything. I put alot of time into learning the ins and outs of ableton. I have good work flow in it. I meddled around with FL studio a while back which was cool but I liked ableton more.
Just because it's happening in Ableton didn't mean it's soundcard related. You could be having a slew of other pc related problems. Ram, cpu, mobo, psu and more can cause all kinds of crazy anomalies. Did this just start? Is it after an update? Give us any information you can about just before and right when it started happening. I like what another guy said about trying Reaper or another free trial of a daw to see if it happens in that one as well. For shits and giggles, if you're running a wireless network card, unplug/disable it. They're known to cause all kinds of issues and cpu spikes.
It gets glitchy the more complex the project becomes. But the strange thing is, at that point, if I freeze all the tracks, the glitching does not go away! And it comes and goes periodically. I could be working on the project for 1 minute without problem and then all of the sudden the CPU spikes over 100% and I get audio drop outs. There is no point of me trying out a different daw because I would first need to learn how to use it to get to a project of complexity where glitching occurs. Usually, waiting for the CPU to drop down to 0 before hitting play DOES NOT solve the issue either. I just dont know anymore lol
I might help to load up Task Manager and set the sorting to CPU and watch while Ableton plays your project to see if it's Ableton spiking.
Also, I noticed you said 'project' instead of 'projects' so is this issue only limited to one thing you're working on? If it's multiple projects where you are using a certain plugin, it's possible it could be that plugin causing it. Some third-party software doesn't jive with some daws.