Audio drop out on audio production machine (Cubase, Focusrite)

Judoludo

Member
Joined
May 19, 2015
Posts
5
Hi there everyone. I have an Audio PC, using Cubase for music production with a Focusrite Scarlett 6i6 1st gen. I have occasional drop outs when playing tracks inside Cubase, but also when watching videos on VLC o listening to audio in Windows.

abc. self built desktop:


  • Asus Prime X470-Pro
  • AMD Ryzen 5 2600X
  • Arctic Freezer 33 eSports One
  • Corsair Vengeance LPX 2 x 8 GB 3200 MHz (CMK16GX4M2B3200C16 - installed on correct slots, as read on Asus mobo manual, for Dual Channel - but running at 2132...)
  • WD Black NVMe 250 GB (OS, software and VSTi's plugins)
  • Crucial MX500 500 GB (Cubase projects and libraries for VSTi's)
  • Seagate Barracuda 500 GB (normal storage, no audio stuff)
  • Sapphire Nitro RX480 4 GB
  • Sharkoon SilentStorm Icewind Black 550W
  • Sharkoon TG5

def. Windows 10 LTSC x64 (v. 1809, build 17763.1)

gh. nope, it's a self built machine with clean install

ijk. built between Nov '18 and Jan '19, fresh install

lmnop. already answered

q. disabled

r. no security software running. actually, I disabled Windows Firewall too, but I'm not able to disable its service.

s. nope

t. nope

u. nope, only disabled core parking and been on Excellent Performances (power settings)



I made a Windows Performance Recorder test with Cubase running and playing VSTi's, waited for the drop out to occur, then stopped the test and saved the WPR file. I check it in Windows Performance Analyzer, but not been able to understand anything... I could provide that test, I think it would be useful to understand my issue. The only problem is, it's around 3 GB, but I can upload it to Drive and post it here.

Thanks for everyone would help me, thanks a lot.

JL
 
Hi Judoludo,

Please try the attached script to capture a trace while the problem is happening. It needs to be run with administrator privileges. The resulting etl file should be around 260MB and they actually compress nicely so I'd suggest creating a zip to upload like you did before. The trace happens in memory and shouldn't grow beyond 260MB and will contain the last 30 to 40 seconds of trace information when stopped.

The trace you already provided doesn't show anything that stands out as a problem so I'm guessing it wasn't recorded while the problem was occurring.

View attachment TraceCPU.zip
 
Hi Judoludo,

Please try the attached script to capture a trace while the problem is happening. It needs to be run with administrator privileges. The resulting etl file should be around 260MB and they actually compress nicely so I'd suggest creating a zip to upload like you did before. The trace happens in memory and shouldn't grow beyond 260MB and will contain the last 30 to 40 seconds of trace information when stopped.

The trace you already provided doesn't show anything that stands out as a problem so I'm guessing it wasn't recorded while the problem was occurring.

View attachment 43335

hi there, thanks for replying. here I made the test as you said.

I played something with Cubase, waiting for the drop out to occur. When it happened, I waited some seconds and then stopped the test. So, it happened on the last few seconds of the record.

https://mega.nz/#!KQwwASRT!f2ouQ3glAPu13xPZIx-K7Gd6_kdHf3eNnk49ZRT8OCQ

let me know, thanks!!!
 
I did a short test with LatencyMon too, and here are the results:

Screenshot (17).jpg
 

Attachments

  • Screenshot (17).jpg
    Screenshot (17).jpg
    244.2 KB · Views: 5

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top