- Trash Cubase preferences... it rebuilds itself at the next start... just for safety.

Kontakt and Superior Drummer should have multicore processing disabled in standalone and plug-in mode because ASIO Guard wants to manage it. If the plug-in also has it enabled, there are often conflicts in ASIO Guard. Omnisphere, for example, should also have multicore disabled... and the libraries on a fast drive helps also.

or:
If you select Studio > VST Plug-in Manager and click Show VST Plug-in Information, you can deactivate the ASIO-Guard option for selected plug-ins eg. Kontakt and SD3... that´s the other way to check. realtime performance goes up and ASIO Guard down


And the thing with the temperature and bifurcation ON in the BIOS and all the other things are also helping bit by bit...

ps:
And of course, very important: in the device manager - USB controller - right-click on each individual object - properties - power management - (computer can turn off the device to save energy) remove all activations per hand...one by one ----- recommended by Steinberg

hope that helps...

cheers......

 

Last edited: Jun 15, 2025

I looked through articles from 15 years ago about setting up Windows XP for music and found that much of it is still relevant today, to confirm I searched for AI in Task Scheduler (just one item for example), it answered:

utilities and programs scheduled in Windows Task Scheduler can potentially cause audio dropouts in a Digital Audio Workstation (DAW) on both Windows 7 and Windows 10. Here’s why:

System Interruptions and Resource Contention

· When a scheduled task runs, it can momentarily consume CPU, disk, or other system resources. Even a brief spike in resource usage can disrupt the real-time processing required by a DAW, leading to audio dropouts, clicks, or pops.

· Some scheduled tasks may trigger background processes, updates, or scans that increase DPC (Deferred Procedure Call) latency, which is a common cause of audio dropouts in Windows systems

Driver and Service Interference

· Certain scheduled tasks may start or interact with drivers or system services. Poorly behaving drivers or services, especially those related to networking, USB devices, or storage, are known to cause DPC latency spikes and audio interruptions

· Tools like DPC Latency Checker and LatencyMon are often used to diagnose such issues, and users frequently find that disabling or rescheduling background tasks can reduce or eliminate dropouts

Examples and User Reports

· Users have reported audio dropouts coinciding with background activity, even when overall CPU usage appears low

· Scheduled tasks that refresh or change audio devices can also cause temporary loss of audio or device switching, impacting DAW operation.
PS Then I looked through Task Scheduler and saw there 12 items...do I need them at all? For example Google, Opera, Adobe Acrobat updates?

 

Quite true. Which is why optimization for a production machine especially running windows 10 or 11 (there is an order of magnitude more autonomous/extraneous junk running on these later winOS versions) is extremely important and not to be taken lightly.

Nope. Not at all. In fact here's a list of the stuff I normally nuke on new builds before installing any production ware. My production machines are never connected to the internet so keep that in mind if your machine needs to be connected for some reason.

 

Last edited: Jun 15, 2025

Opera can disable them, but they keep coming back; they're now forced updates from Opera.
Google and Adobe can disable them. There should be as few entries as possible in the startup program!

 

Hey folks, sorry for going dark... Lots of family stuff has been getting in the way of important stuff like music!

So, I'm still battling away - Having tried many of the suggestions here (thanks again to everyone for their contributions), I now have a new stability issue that sees all of my cores suddenly max out with Cubase at ~100% CPU.

I think I've reached my limit of understanding and expertise, so I'm considering hiring a third-party specialist to help resolve the issue.

Again, all suggestions most welcome!

Thanks.

 

I still maintain it would have been far more helpful for both the OP and those who wish to assist if there had been some fully disclosed demonstration of the issue, or screenshots of the mixconsole showing all tracks, and their inserts/sends including channel latency visible to eliminate all this guesswork everyone was doing. Just saying 17 vsts and 75 plugins means literally nothing if only the OP can see what is actually going on as it happens. I have little doubt that ultimately the source of the problem lies in user expectations rather than a fundamental failure of the software and hardware.

 

Spoiler: Source: ChatGPT KI

Hey! No worries at all — life has a way of reshuffling priorities, and family definitely comes first. Totally get it.
That said, your Cubase issue sounds frustrating, especially after putting in the time trying various fixes. A sudden spike to 100% CPU across all cores is definitely not normal, and it’s good that you're considering getting some expert help — though there may still be a few things worth double-checking before you go that route.

Here are a few targeted suggestions that might help narrow things down or fix the issue:

