Reducing the CPU load
- Live Versions: All
- Operating System: All
Excessive CPU load in Live can lead to dropouts, crackles or glitches in the audio, and/or a sluggish response in Live. Follow these tips to help reduce the CPU load as much as possible.
In Live 11, the improved CPU meter now displays the current (total) CPU usage as well as the average CPU usage.
The CPU meter in Live 10 displays the amount of the CPU currently processing audio, rather than the overall CPU load. To get an accurate reading of the current CPU load overall, open Activity Monitor (Mac) or Task Manager (Win).
- Optimize Live's Audio and CPU Preferences
- Optimize CPU-Intensive Devices
- Optimize Audio file settings
- Optimize system resources
- Reduce CPU throttling
- Upgrade your computer components
1. Lower the Sample Rate
Open Live's Preferences → Audio. Lower sample rates help lower CPU usage. Try setting it to a value of 44100 or 48000 Hz. Ideally, you should pick the correct setting before starting a new project, rather than changing it while working on an existing one.
2. Increase the Buffer Size
Ideally to a value by the power of 2, e.g. 128, 256, 512 or 1024. Keep in mind that higher buffer sizes can cause higher latency.
3. Disable unused inputs and outputs
Open "Input Config" and "Output Config". You can also disable the mono input pair of the same stereo input, or vice versa, depending on which is being used.
Follow these suggestions to optimize the CPU handling of your devices and plug-ins:
3. Freeze or resample tracks containing CPU-intensive devices
Freezing tracks creates a temporary render of the audio and then deactivates all the devices. Right-click a track and choose "Freeze Track". Right-click again and choose "Flatten" if you want to flatten the track to audio.
Resampling a track records it to another track as audio. Then you can deactivate the devices or delete the original track.
4. Put CPU-intensive effects into Return tracks
This allows you process more than one track with the same effect.
5. Reduce polyphony
Reduce polyphony of your devices, plug-ins and multisample instruments. The less voices currently in use, the less CPU is used.
6. Turn off the Spread function
Some Live devices have a Spread parameter (e.g. Corpus, Operator, Sampler). When Spread is used, two detuned voices are generated per note, this doubles the processing requirement.
7. Set the Reverb to "Eco" mode
This controls the tradeoff between reverb quality and computer performance. Eco uses minimal CPU resources, while high delivers the richest reverberation.
8. Turn off Filters, LFOs and Effects
Turn off any unused parameters in devices.
9. Use the standard filter circuit
All of the Cytomic filter circuits (OSR, MS2, SMP, PRD) use slightly more CPU.
10. Disable warping in Simpler
Or use a warping algorithm other than Complex or Complex Pro.
1. De-activate Hi-Q mode on audio clips
This setting improves the Sample Rate conversion when transposing audio files, at the cost of higher CPU drain. The Hi-Q button can be toggled from within the Sample Box.
2. Use Complex and Complex Pro warping sparingly
Use different warping algorithms or turn off warping completely where possible. Otherwise consider freezing the track, or consolidating/resampling those clips.
Other processes on your computer can reduce the amount of CPU available for Live.
1. Close other programs
Check the Activity Monitor (Mac) by pressing [cmd][space] and typing "activity monitor" into Spotlight, or Task Manager (Win) by right-clicking your task bar to see if other applications might be consuming much CPU and/or RAM on your machine, then close them.
2. Deactivate Wi-Fi, Bluetooth and the Webcam
Using these in conjunction with Live can take up more CPU.
3. Disk Management
Check the hard-drive of your machine to see if you have sufficient space available. As a rule of thumb, you should always have 10% of your hard drive's capacity available as free space.
4. Prevent Windows from turning off USB devices
Windows automatically turns off USB ports if it thinks that they aren't being used. USB audio interfaces always need to be on, and this may cause CPU spikes in Live unless this function is disabled. See how to prevent Windows from turning off USB devices.
Certain settings or ways of using your computer can throttle (reduce the maximum capability) of your CPU.
1. Always keep your laptop plugged in
When a laptop is unplugged, the CPU may be throttled when using CPU intensive programs like Live.
2. Choose the High Performance plan (Windows only)
Windows has a number of defined plans, some of which are more CPU efficient than others. However, the High Performance plan is recommended when using CPU-intensive programs like Live.
3. Check the battery life
Old and inefficient laptop batteries can throttle CPU resources. Replace them when necessary.
4. Clean your fans and vents
If fans and vents are full of dust or lint, they need to spin harder and longer to keep the computer cool. This results in thermal throttling, as the system's resources are increasingly reduced the hotter the computer gets. We recommend to get your computer's fans and vents cleaned once a year by a qualified professional.
5. Make sure your computer is well ventilated
Make sure there is an adequate flow of cool air around your computer. Don't place it on a couch, cushion or fabric surface which could block the vents. If using your computer in a hot room, you could use an external fan or AC unit to cool it further.
Live's capabilities are only as powerful as your system. While the minimum system requirements give the absolute minimum specifications needed to run Live, ideally you'll want to get the most powerful computer that you can afford. Despite this, even the most powerful systems can still run into CPU issues depending on their usage.
If you're not able to upgrade your computer outright, you may find considerable improvements simply upgrading individual components. Although in some computers it's impossible to upgrade components, if your computer allows it try upgrading the CPU, upgrading the hard drive to an SSD (Solid state drive) or adding more RAM.