When running a project, have Task Manager open and monitor the CPU/Memory and HD utilisation? If they aren't anywhere close to 100%, this will indicate an issue with the ASIO drivers at the very least, or just that particular version of Cubase. I don't recall if you said you had this issue with previous versions of Cubase. Changing the audio card USB cable and port also wouldn't be a bad test if the earlier steps are good.
If something is hitting 100% (CPU, HD or Memory - last is very unlikely as it would make use for virtual RAM), then you need to look at that hardware. If it's the CPU, re-seat it with new thermal paste, won't hurt.

 

On the ASIO Guard topic, have you tried not using ASIO Guard?

On the PCIe topic, What I meant to convey without getting too far into the weeds was, Most modern motherboards that don't used re-drivers/repeaters have available lanes shared between PCIe slots & SATA or NVMe slots. Some PCIe slots are set to disable NVMe or SATA slots when used rather than sharing. This is usually found in the web site specifications section for the motherboard.

PCIe slot 1 is usually X16 PCI lanes all the time unless you use the BIOS Bifurcate to divide it into two or four:
8 x or 4 x 4 x 4 x 4. 16 lanes total in either combination.

If you have another x16 slot, it is electrically either 8 or 16 PCIe lanes. Again in the specs. PCIe add-in cards can be used for extra NVMe SSDs in sets of two or four depending on the lanes available. You not only have the option to Bifucate/divide the slots lanes, you also have the option to create a RAID set for enhanced read/write speed. The simplest and safest for a novice is Bifurcation.

Hope that help explain what I meant!

Newegg search of compatible RAM for the X570 Taichi
https://www.newegg.com/tools/memory-finder?Category=AE&name=ASRock+X570+TAICHI&Manufactory=1003&Model=949375&ModelValue=600521523+100007611&N=600535716 600418367

 

Last edited: Jun 11, 2025

Thanks again for diving in!

As I mentioned earlier... Switch off ASIO Guard and BOOM! Straight into the red on performance - and that is before I even press "play".

In terms of the PCIe info, thanks for this. I'm going to have to read that several times to get my head around it, but I think I get the gist.

Got a little biz trip for the next few days, so will need to return to this next week. And will do the test you suggest, @CMAudioz.

Thanks to everyone again for all your help so far, it is GREATLY appreciated

 

I'd put money betting that if you completely excise Project Lasso (and any other 'real-time' 3rd party software that 'optimizes' your PC) from your computer, your computer's audio performance will improve dramatically.

EDIT: Or at least disable it (and any other real-time monitoring processes like antivirus) from being executed at startup for testing purposes.

 

Last edited: Jun 12, 2025

You ever tried livestreaming 32 tracks with Cubase fully loaded with plugins? Obviously not because it's impossible with the high latency. So keep quiet untill you actually know what you're actually talking about.

 

Just as well you didn't put money down... This was all happening BEFORE Project Lasso. Lasso actually improved things slightly. That said, I would prefer to have things work without lots of filler like Lasso. So still testing and will no doubt test stripping all manner of things back including Lasso.

 

Process Lasso for better DAW performance ?!

OK, here it is:

1. Launch NVIDIA Control Panel. Click on “Manage 3D settings” in the left hand panel.
2. Click the Program Settings tab.
3. Under “Select a program to customize:” enter the location of the Cubase10.exe (or whatever Cubase version you have) and click Add button.
4. Under “Specify the settings for this program:” scroll down to Power management mode, click on the current setting to get the dropdown menu, and then select “Prefer maximum performance”

To my understanding, what this does is keep the graphics card responding at highest performance so it doesn’t tie up CPU cores, leading to a latency problem. The setting is set whenever you start Cubase, and changed back to default when you close it.

I suppose it could be set under Global Settings, but since I don’t really know what the card is doing, I thought, best just leave it alone for everything else besides Cubase.

Somebody who is a gamer could probably explain it much better.

Source: https://forums.steinberg.net/t/process-lasso-for-better-daw-performance/890448/9

 

Hi there,
I struggle with a similar problem with Bandlab on Win7/64, tried different ways, but, so far, no good result
Today asked perplexity this:
What is IRQ in PC and how it can affect/improve the audio performance in Windows 7/64?
the answer:
https://www.perplexity.ai/search/what-is-irq-in-pc-and-how-it-c-vQ452tKYRl6qUIp5uIWcVg

Note, some tips there are perhaps dangerous for OS, so, I'll try a simple and safe tip: changing the video card slot on motherboard (now it has the same IRQ number with audio card, and this is not good as perplexity said)

 

Spoiler: Source: ChatGPT KI

IRQ (Interrupt Request) in a PC is a hardware signal sent to the processor to gain its attention. Devices like sound cards, keyboards, and network cards use IRQs to tell the CPU that they need processing time. Each device typically gets a unique IRQ number so the CPU can distinguish between different interrupt sources.

How IRQ Affects Audio Performance in Windows 7/64-bit

1. Real-Time Audio Processing:
   
   • Audio devices require low-latency communication with the CPU to process sound in real time.
     
     
   • If multiple devices share the same IRQ (a situation called IRQ sharing), it can lead to interrupt conflicts or delays, especially on older systems or poorly designed drivers.
     
2. Latency and Dropouts:
   
   • When the sound card's IRQ is delayed due to other devices using the same interrupt line, audio stuttering, clicks, or dropouts may occur.
     
     
   • This is especially problematic for professional audio applications (e.g., DAWs like Pro Tools or Ableton Live) that require stable and low-latency performance.
     
3. Improving Audio Performance:
   
   • Use dedicated IRQs for sound cards, especially for professional audio interfaces.
     
     
   • In BIOS, disable unused devices (like onboard audio, serial ports, etc.) to free IRQs.
     
     
   • Ensure that the sound card is placed in a PCI/PCIe slot that does not share IRQs with high-traffic devices (like USB controllers or GPUs).
     
     
   • Use tools like DPC Latency Checker or LatencyMon to analyze and troubleshoot interrupt-related latency issues.
     
     
   • Install the latest drivers and chipset updates, as well-written drivers can manage IRQ sharing more efficiently.
     

Summary
IRQ management is crucial for optimal audio performance. In Windows 7/64-bit, although IRQ handling has improved with ACPI and Plug-and-Play, issues can still arise, particularly with legacy drivers or when multiple high-demand devices share the same IRQ. Proper IRQ assignment and driver optimization can lead to significantly improved audio stability and lower latency.

 

As I see from your post perplexity done its job better than chatGPT, but it's necessary to log in there (use your facbook, Google or something), then enter my question as I did and you'll get several pages of information plus links to all the resources...and conclusion, of course

 

Quick question: Do you think ChatGPT and Perplexity are helpful in solving this problem or not?

 

"Quick question: Do you think ChatGPT and Perplexity are helpful in solving this problem or not?"
_________________________________________________________________________
Only God knows... I have already changed several PCs, a laptop with different versions of Windows and the problem is still relevant
look at this topic, especially the 1st post:
https://www.reddit.com/r/Reaper/comments/18nctwb/if_youre_buying_a_windows_laptop_for_music/

 

I read the article. I recently made music with Windows 7 myself. However, it's a self-built PC, not a laptop. I've never had any problems with it. I've used Asus or Gigabyte motherboards and PCI sound cards like the E-MU 1212M PCIe (PCIe Digital Audio System) or the Infrasonic Quartet - 4-Channel PCI Audio Interface. AMD - FX-8350 Processor - Boxed - Socket AM3 CPU!

 

Yup, that's fair enough. After posting, i had a quick web snoop and admittedly nobody seems to have problems with Lasso. I personally always try to keep all extraneous processes to an absolute minimum.

I would second @Haze 's suggestion to re-install the nvidia driver using the excellent (and free) NV clean install utility, which will enable you to establish that only the elements of the nvidia driver suite that you actually want get installed (i.e. the basic graphics driver) without the nvidia telemetry and other cruft you most certainly don't want or need. Once you've 'clean' installed the driver, go to your nvidia panel and ensure its power management setting there is set to "maximum performance. That is the single most important nvidia setting for stable DAW performance on a system with an nvidia card.

I had a look at the the X570 specs on the ASRock site and see that the motherboard has built-in WIFI, Blutooth, 7-channel sound and a LED controller (polychrome sync). Disable them all in BIOS, login and see if that improves things. If you need to use your PC to surf etc, use the Intel ethernet port instead of WIFI, or disable the WIFI in windows when using cubase.

On your win11, did you ever run anything like ShutUp10++ to disable the many dubious MS features that come enabled by default? Opinions vary, but i personally would be inclined to use win10 instead, less headaches overall.

If, having followed the substantially good advice given throughout this thread, you're still having performance issues, as a last resort i would suggest you beg/borrow/steal an AMD graphics card to switch out your 2080 card with.

EDIT: I also second @taskforce 's suggestion regarding memory. Test your PC with only two memory sicks in the motherboard's A2/B2 ram slots (a dual-channel setting) & see if that makes a difference. It very well might, 'cos tbh it's unclear whether the motherboard supports 128Gb with your memory sticks. I say this 'cos i looked through the X570 Taichi memory QVL page on the ASRock site and your memory config (CMW32GX4M4D3600C18 ?) is NOT listed. It looks like you would need not C18 but C16 memory sticks in a 128Gb set-up. This would explain why the memory speed has been capped by BIOS to 2667MHz.

 

Last edited: Jun 13, 2025

Spoiler: Source: Grok KI

Your system is robust and well-suited for professional audio production with Cubase 14 Pro, but you’re noticing performance issues or bottlenecks ("the brake") in your setup. Let’s analyze potential sources of performance loss based on your hardware, configuration, and typical DAW workflows, ensuring everything fits together cohesively. I’ll break this down systematically, addressing each component and potential issues, and then provide actionable recommendations.

System Overview

• OS: Windows 11 Home
• DAW: Cubase 14 Pro
• I/O: SSL 2+ (USB audio interface)
• CPU: AMD Ryzen 9 5950X (16 cores, 32 threads, 3.4GHz base, up to 4.9GHz boost)
• Motherboard: ASRock X570 Taichi
• GPU: NVIDIA GeForce RTX 2080Ti
• RAM: 128GB DDR4 (4x32GB Corsair Vengeance Pro, 2667MHz)
• Cooler: Be Quiet Dark Rock Pro 4
• Storage:
  • C Drive: Samsung SSD 980 PRO 1TB (NVMe)
  • Project Drive: Samsung SSD 850 PRO 128GB (SATA)
  • VST Drive: Samsung SSD 970 EVO 1TB (NVMe)

This is a high-end setup, with a powerful CPU, ample RAM, and fast storage. However, performance bottlenecks in DAW systems often stem from configuration, drivers, or specific component limitations rather than raw hardware specs. Let’s evaluate each area.

Potential Performance Bottlenecks
1. RAM Speed (2667MHz)

• Issue: Your RAM is running at 2667MHz, which is relatively slow for a Ryzen 9 5950X. Ryzen CPUs, especially 3rd-gen (Zen 3), benefit significantly from faster RAM due to their Infinity Fabric architecture. The sweet spot for Ryzen 5000 series is typically 3600MHz with low latency (e.g., CL16).
• Impact: Slower RAM can reduce CPU performance in memory-intensive tasks, such as loading large sample libraries or running multiple VST plugins. Cubase, especially with heavy projects, can be RAM-intensive.
• Evidence: You listed the RAM as "Corsair Vengeance PRO DDR4 360," but the speed is 2667MHz. This suggests the RAM is either underclocked or not running at its rated speed (3600MHz).
• Check: Verify if XMP (Extreme Memory Profile) is enabled in the BIOS to run the RAM at 3600MHz. Use CPU-Z to confirm current RAM speed.
• Recommendation:
  • Enter BIOS and enable XMP to set RAM to 3600MHz.
  • If the RAM is not rated for 3600MHz, consider upgrading to 3600MHz CL16 DDR4 (e.g., G.Skill Ripjaws V or Corsair Vengeance LPX).
  • Ensure RAM is installed in dual-channel configuration (slots A2 and B2 on the ASRock X570 Taichi for optimal performance).

2. Project Drive (Samsung SSD 850 PRO 128GB)

• Issue: The 128GB SATA SSD for projects is small and slower compared to your NVMe drives (980 PRO and 970 EVO). While the 850 PRO is reliable, its read/write speeds (~550MB/s) are significantly slower than NVMe drives (~3500MB/s for 970 EVO, ~7000MB/s for 980 PRO).
• Impact: Small project drive size can lead to storage constraints, especially with large audio projects or sample libraries. SATA speeds may cause delays when loading or saving large projects, particularly if you’re working with high-resolution audio (e.g., 96kHz/24-bit).
• Evidence: 128GB is very limited for modern DAW projects, especially if you’re storing multitrack recordings, samples, or backups. If the drive is near capacity, performance can degrade further due to reduced free space.
• Recommendation:
  • Move projects to the 980 PRO (C Drive) or 970 EVO (VST Drive), which have faster NVMe speeds and more capacity.
  • Consider upgrading the project drive to a larger NVMe SSD (e.g., Samsung 990 PRO 2TB) for better performance and storage.
  • Keep at least 20% free space on the 850 PRO if you continue using it to avoid performance degradation.

3. USB Audio Interface (SSL 2+)

• Issue: The SSL 2+ is a solid USB 2.0 audio interface, but USB 2.0 has lower bandwidth (480Mbps) compared to USB 3.0 or Thunderbolt. If the USB port or drivers are not optimized, you may experience latency, audio dropouts, or glitches, especially at low buffer sizes (e.g., 64 or 128 samples).
• Impact: High CPU usage or USB bus contention (e.g., sharing bandwidth with other devices) can cause performance issues in real-time audio processing.
• Evidence: You didn’t specify latency issues, but audio dropouts or high CPU spikes during playback/recording are common signs of USB-related bottlenecks.
• Check: Ensure the SSL 2+ is connected to a USB 2.0 or 3.0 port directly on the motherboard (avoid front-panel ports or USB hubs). Check for updated SSL 2+ drivers and firmware.
• Recommendation:
  • Update SSL 2+ drivers from the Solid State Logic website.
  • In Cubase, set buffer size to 256 or 512 samples for stability (adjust lower for recording if latency is acceptable).
  • Disable USB power management in Windows:
    • Go to Device Manager > Universal Serial Bus controllers > Right-click USB Root Hub > Properties > Power Management > Uncheck “Allow the computer to turn off this device.”
  • If issues persist, consider a USB 3.0 or Thunderbolt interface (e.g., Universal Audio Apollo) for lower latency and higher bandwidth.

4. CPU Performance and Cooling

• Issue: The Ryzen 9 5950X is a powerhouse, but DAWs like Cubase are sensitive to single-threaded performance and core management. The Be Quiet Dark Rock Pro 4 is a good air cooler, but under heavy loads (e.g., multiple VSTs, high track counts), thermal throttling could occur if cooling is insufficient.
• Impact: Thermal throttling reduces CPU clock speeds, causing performance drops. Cubase’s ASIO load spikes can also occur if core affinity or power settings are not optimized.
• Evidence: You haven’t mentioned overheating, but check CPU temperatures using HWMonitor during heavy Cubase sessions. Sustained temps above 85°C could indicate cooling issues.
• Check:
  • Use HWMonitor to monitor CPU temps (aim for <80°C under load).
  • Check Windows power plan (set to High Performance).
  • In Cubase, enable “ASIO Guard” and set to “High” for better core distribution.
• Recommendation:
  • Ensure proper airflow in your case and reapply thermal paste if temps are high.
  • In BIOS, enable Precision Boost Overdrive (PBO) for better CPU performance, but monitor temps.
  • In Cubase, go to Studio > Audio System > ASIO Driver Setup and ensure “Multi Processing” is enabled.
  • If thermal issues persist, consider a high-end AIO liquid cooler (e.g., NZXT Kraken X63).

5. Windows 11 Optimization

• Issue: Windows 11 Home may have background processes or settings that interfere with real-time audio processing. Features like Game Mode, Xbox Game Bar, or telemetry can consume CPU resources.
• Impact: Background processes can cause audio dropouts or high ASIO load in Cubase.
• Recommendation:
  • Disable unnecessary startup programs:
    • Task Manager > Startup > Disable non-essential apps.
  • Turn off Windows features:
    • Settings > Gaming > Turn off Xbox Game Bar and Game Mode.
  • Optimize power settings:
    • Control Panel > Power Options > Select “High Performance.”
  • Disable Windows Defender real-time scanning for Cubase and VST folders:
    • Settings > Update & Security > Windows Security > Virus & Threat Protection > Manage Settings > Add exclusions for Cubase.exe and VST drive.
  • Update Windows and all drivers (chipset, GPU, etc.) from the ASRock and AMD websites.

6. VST and Plugin Performance

• Issue: Some VST plugins are poorly optimized or CPU-intensive, especially if they’re older or rely heavily on single-threaded performance.
• Impact: Heavy plugins (e.g., Serum, Kontakt with large libraries) can spike CPU usage, causing dropouts or lag.
• Check: In Cubase, monitor the ASIO meter (F12 > Audio Performance). Identify plugins causing spikes by disabling them one by one.
• Recommendation:
  • Freeze or render tracks with heavy VSTs to reduce CPU load (Cubase: Render in Place).
  • Ensure VSTs are updated to their latest versions.
  • Use the 970 EVO for sample-based VSTs (e.g., Kontakt, Omnisphere) to leverage NVMe speeds.
  • If using Kontakt, enable “Memory Server” in settings for large libraries.

7. Storage Configuration

• Issue: While your C Drive (980 PRO) and VST Drive (970 EVO) are fast NVMe drives, the 128GB 850 PRO project drive is a weak link due to its size and SATA interface.
• Impact: Slow or full drives can cause project load/save delays or errors in Cubase.
• Recommendation:
  • Consolidate projects and VSTs onto the 970 EVO or 980 PRO for faster access.
  • Back up projects to an external drive to free up space on the 850 PRO.
  • Regularly defragment the 850 PRO (if it’s heavily used) using Windows Disk Defragmenter (NVMe drives don’t need defragmentation).

8. Cubase 14 Pro Settings

• Issue: Cubase’s default settings may not be optimized for your high-end system, especially for low-latency or high-track-count projects.
• Impact: Incorrect buffer sizes, ASIO Guard settings, or disk preload settings can cause performance issues.
• Recommendation:
  • In Cubase, go to Studio > Audio System:
    • Set buffer size to 256–512 samples for mixing, 64–128 for recording (adjust based on latency needs).
    • Enable ASIO Guard and set to “High.”
  • Increase disk preload time for sample-based VSTs:
    • Studio > VST Audio System > Disk Preload > Set to 2–5 seconds.
  • Save projects with “Minimize Audio Files” to reduce disk usage.

Does It All Fit Together?
Your hardware is well-coordinated for a professional DAW setup, but the RAM speed (2667MHz) and the small/slow project drive (850 PRO 128GB) are potential weak links. The SSL 2+ is adequate but may struggle with very low-latency tasks due to USB 2.0 limitations. Windows 11 and Cubase settings also need optimization to fully leverage your CPU and RAM.

Summary of Key Bottlenecks

1. RAM Speed: 2667MHz is slow for Ryzen 9 5950X; aim for 3600MHz via XMP or upgrade.
2. Project Drive: 128GB SATA SSD is small and slow; move projects to NVMe drives.
3. USB Audio Interface: SSL 2+ may have latency issues; optimize drivers and USB ports.
4. Windows/Cubase Settings: Background processes and unoptimized DAW settings can cause dropouts.

Action Plan

1. Immediate Fixes:
   • Enable XMP in BIOS for 3600MHz RAM.
   • Move projects to the 970 EVO or 980 PRO.
   • Update SSL 2+ drivers and optimize USB settings.
   • Disable Windows background processes and optimize power settings.
   • Adjust Cubase buffer size and ASIO Guard.
2. Monitoring:
   • Use HWMonitor to check CPU temps and RAM speed.
   • Monitor Cubase ASIO meter for plugin-related spikes.
3. Upgrades (if needed):
   • Upgrade project drive to a 2TB NVMe SSD (e.g., Samsung 990 PRO).
   • Consider a USB 3.0/Thunderbolt interface for lower latency.
   • If RAM isn’t rated for 3600MHz, upgrade to 3600MHz CL16 DDR4.

Additional Notes

• No Chart Needed: Your query didn’t explicitly request a chart, so I’ve avoided generating one per the guidelines.
• Web/X Search: I didn’t need to search the web or X for this response, as your hardware specs and typical DAW performance issues are well-covered by my knowledge.
• Symptoms Clarification: If you can share specific symptoms (e.g., audio dropouts, high ASIO load, slow project loading), I can refine the diagnosis further.

If you have more details about the performance issues or want me to focus on a specific aspect (e.g., latency, plugin performance), let me know!

 

Studio drivers and game ready drivers are actually the same - the difference is that the studio drivers aren't updated as regularly and are considered the last truly "stable" release. The studio drivers still contain the junk, it's just not as up to date junk. I see no mention in your responses that you have reinstalled the drivers using NVCleanstall, nor tried the hidden power plan settings. Seriously, try these, they are 100% potential fixes, not guaranteed of course but don't ignore them.

Then I must simply be imagining that my three PCs with Cubase and NVIDIA cards are all running with no issues, plus all the other PCs I've set up for others with exactly the same combination. It's true that it's not always necessarily a simple task to configure but it doesn't mean it can't be done. I, in fact, have literally just fixed someone's system three weeks ago that was having latency problems due to graphics related issues (very much aggravated by MPC software). That system is a Cubase/NVIDIA combination. The glitches have now been banished.