Diagnosis Checklist Before Hiring Help
1. ASIO Guard / Audio Interface Driver

• Make sure your audio interface drivers are up to date.
  
  
• Try disabling ASIO Guard temporarily (Devices > Device Setup > VST Audio System) — sometimes it causes issues depending on plugins used.

2. Plugin Culprits

• Try running your project in Safe Mode (hold down Ctrl+Shift+Alt while launching Cubase) and disable third-party plugins.
  
  
• You could also freeze or disable tracks one at a time to see if a specific plugin is spiking the CPU.

3. Multi-Core Setup

• Check if Cubase is properly utilizing multi-core support (Studio > Studio Setup > VST Audio System).
  
  
• Try toggling Steinberg Audio Power Scheme on/off — some systems behave differently with it.

4. Buffer Size

• Increase the audio buffer size in your audio interface settings — low buffer = high CPU, especially in bigger projects.

5. Background Processes

• Use Task Manager to check for other CPU-hungry apps or Windows background services (e.g., indexing, updates).

‍ When to Bring in a Pro
If:

• You've tried everything and the issue persists across multiple projects,
  
  
• Or Cubase is unusable even with minimal setups,

Then hiring a specialist might save you time and headaches. Look for someone experienced in DAW optimization, ideally with Windows/Cubase systems, as many DAW problems are often tied to system config quirks.

If you’d like, I can help you draft a quick checklist or info summary to send to a specialist so they can hit the ground running.

Let me know!

Spoiler: Source: Grok KI

Your system is indeed robust, with high-end components like the AMD Ryzen 9 5950X, 128GB RAM, and fast SSDs, so it’s frustrating that you’re hitting performance bottlenecks in Cubase 14 Pro. The issues you describe—glitches, maxed-out performance meters, and crashes despite increasing buffer size—point to a combination of potential hardware configuration, software settings, and plugin-related problems rather than raw hardware limitations. Let’s break this down systematically and explore solutions based on your setup and the context from relevant discussions.

1. Potential Hardware Configuration Issues
Your hardware is powerful, but certain combinations or settings could be causing inefficiencies:

• CPU (AMD Ryzen 9 5950X):
  • The Ryzen 9 5950X is a 16-core, 32-thread beast, excellent for multi-threaded workloads like DAWs. However, Cubase’s performance meter spiking to 100% while Windows Task Manager shows low CPU usage (e.g., 15%) is a known issue with Ryzen CPUs. This suggests Cubase isn’t fully utilizing all cores or is being throttled by other factors like thread scheduling or DPC latency.
  • Possible Issue: Windows 11’s thread scheduling with Ryzen CPUs can sometimes misallocate tasks, especially with real-time audio processing. AMD’s chiplet design can introduce slight latency in certain scenarios, though this is less likely with a high-end CPU like the 5950X.
  • Solution:
    • Disable SMT (Simultaneous Multithreading): In your BIOS, try disabling SMT to reduce thread contention. Some users report improved real-time audio performance, though it may limit multi-core performance for non-audio tasks. Test this with a small project to compare.
    • Set CPU Affinity: In Windows Task Manager, set Cubase’s process affinity to use only physical cores (not hyper-threaded ones) to avoid scheduling issues. Right-click Cubase in Task Manager > Set Affinity > Uncheck half the threads (e.g., every other core).
    • Power Plan: Switch to the “Ultimate Performance” power plan in Windows. Run powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61 in Command Prompt (as admin), then select it in Control Panel > Power Options. This minimizes CPU throttling.
    • BIOS Settings: Ensure your BIOS is updated to the latest version for the ASRock X570 Taichi. Disable C-States (power-saving features) to maintain consistent CPU performance. Check for AMD-specific optimizations like Precision Boost Overdrive (PBO) and adjust if needed, though default settings are often fine for DAWs.
• Motherboard (ASRock X570 Taichi):
  • The X570 Taichi is a solid board, but some users report USB-related issues with X570 chipsets, which could affect your SSL 2+ interface. USB bandwidth contention or driver conflicts might contribute to audio dropouts.
  • Solution:
    • USB Port Check: Ensure the SSL 2+ is connected to a USB port directly on the motherboard (avoid front-panel ports or hubs). Use a USB 3.0 or 2.0 port, as some X570 boards have finicky USB 3.1 Gen2 ports.
    • Update Chipset Drivers: Download the latest AMD X570 chipset drivers from AMD’s website (not ASRock’s, as they may be outdated). This can resolve USB and interrupt-related issues.
    • Check USB Power Management: In Device Manager, go to Universal Serial Bus controllers, right-click each USB Root Hub, and disable “Allow the computer to turn off this device to save power.”
• GPU (NVIDIA GeForce RTX 2080Ti):
  • GPUs typically have minimal impact on DAW performance, but NVIDIA drivers can introduce DPC (Deferred Procedure Call) latency, which disrupts real-time audio processing.
  • Solution:
    • Clean Driver Install: Use Display Driver Uninstaller (DDU) in Safe Mode to remove all NVIDIA drivers, then install the latest NVIDIA Studio Driver (not Game Ready Driver) for your RTX 2080Ti. Studio Drivers are optimized for creative applications and reduce DPC latency.
    • MSI Mode: Enable Message Signaled Interrupts (MSI) for the GPU using MSI Utility (run as admin). Set the GPU’s interrupt priority to high to reduce latency spikes.
    • Disable GeForce Experience: Uninstall GeForce Experience, as it can add unnecessary background processes that increase latency.
    • OpenGL Triple Buffering: If you experience graphical glitches in Cubase, go to NVIDIA Control Panel > Manage 3D Settings > Add Cubase > Enable OpenGL Triple Buffering.
• RAM (128GB Corsair Vengeance Pro DDR4 3600):
  • 128GB at 2667MHz (likely downclocked from 3600MHz due to XMP or motherboard limitations) is overkill for most DAW workloads, but slow RAM speeds can bottleneck sample-heavy plugins like Kontakt or EastWest Opus.
  • Solution:
    • Enable XMP: In BIOS, enable XMP (Extreme Memory Profile) to run your RAM at 3600MHz. Verify the speed using CPU-Z. If it’s stuck at 2667MHz, ensure the RAM is properly seated and the BIOS supports the full speed.
    • Test RAM Integrity: Run MemTest86 to rule out faulty RAM modules, as errors can cause crashes.
    • Check Usage: Monitor RAM usage in Task Manager during a project. If it’s not maxing out, RAM isn’t the bottleneck.
• Storage (Samsung SSDs):
  • Your setup with separate C:, Project, and VST drives (all SSDs) is ideal, as it minimizes I/O bottlenecks. The Samsung 980 PRO and 970 EVO are fast NVMe drives, and the 850 PRO is a reliable SATA SSD. No issues here, but ensure projects and samples load from the fastest drives (980 PRO or 970 EVO).
  • Solution:
    • Verify Drive Health: Use Samsung Magician to check drive health and firmware updates.
    • Optimize Project Drive: Ensure your Cubase projects and VST sample libraries are on the 970 EVO (NVMe) rather than the 850 PRO (SATA), as NVMe has higher throughput for large sample libraries.
    • Defragment SSDs: SSDs don’t need traditional defragmentation, but ensure TRIM is enabled (run fsutil behavior query DisableDeleteNotify in Command Prompt; it should return 0).

2. Cubase and Software Settings
Cubase’s performance issues often stem from settings or plugin inefficiencies rather than hardware alone. Your use of Vienna Ensemble Pro (VEP) and AudioGridder is a good start, but their effectiveness depends on configuration.

• Buffer Size and ASIO Settings:
  • You’ve increased the buffer size, but glitches persist. A buffer size of 256 or 512 samples at 48kHz is typical, but some plugins (e.g., EastWest Opus, Kontakt) cause spikes even at higher buffers.
  • Solution:
    • ASIO Guard: In Cubase, enable ASIO Guard and set it to “High.” This pre-renders non-real-time tracks to reduce CPU load. However, disable it for tracks requiring live input to avoid latency.
    • Buffer Size Test: Try 1024 samples for playback/mixing to see if glitches stop. For recording, lower to 128 or 256 samples if latency is tolerable. Use your SSL 2+ control panel to adjust.
    • Steinberg Power Scheme: Enable Cubase’s power scheme in Studio > Studio Setup > Audio System to optimize CPU usage.
    • Multi-Processing: In Studio Setup, ensure “Activate Multi Processing” is enabled to leverage all 16 cores of your Ryzen 5950X.
• Vienna Ensemble Pro and AudioGridder:
  • AudioGridder hosting plugins externally (e.g., EastWest Opus) significantly reduces Cubase’s CPU load, as you’ve noted, but high server latency (e.g., 512 samples) can still cause issues.
  • Solution:
    • Optimize AudioGridder: In AudioGridder’s settings, lower the server latency (try 128 or 256 samples) and increase the buffer size on the hosting machine if needed. Ensure AudioGridder runs on the same PC to avoid network latency.
    • VEP Configuration: In VEP, set the instance to use multiple threads (e.g., 8–16 threads) and host CPU-intensive plugins like Opus or Kontakt. Save VEP projects on the 970 EVO for faster loading.
    • Plugin Load Balancing: Distribute plugins across multiple VEP instances to prevent any single instance from overloading a core.
• Plugin-Specific Issues:
  • Certain plugins, like EastWest Opus or Kontakt with specific libraries, are known to cause performance spikes in Cubase, especially with orchestral presets.
  • Solution:
    • Identify Problematic Plugins: In Cubase, disable plugins one by one to pinpoint which cause spikes. Common culprits include Kontakt, Opus, or any plugin with heavy sample streaming.
    • Update Plugins: Ensure all plugins are updated to their latest versions, as older versions may not be optimized for Windows 11 or Cubase 14.
    • Freeze Tracks: Freeze or render tracks with heavy plugins to reduce real-time processing. Use Cubase’s “Freeze” function or bounce to audio.
    • Kontakt Optimization: In Kontakt, enable “Background Loading” and increase the preload buffer size to reduce disk streaming demands.
• Cubase 14 Stability:
  • Cubase 14 has reported performance issues, with some users noting higher CPU usage and dropouts compared to Cubase 13, especially with VST3 plugins.
  • Solution:
    • Update Cubase: Ensure you’re on the latest Cubase 14 patch (e.g., 14.0.20 or newer). Check Steinberg’s website for updates, as some fixes address CPU spikes.
    • Test Cubase 13: If possible, test your project in Cubase 13 to confirm if the issue is version-specific. Some users report better stability in Cubase 12 or 13.
    • Check Crash Dumps: Look for crash dumps in %UserProfile%\Documents\Steinberg\CrashDumps\ and analyze them with WinDbgX to identify the cause (e.g., plugin or driver conflicts).

3. System-Wide Optimizations

• DPC Latency:
  • High DPC latency is a common cause of audio dropouts. Your Ryzen 9 5950X and X570 setup should be capable of low latency, but drivers or background processes can interfere.
  • Solution:
    • Run LatencyMon: Download LatencyMon and run it while using Cubase. Look for drivers with high execution times (e.g., nvlddmkm.sys for NVIDIA or dxgkrnl.sys for DirectX). If the kernel driver is spiking (as noted in some Ryzen setups), it may indicate a driver conflict.
    • Disable Unnecessary Devices: In Device Manager, disable Wi-Fi, Bluetooth, and unused network adapters to reduce interrupts.
    • Update Audio Drivers: Ensure the SSL 2+ drivers are the latest from Solid State Logic’s website. Test with ASIO4ALL as a fallback to rule out driver issues.
• Windows 11 Optimizations:
  • Windows 11’s new CPU architecture handling (e.g., P/E cores, though not applicable to Ryzen) and background processes can impact DAW performance.
  • Solution:
    • Disable Background Apps: In Settings > Apps > Apps & Features, disable unnecessary startup apps (e.g., OneDrive, Cortana).
    • Turn Off Game Mode: In Settings > Gaming, disable Game Mode and Xbox Game Bar, as they can prioritize GPU/CPU resources incorrectly.
    • Update Windows: Ensure Windows 11 is fully updated, as some patches improve Ryzen compatibility.
• Cooling and Thermal Throttling:
  • The Be Quiet Dark Rock Pro 4 is a great cooler, but heavy workloads can still cause thermal throttling if not configured properly.
  • Solution:
    • Monitor Temperatures: Use HWMonitor to check CPU/GPU temperatures during a Cubase session. Ensure CPU stays below 85°C. If throttling occurs, reapply thermal paste or improve case airflow.
    • Fan Curve: Adjust fan curves in BIOS or using Be Quiet’s software to ramp up cooling under load.

4. Project-Specific Tweaks

• Project Complexity:
  • Even a “relatively small” project with many plugins can overwhelm Cubase if they’re CPU-intensive. For example, 155 plugins across a project can push even a high-end system to its limits.
  • Solution:
    • Optimize Track Count: Disable unused tracks in Cubase to reduce CPU load. Use the “Deactivate” function for tracks not currently needed.
    • Reduce Sample Rate: If your project is at 96kHz, try dropping to 48kHz or 44.1kHz to reduce CPU and disk demands, especially for playback/mixing.
    • Check Markers: Excessive markers (e.g., thousands) can cause stuttering. Check your Marker Track and delete unnecessary markers.
• VST3 Bug: Some users report a VST3-related bug in Cubase causing performance issues, fixed in later updates (e.g., Cubase 10.5.10 for older versions). Ensure all plugins are VST3-compatible and updated.

5. Troubleshooting Steps
Here’s a step-by-step plan to diagnose and resolve your issue:

1. Run LatencyMon: Identify any high-latency drivers (e.g., NVIDIA, USB, or network). Address them by updating or disabling.
2. Update All Drivers: Chipset (AMD), GPU (NVIDIA Studio), audio (SSL 2+), and BIOS.
3. Test Buffer Sizes: In Cubase and SSL 2+ control panel, test 256, 512, and 1024 samples. Note when glitches occur.
4. Isolate Plugins: Disable all plugins in a project and re-enable one by one to find culprits.
5. Check ASIO Guard: Set to “High” for playback; disable for recording.
6. Monitor Resources: Use Task Manager and HWMonitor to watch CPU, RAM, and temperatures during a session.
7. Test AudioGridder/VEP: Host all heavy plugins in VEP with optimized settings (low latency, high threads).
8. Rollback Test: If possible, test the project in Cubase 13 to rule out version-specific issues.
9. Analyze Crashes: Check crash dumps in %UserProfile%\Documents\Steinberg\CrashDumps\ for clues.

6. Is It a Bad Hardware Combo?
Your CPU, motherboard, and GPU combo is not inherently problematic. The Ryzen 9 5950X outperforms many Intel CPUs in multi-threaded DAW tasks, and the X570 Taichi is a reliable board. The RTX 2080Ti is overkill for Cubase’s minimal GPU needs but can introduce latency if drivers are misconfigured. Your 128GB RAM and SSD setup are more than sufficient. The issue likely lies in software settings, plugin inefficiencies, or driver conflicts rather than a fundamentally bad hardware combo.

7. Next Steps if Issues Persist

• Contact Steinberg Support: Share your findings (e.g., LatencyMon results, crash dumps) with Steinberg. They may identify Cubase 14-specific bugs.
• Test Another DAW: As a diagnostic, try your project in Reaper or Studio One. If performance improves, it points to Cubase-specific issues.
• Consider Downgrading: If Cubase 14 remains unstable, revert to Cubase 12 or 13, which some users report as more stable.
• Hardware Upgrade (Last Resort):
  • CPU: Upgrading to a Ryzen 9 7950X or Threadripper is unlikely to help, as your 5950X is already top-tier for DAWs.
  • Audio Interface: The SSL 2+ is solid, but if USB issues persist, consider a PCIe-based interface like an RME Fireface for lower latency.

8. Summary
Your system should handle heavy workloads, so the issue is likely a combination of:

• Driver Latency: NVIDIA or USB drivers causing DPC spikes.
• Plugin Inefficiencies: Heavy plugins like Opus or Kontakt overloading Cubase’s VST host.
• Cubase 14 Bugs: Potential stability issues in the latest version.
• Suboptimal Settings: Buffer size, ASIO Guard, or Windows power management not optimized.

Start with the troubleshooting steps above, focusing on LatencyMon, driver updates, and plugin isolation. If you share specific details about the project (e.g., plugin list, track count, sample rate) or LatencyMon results, I can refine the advice further. Let me know how it goes!

 

Last edited: Jul 10, 2025 at 5:38 PM

Have you tried the suggestions in these five pages? One of the first suggestions was to try replicating the project on Reaper. Did you do that?

 

Yeah, i have a 5950x pc and abandoned it - its fast on paper but in reality its dog slow, its sitting doing nothing these days, i use an m2 air its much better

 

it's one of those things, on paper that CPU should handle it, but in reality it's another story, too many bottlenecks for audio, hardware and software wise, Cubase bottleneck on complex routings and that CPU bottleneck with so many cores, doubt he utilized 20% of his raw power in here before hitting all these.

 

