BURNT HOUSE / CUBASE PRO 16 / SYSTEM PERFORMANCE
Nothing breaks a creative session faster than playback that crackles, drops out or stops responding when the arrangement becomes dense. A powerful computer helps, but a stable Cubase project also depends on how instruments, plug-ins, buffers and real-time processing are managed.
Understand the difference between latency and processing headroom
The audio buffer affects how much audio the system processes at a time. Smaller buffers can reduce monitoring latency when recording, but they leave less time for the computer to complete each processing cycle. Larger buffers generally provide more headroom for mixing and playback, at the cost of greater monitoring latency.
Choose settings for the task. When recording a live performance, use a buffer that keeps monitoring comfortable and stable. When editing or mixing a large project, a larger buffer may be more appropriate. There is no single setting that is ideal for every session.
What ASIO-Guard does
ASIO-Guard allows Cubase to pre-process certain audio paths ahead of playback, reducing the amount of work that must happen at the last moment. It can improve stability in projects with many tracks and plug-ins, but not every process can be treated in the same way. Live inputs and real-time monitored paths have different requirements.
Cubase 16 offers expanded ASIO-Guard buffer options. Test the settings with your own projects rather than assuming the highest option is always best. A setting that improves one session may not help another, particularly when external hardware or live monitoring is involved.
How to set ASIO-Guard in Cubase 16
- Open Cubase’s Settings dialog and select Audio > Advanced.
- Find the ASIO Guard control under Audio Processing. Choose a level rather than leaving it Off.
- Test a higher level when playback is struggling with a dense project. Higher ASIO-Guard levels can improve processing stability and playback headroom, but they also increase ASIO-Guard latency and memory use.
- Keep in mind that ASIO-Guard does not remove the real-time demands of live monitoring. When you monitor or record-enable certain inputs, MIDI or instrument channels, related processing may move from the pre-processed path to real-time processing.
Steinberg documents the control and its trade-offs in the Cubase Pro 16 Audio – Advanced reference.
Use the Audio Performance Monitor to find the bottleneck
Open Studio > Audio Performance Monitor while the project is playing. The panel shows separate processing loads for Real Time and ASIO Guard, along with peak load and detected dropouts. In the detailed dropout list, Cubase can identify the position and tracks involved and suggest operations such as opening the audio interface’s buffer control, adjusting ASIO-Guard or freezing a track.
If the real-time curve is the one reaching its limit, increasing ASIO-Guard may not solve the problem. Check live-monitored and record-enabled channels, then test the audio-interface buffer only when you are not depending on low-latency live monitoring. If ASIO-Guard is overloaded during playback, test a higher level and reduce the most demanding plug-in or instrument. Steinberg explains the readings and suggested operations in its Audio Performance Monitor documentation.
Find the actual bottleneck
When a project struggles, do not randomly disable half the session. Check the performance meters, identify heavy instruments and processors, and bypass one suspect at a time. Oversampling, linear-phase processing, convolution reverbs and complex virtual instruments can be demanding. A single processor can sometimes cause more trouble than dozens of simple channels.
Render or freeze parts that are finished
When an instrument part is musically settled, consider freezing or rendering it. Keep the MIDI and original instrument settings where practical so the sound can be revisited. Print effects when they are part of the sound design, but retain an unprocessed source if you may need to change the balance later.
Check plug-in and driver compatibility
Use the correct audio interface driver and keep firmware and software versions compatible. If a project becomes unstable after installing a new plug-in, test the session without it. Avoid changing several system settings at once, because that makes the cause difficult to identify.
Build a reliable workflow
- Use a lower buffer for low-latency recording where stable.
- Increase the buffer for demanding mixing sessions.
- Test ASIO-Guard settings with representative projects.
- Identify heavy plug-ins before freezing everything.
- Keep drivers and plug-ins current and compatible.
- Save versions before major system or project changes.
Further reading
Explore our Cubase setup guide and session workflow article.
Build a repeatable troubleshooting sequence
First save a new project version. Then note when the problem occurs: during recording, playback, opening a plug-in window or exporting. Check the audio interface connection and driver, then inspect Cubase’s performance meters. Bypass the most demanding recent plug-in or instrument and test again. If the issue disappears, re-enable devices one at a time until the cause is clearer. Change only one system variable per test and record the result.
Separate real-time monitoring from playback processing
Software monitoring, external hardware monitoring and virtual instruments can have different latency requirements. A low buffer may be essential for a performer hearing a live input through Cubase, while an already recorded audio track can often be played with a larger buffer. Disable unnecessary live monitoring paths when mixing, and avoid expecting ASIO-Guard to remove the latency of every live process.
Keep sessions portable and recoverable
Use project folders, consolidate audio where appropriate and keep a backup before updating Cubase, drivers or major plug-ins. When freezing or rendering an instrument, retain the MIDI, preset and routing information needed to recreate it. A stable session is not just one that plays without crackles; it is one that can be reopened, transferred and revised without losing essential decisions.
Do not treat every dropout as a CPU problem
Disk activity, a failing cable, interface clocking, driver conflicts, background tasks and plug-in compatibility can all contribute to instability. If the performance meter looks comfortable but audio still drops out, investigate the complete signal path. For recurring problems, note the exact project, buffer, driver version and steps that reproduce the fault before seeking technical support.
