Ok I'm a complete idiot regarding hardware.
I have the integrated audio card in my mini PC, and it's trash because sometimes the sound disappears and I have to reboot the whole PC, etc.
I was thinking I might want to buy an audio card or an interface. But why do I need an interface? I don't plan on recording anything (except a microphone). I don't care about latency, I just want to make sure everything works correctly and right now it is not: everytime I'm using the ASIO drivers it's like a time bomb, sooner or later the sound is going to disappear. It can happen in 5 minutes or 5 hours.

Do I buy an audio card? A cheap one possibly. I just need it for the DAW.

 

First you can try an asio driver like asio4all. It is free : https://www.asio4all.org/
And maybe your system will be better with it ?

 

What Is An Audio Interface and Do You Need It?

You shouldn’t let technology get in the way of your creativity, but at some point a certain amount of tech is necessary. The right gear can inspire you, speed up your work, and even guarantee what you hear is what everyone else hears. One of the first decisions you’ll come to when getting started in music production is how to get sound into and out of your computer. Let’s take a look at your options.

What does an Interface Do?

Audio interfaces convert microphone and instrument signals into a format your computer and software recognize. The interface also routes audio from your computer out to your headphones and studio monitors. Interfaces typically connect to your computer via USB cables, though some use Thunderbolt, Firewire, or even ethernet. Interfaces range in price from well under $100 to several thousand dollars, and even the most affordable interfaces sound great and provide the basic features.

www.mi.edu/in-the-know/do-you-need-audio-interface/

Audient iD4 MKII - 128 EUR
www.thomann.de/de/audient_id4_mkii.htm

Focusrite Scarlett Solo 3rd Gen - 104 EUR
www.thomann.de/de/focusrite_scarlett_solo_3rd_gen.htm

 

Well then I don't need an audio interface at all.
@zib That's what I use when I have FL Studio open, otherwise it's impossible to use

 

Really, you just need something with solid, low latency ASIO drivers (or works well with ASIO4ALL). If ASIO4ALL works for you, then great.. but if not, and ASIO drivers also suck, then you might need to explore a better sound device of some sort (although that might not be your only/real bottleneck).

I actually own an audio interface even though I'm almost 99% all in the box with VSTs, in my case... and that was just because of the ASIO drivers. But it isn't necessary, and I'm glad I actually bought an interface, because I sometimes use it on occasion for hooking my electric guitar in and farting around. But there isn't really a need for an audio INTERFACE, specifically, no. If you ever plan on buying some synthesizers or even low-end devices like a Korg Volca*, you'll want one then, but can always cross that bridge when needed.

Also, my PC is quite good, but if I tried to run some moderately high track-count stuff through my integrated sound it would very likely choke, but my interface would have no problems with it, due to the ASIO drivers.

 

Last edited: Mar 24, 2022

I'm assuming you mean asio4all? When say, you're using your daw, the desktop audio will stop working, and vice versa. That's just the way it works, the problem is sometimes depending on what you're doing it can be a little hard to get the driver to work as it was initialy. Maybe that's whats going on? Because there are solutions for that.

As for having an audio interface for no other reason than stability, the options BEAT gave are pretty good.

 

You definitely need an audio interface, the manufacturer's drivers and chip are much better than Asio4all Driver.
So don't let them tell you that Asio4All drivers are enough, that's nonsense.

 

Yes of course the desktop sound stops working, but what I'm referring to is: when I'm fooling around on my DAW, sometimes I get a very quiet "zip" sound and ALL SOUND stops working: be it DAW or desktop or porn. The only way to restore it is to TURN OFF the pc (not even rebooting as I wrote above) then turn it on again. It's starting to happen more often and I'm slightly worried.

I don't want and can't afford any equipment, nor I will ever need to hook up a guitar or synth, that's why I really don't want to spend 100 € for an audio interface.

(Yes, ASIO4ALL)

Thanks for all your answers

 

Tell me with what hardware and with what computer you make music? In other words how old is your hardware?
For us musicians it's always very hard to read what junk people want to make music with.

 

Then i should buy an focusrite scarlett 2i2
i have the 1st gen and the performance is good enough for basic users
you also need a decent cpu for low latency its not only the audiocard itself
what are your pc specs cpu ram etc

 

I agree. I tried Asio4all with my old Focus rite pro 40 and I get better latency with the Focus rite drivers.
They are codded better. This dos not mean ASIo4all is bad it just not as good for dedicated audio interfaces.

If you guys could help me I posted a audio comparison in hardware form Pro 40 versus Presonus Quantum 2626
test but no one responded to the post.

 

Give me the Link ?

 

I-Dio-Tech drivers are the best all for one solution!
They are free and for nothing!

 

asio4all is useless for audio interfaces, those generally got their own asio drivers. asio4all is only for onboard sound lacking asio drivers, its a better-than-nothing asio driver.
there are more free asio drivers, im not sure but doesnt fruity loops include one? steinberg has got one too, afaik. and look for the i-dio-tech drivers too! but there are more, imo

 

Last edited: Mar 24, 2022

https://audiosex.pro/threads/comparison-gen-1-pro-40-verus-quantum-2626-dry-guitar.63756/

 

FL Studio includes its own FL Studio ASIO driver, that supports multi-client (as in, you can play Youtube/Spotify/whatever while FL Studio is still open)

There's ways around this, but you need something that exposes multiclient ASIO to the host. I'm using Voicemeeter, which holds theASIO4All driver, and then exposes itself as both a virtual ASIO device, and a WDM device for regular Windows audio. FL Studio ASIO also doesn't take over the WDM, I think Cubase's Generic ASIO Driver has this feature as well.

Have you set *all* your samplerates to the same? In both your DAW and Windows? Because that sounds like there's mismatch and the codec gives up not knowing which one to settle on.

dude, they changed the name to FL Studio in 2003, you had 19 years to catch up

 

What do you think FL is standing for?