Sounds like you might've tweaked yourself into a corner. I'd start from scratch, reinstall, revert to defaults. Then re-evaluate performance without tweaks and come back if problem persists. Better not apply tweaks unless 100% clear on what they actually do (not "internet forum says is good tweak"). Make sure to remember (or even write down) what I did when, where, to which components. Measure. If there's no actual difference, but something feels juuuust a little faster, revert the tweak - it's almost certainly not real. Placebo / expectation bias / apophenia / illusion of control, it happens to smart people too.

 

Again, lots of great info, thanks as always, folks! It is all very much appreciated.

So, let's cover a few things...

I was thinking the same... however...

I'm already on the same page... and talking of pages...

You'll be glad to know I have been ...in fact, since my last post I rolled back one tweak and fixed the 100% CPU overload. The tweak in question was the disabling of Hyperthreading in BIOS. Switched it back on, and the CPU overload has gone away.

This bit made me smile... my 'day job' for many years was essentially behavioural psychology in business, and the placebo effect was a part of that!

@dylan63819 - Yep, I've been going through as much as possible, but not all. Obviously, some suggestions were not going to be relevant because they didn't apply to my particular situation, I had already tried them, or were, as far as I could see, not particularly helpful. Rightly or wrongly, the Reaper suggestion is one I haven't followed through on... Maybe I'm missing something, and sorry if this seems blunt, but how will testing a particular project on a different DAW help me? I have seen these issues across multiple projects, and as a longtime user, I want to continue using Cubase, not Reaper. So, even if that project works better in Reaper, what have I learned about tuning my system for Cubase?

Following on from going through 'the five pages'...

Update on MemTest: I finally had a chance over the past few weeks and ran it for almost 10 hours, passing without a single error.

@PulseWave - You've shared lots of great info, thanks! ...I'm still working through some of the finer details.

@score - Thanks for this! I have Kontakt and EZdrummer (not Superior), but have now tested disabling ASIOguard on both. More consistent and stable performance, so again, THANK YOU!

