Operation Manual
CHAPTER 23. COMPUTER AUDIO RESOURCES AND STRATEGIES 320
23.1.2 CPU Load from Tracks and Devices
Generally, every track and device being used in Live incurs some amount of CPU load.
However, Live is smart and avoids wasting CPU cycles on tracks and devices that do not
contribute anything useful.
For example, dragging devices into a Live Set that is not running does not signicantly
increase the CPU load. The load increases only as you start playing clips or feed audio into
the effects. When there is no incoming audio, the effects are deactivated until they are
needed again. (If the effect produces a tail, like reverbs and delays, deactivation occurs
only after all calculations are complete.)
While this scheme is very effective at reducing the average CPU load of a Live Set, it cannot
reduce the peak load. To make sure your Live Set plays back continuously, even under
the most intense conditions, play back a clip in every track simultaneously, with all devices
enabled.
23.2 Managing the Disk Load
A hard drive's access speed (which is related to, but not the same thing as rotational speed)
can limit Live's performance. Most audio-optimized computers use 7200 RPM or faster
drives. Laptops, to save power, often use 5400 RPM or slower drives, which is why projects
on laptops usually have lower track counts. The amount of disk trafc Live generates is
roughly proportional to the number of audio channels being written or read simultaneously.
A track playing a stereo sample causes more disk trafc than a track playing a mono sample.
The Disk Overload
Indicator.
The Disk Overload indicator ashes when the disk was unable to read or write audio quickly
enough. When recording audio, this condition causes a gap in the recorded sample; when
playing back, you will hear dropouts.
Do the following to avoid disk overload: