@Aef you’ve been given awesome advice throughout this thread. I won’t cover what’s already been said. I’d like to help you fix your current issue as I sincerely believe your current machine is good enough to do what you need to do.
Let’s try a few things that I haven’t seen mentioned. First off, I come to you as a builder of my own PC’s that also still has every working build from win 98 to present. I’ve only lost one PC to lightning but have all my others in perfect working order. So my point is, I’m not going to sit here and waste your time. I actually have a clue about system handling and resources.
First, I’d like you to bring up task manager. Though windows 7 through 10 have optimized the ability to run more tasks, more often than not, audio dropouts, clicks, stutters, pops and garbled audio can result from numerous running applications and resources that should not auto start upon a boot. Now keep in mind, some processes are system specific and may need to run based on hardware or software configurations. However, you can simply test one process at a time to see if it indeed needs to run. Well get to that in a second.
So, running processes. Anything in the 60+ should probably be looked at. This is one of the main reasons to build your own system. You say what gets installed/runs and what doesn’t. But, you can still do that now by simply shutting things down for both windows and running software that auto starts. I can give you so many different things that aren’t usually needed that will claim more power, it would make your head spin.
Stuff like audio driver control panels, NVIDIA driver helper, auto start behind the scenes programs, remote access, start up items placed in “start up”, windows scheduler, some virus protection, (which is another reason to build an audio box and never put it on the net) and anything else that can take away from the priority of audio recording.
I use msconfig as well as task manager to look up things that are runnimg. Type them in search bar online, and see if it is something that needs to auto run or can be manually run when needed. Audio apps like iTunes, Pandora etc can all wreak a little havoc on some systems. If you’d really like to dive in deep with this, you can always visit www.blackviper.com which is a complete tweak site for any OS. He walks you through everything. What it is, if it’s needed, how it works etc. It’s how I learned how to tweak all my machines, and why I think they all still work today.
So, out of all the above, see how many processes you have running for starters. You can really gain improvements this way. This is where I would start and I’ll tell you why.
I’m a beta tester for Bandlab Cakewalk, Celemony Melodyne, FXPansion/BFD Drums and Fractal Audio. I’ve done just about all my testing on a stock Dell Inspiron running an i3 and 4 gig of RAM. I am not even using an interface on that PC and it’s been flawless with everything I’ve thrown at it. I run Cakewalk Sonar and Reaper as my DAWs on that machine.
57 running processes, and I’m doing what another poster suggested (sorry on my phone and don’t have time to scroll through to see who it was) ASIO4ALL on a Realtek stock sound interface built into the mobo. I do this purposely to test using the least amount of power so that we can analyze things for limitation purposes.
On this PC using the above configuration, I am able to record and monitor at 64 and 128 buffers with no audio degradation (depending on tracks and processing already there) and simply raise back up to 2048 buffers for mixing. I would suggest trying this as the other poster mentioned. This will tell you if it’s your interface or drivers, which I don’t believe to be the case. Saffire pro’s are pretty darned decent. But you never know. Some interfaces just don’t get along with certain situations. I had a few like that, MAudio being one that was just terrible and an older RME. The RME 800 by the way, is pretty awesome. I have one of them as well in another machine. My weapons of choice have been my UAD Apollo, an old Echo Audio Layla 24/96 and my Midas M32, which is built into the console.
With that in mind, it is my belief that the number of resources/processes, the interface or a bit of both may be the culprits here.
One other thing. Not accusing or anything, but if you are using any cracked plugins, these can wreak absolute havoc on some systems. I had a friend who ran so many cracks, his box didn’t perform well at all. We reformatted and never put them back on and he’s been fine. Removing plugs you don’t use is also super helpful.
Last thing which you may be doing already. I have been an advocate of multiple drives and have been using them since Win 98SE. One for OS, plugs and programs, one for nothing but audio, one for nothing but samples. It’s worked flawless for me. I don’t have any SSD drives on my main recording boxes as I don’t feel the need with my good systems. 7200 rpm and loads of gig’s of space is more important to me than the speed that wasn’t super noticeable to me. (I do have a system that has one) That’s just my take as I process stuff in real time, run loads of synths, plugs, tracks and never get audio dropouts or issues. When a windows box is tweaked right, it will hang with and can exceed a mac. The issue there, is controlling the bloatware, which macs are starting to have now also. I won’t even get into the mac issues we’ve had just so we wouldn’t turn down business for those people that MUST use pro tools. Ugh!
Best of luck with everything. If you need me for anything, reply here or message me.
-Danny