To avoid disk overload take the steps listed in our dedicated article: Avoiding Disk Overload. This is more likely to occur if triggering multiple large audio files at once. In this case the Disk Overload (D symbol) indicator will flash. If the hard disk cannot read or write audio quickly enough, you may hear dropouts. Make sure to close all other programs and processes on your computer which might be using valuable CPU resources.
To reduce the CPU load in Live take the steps listed here: Reducing the CPU load in Live. When the CPU load on your computer is too high, you'll probably hear gaps, clicks or other audio problems in Live.
Older interfaces may not have drivers available for your current operating system.Make sure that the audio interface drivers and firmware are completely up to date.
Check our dedicated article on Driver Error Compensation. Reset Driver Error Compensationĭriver error compensation set to extreme amounts may cause audio issues. Note: Many ASIO audio interfaces only allow the buffer size to be changed via their own control panels. If there is no native ASIO driver available for your interface, you can use ASIO4ALL.For best performance we recommend using ASIO rather than MME/Direct X as the driver type.Note: Larger buffer sizes will also increase the audio latency. Reduce the In/Out sample rate to 44100 samples.
Find the sweet spot just above where the crackles and audio dropouts stop. However, if the buffer size is set too low, then crackles, static noise, pops or dropouts may occur. In computer based audio systems a certain amount of latency, known as audio buffering, is necessary to ensure that playback, recording and processing results in an error-free audio stream.
In this troubleshooting guide we'll cover the most common reasons for these audio issues and how to resolve them.
I have installed all the Pro App upgrades.If the CPU load is too high and audio can't be buffered within the chosen buffer rate, then crackles, dropouts (gaps in playback), or glitches may occur during playback. I'm using a MacPro quad 2.66 with 5GB RAM, OSX 10.4.9 Logic 7.2.3. Is it an intel bug? Can anyone shed any light? The really strange thing is that this problem never occurred on our old G4. Though in future I think I'll stick with IR-1. My system is now as happy as larry and has never even used 50% of it's cpu. To get around it, I created a short region of silence, looped it through the song and sent it to all of my space designer instances so they never became idle. The start/stop/skip method does not seem to solve this. Despite the fact that IR-1 is typically far more CPU intensive than space designer. If I switched the space designers to waves IR-1Ls the problem went away.
This occurred most frequently at the end of a song when they all tried to unload at once. Further examination revealed that these weird spikes were only occuring at the point in the song where the reverb in question was no longer in use, as though the spike was being caused by it attempting to unload itself. By going around the session an bypassing plugins till the problem went away I managed to trace the problem to an instance of space designer. My system will be playing back fine with CPU usage at around 25% then all of a sudden it will spike massively and more often than not I will get a core audio overload message. I'm suffering a similar problem to this but it isn't quite the same as it seems to be specifically related to the space designer.