ASIO sound devices don't work

J

jmschwoerer

New Member
We stream in a house of worship with OBS*. Our Audio runs through an M-Audio mtrack Duo interface. I remember in Version ~20. or something there was an issue with ASIO, or it just was not native. I had to install a plugin. But since roughly 2 years this setup with ASIO runned perfectly. But since two weeks I figure again an ASIO issue. When inserting a ASIO device, there is no audio at all. No Input as well also no output.

We run the latest version of OBS (31. 0.1).

DO I need again an extra Plugin for ASIO?

Best regards

*so we use it each Sunday and several technicians can do updates and setting ... so I can not exactly say if the problem occurred after an update.
 
L

Lawrence_SoCal

Active Member
My understanding (could easily be wrong) is that ASIO is NOT native to OBS Studio.

With OBS v28, a new interface required many (most) plugins to be be updated to be compatible with the new version (ie, a plugin could work with 27 (and a couple of earlier versions, or it could work with v28 and later)

So, as always, an end-user needs to check each plugin individually (manually) before upgrading OBS Studio, and follow plugin author guidance on whether to upgrade plugin before or after an OBS Studio Update, or to back up settings (if possible), remove plugin, update OBS Studio, then install newer plugin [will vary by plugin]
 
A

AaronD

Active Member
ASIO is indeed a plugin, not native. And it's only on Windows, because only Windoze has such a stupid audio system that it needs to be bypassed like that. Direct from app to hardware.

If you're okay with finding and turning off all of the "features" that Windoze has by default, and if you're okay with a bit more latency than ASIO (not necessarily noticeable, but technically there), then you can just connect a native source in OBS to Windows' rendition of the card, and call it good. However:

Your 2-channel interface won't have this next problem, but a lot of professional and prosumer ones do:

OBS HATES multi-channel interfaces! The ASIO plugin allows you to choose specific channels, and that's fine, but OBS's native sources do not. The native sources assume that the entire device is a single surround source, with a format determined by the channel count, downmix all of that, and THEN give you that mess to try and make something of. Not good.

So if you can't use ASIO, and you must use a multi-channel interface, then you also must use something in between, that can pick out your desired channels and present OBS with a virtual device with only those channels. Usually, that's a DAW that you'd do all of your other processing in too, not in OBS, and send only the final, already-mastered soundtrack to OBS to pass through unchanged.

Or, you could insist on a stereo-only interface (that really does only report 2 channels total to the computer, and not 4 or 6 or whatever to support different options), and feed that from a physical console that does all the work and outputs the final, already-mastered soundtrack for OBS to pass through unchanged. Which might be what you're doing already.

If you're using a 2-channel interface for two separate mics or other unrelated sources, there's a hack to get separate control natively, but it *is* a hack, that only works for 2 channels specifically.
 
J

jmschwoerer

New Member
Thanks for the replay. So with the last update of OBS the ASIO plugin must have been removed. SO I've no changed to the original windows driver - this works now also.

I'm more an audio guy and grew up with Cubase - so I love ASIO ;) But when this setup now works thats fine for me.

Thanks again.
 
You must log in or register to reply here.
Top