so ,

Might as well make a post about the obvious ,

Audio is processed 100% by your cpu. The only role your interface has is sending that audio to a DAC. Things tend to matter when you have 10+ physical ins and outs being used but usb 2 can handle that.

The issue is not the interface. A better interface will not allow you to run more plugins. More tracks that are summed internally to a stereo out will not add any more stress to your interface than 200. It is still 2 tracks as far as the interface is concerned.

Anyways. I think the way the OP responded is a pretty clear sign that he is a teenager and doesn't really understand what the issue is or how to solve it.

 

Using asio4all will provide a higher latency but your ability to use plugins has absolutely nothing to do with any interface. Audio in the box is 100% cpu . The interface just has drivers that provide better latency and well functionality / converters /

But this is a performance issue and sadly that is really not the interface you should be looking at.

 

Audio drivers haven't really changed in over a decade. Sound cards made 10 years ago perform as well. Usb2 performs as good / better than 3.

Do not take this the wrong way. I've been doing this professionally for 20+ years. You are angry and your lack of understanding is making you blame the issue on what is most likely an issue with your cpu.

You could just test with a virtual driver and rule out the computer but I suspect you don't understand what that even means.

Good luck. Try to be a little nicer to those that can help you

 

You mean that the audio isn't being processed by the interface converters but solely by the CPU? Please explain.

 

My vote is that this tread be closed as it will most like never see a resolution due to the OP.

 

just try diffrent versions of drivers
i have an scarlett 2i2 fist gen and installed the latest drivers on win 7 they run like crap
after that i installed a beta version and tose worked without any problems
im now on windows 10 with the latest drivers
and those work great on 10 but not on 7
so try diffrent versions

 

still, new info presented can be useful to other people

converters are precise number converters, that simply converts analog input to discrete bit value's and visa versa. the AD/DA sets the limit of number of in's and out's and the possible bit depth & sample rates.
The cpu is responsible delivering that audio stream to the buffer on a set interval.
If the cpu is too slow, the converter will convert blank spaces, which sounds horrific.

Edit:
Now I think about we are still leaving something out. In my expierence the Interface driver can have profound effect on the performance. the how and the why of that I don't know and can only guess, but in the past switching from an Edirol ua-25 to an rme device did influenced the performance a lot, back then these 2 devices had an 400 euro price difference & it was in the dual core - windows xp era

 

Last edited: Nov 19, 2021

It gets around very quickly on the Internet through reviews and tests who makes the best or worst drivers. If you produce poor quality as a manufacturer, you will not win any new customers and will disappear from the market in the long term.

Some companies read this very carefully and the deficiencies will be corrected in the next update. It's called service. There are also companies that stop their support. This is called customer unfriendly. So you as a customer have the power to support companies that do their job well and buy and not recommend companies that do their job badly.

 

The current thread has been tainted by the OP. I do agree however, that useful information could be gained from input by thoughtful posters & respondents. This of course could be done by adding to existing threads or creating a new thread focused on s specific layout of how audio is processed from software to final output as an example.

 

Your audio is 1 and 0s. This is all processed prior to having anything to do with your interface . The output of your DAW is then sent to your interface. Everything prior to that is done by your cpu. The interface is merely responsible for providing a stable buffer to smoothly receive and convert data to an electrical signal.

Use a virtual driver. You can see it in real time. The DAW will send the same output to a virtual bus. All the "audio " is processed without any interface because the interface only converts that output. Not before.

This is assuming you aren't tracking but merely summing audio and sending a stereo out to your monitors.

Your interface does not compute anything. It is all cpu.

 

If you are tracking , the interface will make a difference but in terms of anything to do with your DAW, how many effects , instruments ... That is all in the digital domain and has absolutely nothing to do with your interface.

The performance of your interface is seen when you are tracking at 192 using a low buffer. Poor performance is seen with higher buffers to avoid the crackles and dropped audio.

If you are in the box , the interface is just not even part of the process until your DAW has done the computation with your cpu and sends that to your interface. Its all cpu.

 

Thanks for your answer,

 

Exactly, the CPU is what handles the audio processing. It has been said already, so there it is... you can buy a 1000$ interface and still get problems because your CPU is slow/bad.