These are usually at the top of the list, even on a well optimised system. It's the actual reported latency of them that matters. If they're reporting 0.0x whatever then they're fine - Close to or above 1 then you've got serious issues (DPC will fail at this point).

That seriously stinks of a memory leak...

 

Spoiler: Source: ChatGPT KI

For your ASRock X570 Taichi motherboard and the 128GB Corsair Vengeance PRO DDR4 3600MHz (4 x 32GB) RAM kit, you should make specific BIOS/UEFI adjustments to ensure system stability and optimal performance. Here's a breakdown of what settings you should configure:

✅ 1. Update BIOS

• Why: Older BIOS versions may not support 128GB at 3600MHz well.
  
  
• How: Visit the ASRock X570 Taichi support page, download the latest BIOS, and update via BIOS flash utility (Instant Flash).
  

✅ 2. Enable XMP Profile

• BIOS Path: OC Tweaker > Load XMP Setting
  
  
• Action: Select the XMP profile for DDR4-3600 (usually 3600MHz, CL18 or CL16 depending on kit).
  
  
• Why: This applies the correct speed, timings, and voltage for your RAM.
  

⚠️ Note: 4 sticks of 32GB DDR4 (128GB total) at 3600MHz can stress the memory controller. Some systems may default to 2666–3200MHz for stability.

