Overworking your CPU can cause any or all of these problems, which mess up the flow of your session and halt creativity in its tracks. In this post, we\u2019ll talk about a few common tactics and best practices for reducing your CPU\u2019s workload and getting your sessions back to feeling snappy again.<\/p>\n\n\n\n
Buffer size is a measure of the length of time the computer has to perform a given set of operations. Put simply, a longer buffer size means the machine has more time to make the calculations asked of it by the DAW. If the computer has more time to work, the CPU can allocate less resources to performing that work. In practice, this means that a longer buffer size can alleviate common issues like clicks and pops during playback, audio dropouts, choppy audio, and aliasing.<\/p>\n\n\n\n
Unfortunately, a longer buffer size means more latency, which can be troublesome especially if you’re doing musical tasks that require precise timing (like live recording). If you can live with increased latency, bump up your buffer size and your CPU will be significantly less taxed. Generally, I try to keep my buffer size around 128 samples or less if possible when doing live recording, but I bump up the buffer size to 1024 or 2048 samples if I experience performance issues when mixing or mastering audio. For more information on buffer size, I recommend this excellent article on latency.<\/a><\/p>\n\n\n\n Your computer\u2019s internal temperature is directly related to its performance capabilities. If the computer gets too hot, it’ll slow down or even shut off to avoid damaging the fragile components inside. To combat this, computers have cooling fans which exhaust hot air from the machine. These fans need ventilation space in order to function; if your computer is squished up against a wall or tucked into a drawer, for example, consider placing it elsewhere so that the machine\u2019s fan can cool down the components so that your hardware works as efficiently as possible.<\/p>\n\n\n\n A session may slow down when it has multiple processing-intensive plugins running because the CPU must perform all the calculations requested of it by the plugins in a very short window of time. When you render your project\u2019s tracks to audio by freezing, flattening, or bouncing, you’re essentially allowing your CPU to perform any calculations your plugins request in advance so that your computer doesn\u2019t have to perform these calculations in order to play back your project. <\/p>\n\n\n\n Of course, bouncing means committing to the decisions you\u2019ve made. For example, if you render a MIDI track to audio, you won\u2019t be able to go back and change the MIDI pattern or tweak plugin parameters. That\u2019s why DAW developers built freezing functionalities; if you still want the option to be able to go back and make edits to the MIDI, you can always simply freeze the track and unfreeze it when you want to make edits.<\/p>\n\n\n\n Stop applying all of your mixing plugins in your original session \u2013 bounce out the stems of your track when it\u2019s ready for mixing and do your mix processing there. Rendering to audio will help you commit to the decisions you make, stay organized, and save your CPU from having to perform processing-intensive tasks. It\u2019s probably not a bad idea to do the same thing when mastering<\/a>, since mastering plugins can really take a toll on your CPU. Try bouncing a mix you\u2019re happy with, and then loading your pre-mastered mix into a separate project to perform mastering tasks.<\/p>\n\n\n\n Driving two displays costs more of your computer\u2019s processing power than using only one. If you have a second monitor and are using an external keyboard and mouse, try putting your laptop into closed-clamshell mode if you aren\u2019t actively using your second display. Since you won\u2019t be using resources to drive the extra display, your computer can devote more power to processing your audio instead.<\/p>\n\n\n\n Sometimes, HDD\/SSD read\/write operations can make your DAW run slow, especially when there’s little space remaining on the disk. A good rule of thumb is to keep at least 15% free space for mechanical drives and at least 25% free on solid-states, although some have called this too conservative. In my experience, leaving between 15 – 20% free on my SSD works just fine. If you\u2019re on a Mac and have an unnecessarily large sample library that you try to keep in a completely unorganized folder on your desktop (guilty), this is especially pertinent, as iCloud Drive will likely be constantly transferring files when it detects too little free space, eating up precious read\/write operations and bandwidth.<\/p>\n\n\n\n Hopefully these tips on conserving CPU resources help you experience a smoother session the next time you open up your DAW. Do you have any recommendations that we didn’t cover above? Let us know in the comments below.<\/p>\n\n\n\n Bring Splice directly into your DAW with the Sounds Plugin (beta):<\/p>\n\n\n\n
\n\n\n\n2. Ventilate<\/h2>\n\n\n\n
\n\n\n\n3. Freeze, flatten, or bounce your tracks<\/h2>\n\n\n\n
\n\n\n\n4. Bounce an entire mix session<\/h2>\n\n\n\n
\n\n\n\n5. Close your laptop (if using a second monitor)<\/h2>\n\n\n\n
\n\n\n\n6. Check your system drive space<\/h2>\n\n\n\n
\n\n\n\n