Dubstepforum.com

ABLETON EXPERTS I NEED HELP.

I have a project, and at one point in the song I go to a break that leads into a drop. AT THE BEGINNING of that drop the ENTIRE project freezes for like 0.3 seconds, and it just RUINS it. I had an issue similar to this before, but I thought that when I exported it fixed it. However, I exported this, and it's actually in the wav file I exported!

I then decided to move ALL THE TRACKS to a different area of the project(This had worked before), and when I did that it was STILL there in the same place.

What is causing this??? I checked my automation, and went through and deleted tracks and brought them back and I can't figure it out.

The weird thing is, when it freezes for that 0.3 seconds my CPU starts acting funny. It's at about %25-%30 in the intro, when it hits that break it spikes up to %70-%90 for 0.3 seconds and then goes down to %40-%50. My drums also get EXTREMELY loud(According to the levels meter, since I can't hear it at that moment, because I actually turn the Mixer->Speaker on/off to off).

If you can help me please do!

Weird.
What's your buffer size? Try bringing it up a little... 256 samples is in most of the cases a solid setting!

If you're automating a lot of stuff at the drop, the increased workload the VST instruments and effects are putting on your CPU is probably causing the CPU usage to spike and thus causing the audio to pause. Best advice I can give is to freeze some audio tracks (cannot remember whether Ableton has this function or not... think it does?) or bounce down individual tracks and see whether that frees up some CPU cycles to make things run smoothly again

Dub Fiend wrote:If you're automating a lot of stuff at the drop, the increased workload the VST instruments and effects are putting on your CPU is probably causing the CPU usage to spike and thus causing the audio to pause. Best advice I can give is to freeze some audio tracks (cannot remember whether Ableton has this function or not... think it does?) or bounce down individual tracks and see whether that frees up some CPU cycles to make things run smoothly again

I had a lot of automation, and I had frozen all the VSTs, but I also had automated the Master Track's volume.

Now, I went ahead and copied everything and put it in a new project and it worked just fine.

Literally had no issues, but when I went and re-did the automation in the master track there was still a tiny pause. I ended up copying EVERYTHING to a new project. Exporting with NO master track automation, and the putting the exported wav into another project, automating it, and then exporting that.

It all works out, but it's a hassle.

Best thing I can suggest to anyone who has this issue. Copy EVERYTHING to a new project!