Fully uninstall ASIO4ALL.
Fully uninstall Scarlett drivers
Reboot
Install latest Scarlett drivers (whether you had them or not.
Configure your audio recording apps to use Scarlett ASIO drivers.
Do not install ASIO4ALL - do not use!
Further issues download and use latencymon to diagnose.

Thanks I'll try it

Oh one last thing, make sure Windows update is fully up to date if you are using windows 7 and use the latest display adapter drivers you have (because we've heard of unrelated issues with earlier drivers esp with Nvidia drivers).

You should have a nice working base to diagnose any further issues by this stage. Then use latencymon.

Nothing changed, I'll check out latencymon

Is ASIO4ALL fully uninstalled? (Not just disabled).
Check device manager and disable any HDMI audio devices you don't need.
So yeah latencymon drivers tab, order by dpc.

Cheees.

So I installed it on an older hard drive that was set up with cubase and it works great. I'm thinking it's some sort of windows update or installation problem. I'll try and reinstall Windows and everything but I'm just happy it works on one of my hard disks

PreAl wroteFully uninstall ASIO4ALL.

Do not install ASIO4ALL - do not use!

I'm curious as to why you are so 'anti' ASIO4ALL. When I was on Windows it was the only way I could get any decent audio performance (although that was with a built in audio interface).

Sorry to hijack the thread

jpsbuk wrote

PreAl wroteFully uninstall ASIO4ALL.

Do not install ASIO4ALL - do not use!

I'm curious as to why you are so 'anti' ASIO4ALL. When I was on Windows it was the only way I could get any decent audio performance (although that was with a built in audio interface).

Sorry to hijack the thread

ASIO4ALL is maybe something to try if you don't have a proper audio interface with ASIO drivers, ie if you just have a sound chipset (although WASAPI with Windows 10 seems far superior in this scenario if you are compatible). The clue is in the name...ASIO4ALL. It's just a WDM wrapper regardless and no way is it going to be better than ASIO drivers supplied with the interface, which avoid the hardware abstraction layer, that is unless they are really poorly written ASIO drivers.

ASIO4ALL is well known for causing conflicts with other ASIO drivers. Another driver that can cause similar issues is the generic ASIO driver supplied with cubase which should also be removed if installed (Google for details, that's something the OP should also try).

The OP has a Focusrite interface and that comes with its own ASIO drivers, the Focusrite drivers is what he should be using.. and they should be good well written low level ASIO drivers. Removal of other drivers that are unneeded (such as ASIO4ALL) simply reduces the possibility of conflicts and resource hogging.

If you think you think you are getting better performance than your audio interfaces native ASIO drivers, then you are probably having some other underlying issue or just have poorly written ASIO drivers (or your other driver's are simply conflicting with ASIO4ALL). Without going into a whole new thread it's difficult to tell.

No way anyway Focusrite would recommend using ASIO4ALL regardless in the OPs case. Milage may vary in other cases.

Re-installing Windows is very drastic and I would advise against it at this point. It will rarely fix an audio issue. DPC latency checker and LatencyMon are very important. Please run these programs as they will indicate resources being used elsewhere. It can often be just one thing as well that will do it. They will tell how you how well your system is running for audio production.

Yeah I'd go for latencymon and get rid of cubase generic ASIO drivers.

Periodically (around once a year) I run DISM and SFC (Win7 uses the system update ready tool instead). Another thing I periodically do is uninstall and reinstall .NET library components, there's also an integrity tool to do it if you Google. All this keeps windows integrity in check.

https://support.microsoft.com/en-gb/hel ... -readiness

Only time I ever reinstall windows if it's a complete mess (or too many useless applications have been installed).

Good point, and it's such a pain doing all the windows updates again. I'll try the latency checkers and post the results

https://www.sweetwater.com/sweetcare/ar ... windows-7/

Adjusted these settings, unlocked all my CPU cores via bios, took off cool n quite. Turned on overclocking, set sample block size to 64

If I have just the Kemper rig manager and studio one open it seems to be fine now.

Not sure how to run the program but;

Latency Mon by itself maxed at 100 microseconds

Latency Mon with 4 guitar tracks going and peaked at 3000 microseconds.



Is my PC just outdated?

kylebarrett1 wroteIs my PC just outdated?

Sure is. It's Passmark score of 4068 is way below bare-minimum for a modern DAW. As a point of reference, the i5-8400 (a strong middle-weight contender) has a score of 11642...

https://www.cpubenchmark.net/compare/AM ... /255vs3097

I bought my current system after having similar troubles as you with an AMD that had an even higher benchmark than yours. My current system hums along great. Been mixing a 20-ish audio track each song album with it this month and it has not even broken a sweat using some pretty CPU-heavy plugins.

A word of warning too.... if you turned-off your cooling settings AND overclocked it you may dramatically shorten your CPU's life. If you absolutely must do that to get acceptable performance, just be aware of that.

I would set the sample rate to 128.

Also Sweetwater is wrong, do not set to background services, this is a common myth. Studio One is an app and should get priority and audio interface drivers are not windows services.

Other thing to do is turn off hyperthreading in bios
Regardless please list your full specs in your signature

I didn't find anything about hyper threading in the bios. Changed the sample rate and my computer blue screened. Is there a better processor that is compatible with my board that would be worth trying?

kylebarrett1 wroteI didn't find anything about hyper threading in the bios. Changed the sample rate and my computer blue screened. Is there a better processor that is compatible with my board that would be worth trying?

It looks like you may have a few options for a decent upgrade... https://www.cpubenchmark.net/socketType.html#id11

AMD FX 8350 would be the fastest thats compatible. Would a benchmark of 8947 be fast enough to solve the problem?

I would say that's a waste of money to only get up to 9000 but if that's all the upgrade you can afford then it will be an improvement for sure.

You might want to read through this article. It's written by the folks at FL Studio but the general advice on choosing a processor and other performance tips apply to any DAW...

https://support.image-line.com/action/k ... se?ans=214