@Semarus - I hear you. As a new user to the forum, I wasn't sure how much info was appropriate, so genuinely hadn't thought to do a series of large screenshots. After my next set of tests (as I mentioned earlier, I'm still going through some of the finer details of the posts from @PulseWave), and if my problems persist, I will share, share, share!

BUT... on the subject of 'user expectations', your comment seems to suggest I might be being unreasonable in said expectations.

Well...

I want to use Cubase in the way I see the 'Pros' do. I've watched a lot of Cubase videos from quality training sources (like Chris Selim and Dom Sigalas), and top producers/composers (like Hans Zimmer and JunkieXL) who use Cubase in ways that far surpass my needs

...and yet, I can't get a decent level of performance on a PC that is heavily spec'd (on paper).

That is frustrating, and that is why I am seeking a solution that I still believe can be found.

Again, thanks to everyone for all your help and suggestions. I may not always agree with you, but I appreciate your input very much.

 

Spoiler: Audio interfaces from Solid State Logic – SSL 2 and SSL 2+ in testing

Audio interfaces from Solid State Logic – SSL 2 and SSL 2+ in testing

Software-wise

The SSL interfaces work on Mac and PC. For Windows (Windows 7 and later), the manufacturer offers a driver package for download; no driver installation is required on Mac OS, as SSL relies on the system's integrated drivers for class-compliant devices. As usual, I tested the low-latency performance on both platforms using U-He's CPU-hungry DIVA soft synth (see "Latency Benchmarking" below). On Windows, I was able to play the maximum possible 16 DIVA voices without any dropouts, even with the smallest buffer setting of 16 samples. Cubase Pro 10.5 reported an output latency of 2.49 ms; the input latency was 1.859 ms.

The latter is only relevant if you want to edit audio signals in real time during recording, for example, when recording guitars with NI Guitar Rig. Input latency is irrelevant for processing MIDI signals, i.e., playing soft synths or sample instruments. I tested on a fairly powerful Windows 10 computer with an Intel Core i9 9900K 8-core CPU (3.6 GHz) and 64 GB RAM. Since the Cubase CPU meter seems quite twitchy, you'll probably need to select higher buffer settings for less powerful computers. With 64 samples, input and output latencies of 2.49 and 2.95 ms, respectively, are still very practical.

Latency Benchmarking
Manufacturers like to advertise ultra-short latencies. However, as a user, you don't just want to play audio files; you also want to work with DAW software and use plug-ins that require a certain amount of CPU load. Therefore, the crucial factor is the latency setting at which you can mix and play music without worry.

A practical CPU load can be reproducibly and precisely controlled with the power-hungry DIVA soft synth from U-He. To ensure consistent test conditions, I always use the same "BS Beauty Pad" preset in the particularly CPU-hungry "Divine" mode. For each latency setting, I test how many of the maximum 16 voices can be played back without audio dropouts. The latest version of Cubase serves as the test platform, in this case Cubase Pro 10.5. The specified latency values were determined at a sampling rate of 44.1 kHz. Higher sampling rates reduce latency but increase CPU load.

Source: www.soundandrecording.de/equipment/audio-interfaces-von-solid-state-logic-ssl-2-und-ssl-2-im-test/

Steinberg / Windows: How to set up and optimize a Digital Audio Workstation

Tweaking Cubase/Nuendo
In the Studio ▸ Studio Setup ▸ VST Audio System ▸ Advanced Options, there are some settings you can experiment with.

• ‘Processing precision’
  A processing precision of 64-bit float can increase CPU load and memory consumption.
• ‘Activate Multi Processing’
  Usually, having this selected is the preferred setting. But if performance issues arise, it is worth deactivating the multiprocessing support for a test.
• ‘Activate ASIO-Guard’
  As mentioned earlier, Cubase/Nuendo makes heavy use of real-time processing.
  The ASIO-Guard allows you to shift as much processing as possible from the ASIO real-time path to the ASIO-Guard processing path. This results in a more stable system.
  However, depending on the system, the project and the plug-ins used, it is worth a try deactivating it or selecting a different level.
  

Tweaking the computer
Modern systems with a fully updated Windows should not need any of the default settings to be modified. However, if certain drivers are not fully optimized and you experience audio drop-outs, it is worth having a closer look. Note that the following settings are often not accessible, especially on laptop systems.

• Disable Hyper-Threading (Intel)/Simultaneous Multi-Threading (AMD) in the UEFI BIOS if your CPU supports it and if your BIOS allows you to modify this setting.
• Disable advanced power-saving and dynamic performance options for your CPU if applicable. This usually needs to be done in the UEFI BIOS of your computer and includes ‘Enhanced Intel SpeedStep (EIST)’, ‘AMD Cool 'n' Quiet’, ‘Intel Turbo Boost’, and ‘AMD Turbo CORE’.
• Disable C-States in the UEFI BIOS if this is accessible. C-States allow your CPU to sleep when idle, which may interfere with real-time applications such as audio. This option is often called ‘Disable CPU Idle State for Power Saving’.

https://helpcenter.steinberg.de/hc/...t-up-and-optimize-a-Digital-Audio-Workstation

 

Last edited: Jul 11, 2025 at 12:38 PM

Did you ever execute the Dom Sigalas Cubase performance test to find out how Cubase is performing on your system? Also... I've read many times that Cubase does not like AMD Ryzen CPU's.

 

That's outdated.

 

Years ago i had a notebook that was a bit crappy. Some plugins on FL Studio would max out the cpu, while on Reaper they were much lighter. i don't even use Reaper, i was just trying to see if the problem is with Cubase, and not your hardware. For the gentlemen above who can't make music with their 5950x.. No, nothing.. I won't say anything..

 

If you mean the test he did comparing his old Intel system to an AMD one ...then, until today, no, I hadn't. So you just inspired that action, @Caldera! Thank you!

Now here's the crazy irony... It was watching that video back in 2021 that inspired me to invest in the 5950X because that was the CPU being tested! ...and given I was already a customer of the sponsor of that video, Scan Pro Audio, I actually bought all the components from them too.

However, until your post today (and subsequent googling), I didn't realise that Scan had made the benchmark test available to everyone.
I'd also forgotten that I got the components from Scan!

So I ran the benchmark test project and oh dear...

However, now that I recall how Scan was involved in the original inspiration and how Dom's benchmark was created with them, I've reached out to their support team and look forward to a call on Monday.

So thanks again, @Caldera ...it just goes to show the simplest of suggestions can lead to interesting results!

(BTW - if anyone is wondering why it's taken me four years to get to this point, it would be a fair question... let me just say, I have mental health issues which can steal a lot of time, years in fact.)

 

I don't understand.. The 5950x is a great cpu.. Why doesn't it work well with Cubase?

 

My point exactly!

But I might have some positive news to report soon, I think I might have started to see some light at the end of the tunnel.

 

I'm sure this was covered.. but I don't see it when keyword searching, so... What specific audio driver is currently the windows system driver. What audio driver is currently the cubase driver?