✅ 3. Manually Tune Memory (If XMP is unstable)
If XMP causes instability (e.g. system won't boot or crashes):

• Set speed to DDR4-3200 or DDR4-3466 instead of 3600.
  
  
• Set timings manually (e.g., 16-18-18-36 or 18-22-22-42 depending on kit).
  
  
• Set DRAM voltage to 1.35V.
  
  
• Increase SOC Voltage to 1.05V – 1.10V (found in OC Tweaker > Voltage Configuration).
  

✅ 4. Infinity Fabric Settings
For Ryzen processors:

• FCLK (Infinity Fabric Clock) should ideally match half of the memory speed.
  
  • For DDR4-3600 → FCLK = 1800MHz
    
    
  • For DDR4-3200 → FCLK = 1600MHz
    
• BIOS Path: OC Tweaker > Infinity Fabric Frequency
  

If you see instability:

• Drop FCLK to 1600MHz and memory to 3200MHz (safest combo for 128GB).
  

✅ 5. Gear Down Mode & Command Rate

• Try Gear Down Mode: Enabled and Command Rate: 2T if encountering instability.
  
  
• BIOS Path: OC Tweaker > DRAM Timing Configuration
  

✅ 6. SOC and VDDG Voltages (Fine-tuning)

• SOC Voltage: 1.05V–1.10V
  
  
• VDDG CCD/IOD Voltage: 0.95V–1.00V
  These help with memory controller stability under high capacity and speed.
  

Optional: Run Stability Tests
Once booted:

• Use MemTest86 or HCI MemTest in Windows to test RAM.
  
  
• Use Prime95 (blend test) or AIDA64 Stress Test for system-wide stability.
  

Summary of Safe Stable Settings for 128GB:
Setting Value
Memory Frequency DDR4-3200 or DDR4-3600 (if stable)
DRAM Voltage 1.35V
XMP Profile Enabled
SOC Voltage 1.05–1.10V
FCLK (Infinity Fabric) 1600–1800 MHz
Gear Down Mode Enabled
Command Rate 2T

 

IF crashes, something is not right.
Use https://www.ocbase.com/ to test the RAM/CPU.
Sometimes reseating the CPU and RAM solves the problem.
Sometimes clearing the CMOS helps too.

Verify if the motherboard BIOS is updated
https://www.asrock.com/mb/AMD/X570 Taichi/index.asp#BIOS
and use the latest chipset driver from
https://www.amd.com/en/support/downloads/drivers.html/chipsets/am4/x570.html

Also look at https://www.kvraudio.com/forum/viewtopic.php?t=621326

 

just wanted to chime in with my experience but keep in mind that due to your specific components, software and configurations.... ymmv!

let me preface this by stating that i use my pc as a music production as well as gaming and entertainment. as far as optimizing for digital audio, it can get really deep but at some point you will have diminishing returns.

my pc specs:
3700x
b450 mb
2070 super
16 bg 3000mhz
nvme ssd (primary) sata ssd (secondary)
studio one 7

while most vst's and vsti's are well optimized for low cpu usage, i find that there are some that will quickly max out my pc. more specifically, some arturia analog lab presets will get my audio to start crackling while at a 128 buffer (or lower). as a work around... studio one has a feature called low latency monitoring that allows you to keep the buffer really high but also has a toggle to reduce latency for the specific track you're working with. so worst case scenario, i can use a lower demanding preset with the low latency toggled "On" to record the midi with minimal input delay, then disable it to browse through all of the presets with the higher buffer to avoid crackling and audio dropouts. lastly, i freeze the instrument track to offload the cpu usage. this workflow allows my older "mid-range?" pc to punch well above its weight class. so while this works well with vsti's for vst's i utilize busses to reduce plugin redundancy. i typically dont max out my cpu with vst's but i have run into limits when i get to the master bus. especially when i don't freeze my instrument tracks. some vsts are pretty cpu hungry but in many cases you can simply turn off oversampling (or low quality setting) while making adjustments and just turn it back on when you export. some vst plugins allow you to set it separately for real-time processing and export. studio one also has plugin nap which disables vsts when there not being used. you are also able to see how much cpu each plugins is using. worst case scenario, I've had to export my track as 32bit float 48khz (native sample rate) with no master fx and master the stereo track in a new session.

with that being said... i do have many instruments and plugins that don't require me to use that work-flow but i prefer to not be limited and don't mind using those workarounds. i will also say that i've recently tried cubase 14 and found that it's considerably less CPU-efficient compared to studio one. i also found that the track freeze option also locked the track which prohibits you from copying and pasting an 8 bar loop (rendering the track was a viable alternative). the last straw was when i was just changing the preset on a vst and everytime i changed the preset the audio would cut out. overall it was disappointing because i really like the step sequencer , drum machine and sampler. i'm not here to bash cubase or promote studio one but you may have better luck with studio one.

in regards to expectations. some plugins are hogs. you can always upgrade to the latest and greatest but im not certain how much performance gains cpu and ram are gaining year over and year and how well optimized these plugins will be for said advancements. me personally, ive set the max processor state to 99% (power plan setting) which reduces my cpu performance by about 10-15% in exchange for lower temps and quieter fans. I also use 48khz instead of 44.1khz which furter reduces cpu performance by roughly 10%. i know if i upgraded my cpu/ram/mb i can get a nice performance boost but idk if it would double or triple? regardless, it would only be a matter of time before i figure out how to max that out and have to use workarounds

one benefit of having said limitations for me is that i have to commit when printing to audio and also be very purposeful in which vsts i use or dont use. less is more?

sorry for going off track. i recently had to do a fresh install of windows looked into a bunch of optimizations. i started to get pretty deep into it but at some point i was uncertain if it was helping or not. i will share the specific things that made the most impact for me.

1. bios version - avoid the beta releases. i was using an old bios and updating it did give me a nice performance boost. but ive read that updating can also have the opposite effect so i would consider it a last resort because of the risk of bricking your motherboard. also i wasn't able to find any info regarding the different bios versions in regards to digital audio workstation performance so its a bit of a crap-shoot.

2. nvcp low latency mode - in nvcp i set the exe for studio one to have low latency mode enabled. accoding to latency mon, this reduced my systems latency considerably.

3. close unnecessary apps. i use gpu tweak to under clock my gpu and disable 0db fan, its set to launch on windows startup. i f i don't x out of it i get random audio dropouts and high latency spikes according to latency mon. there are other apps that have similar effects on realtime audio.

those mentioned are in addition to whats already been mentioned and recommended in the guides that were linked. although i personally didnt follow those guides entirely, i just messed with the settings until it was "dialed-in" to low latency and no random dropouts.

 

Recently there was Ableton benchmark thread, so in my case with newer base model I could run same stuff on much lower buffer without clicks, while having more CPU headroom (my M1 performs slightly better then OP's Intel, but it's few percent more CPU headroom, better GUI responsiveness, but we get clicks on the same same spots and buffer). I have no clue how things are in AMD world, but if they are close to what is there for M's, you should be able to get enough of an upgrade from 9700X. If you expect more then 50% gain in performance (x0.5), you will be probably disappointed. What you will probably get is no clicks on that same patches and possibility for even lower buffer, if you cherish that, it's nifty upgrade.