ASIO won't install on Foobar2000
Feb 13, 2012 at 12:31 AM Thread Starter Post #1 of 13

Mauricio

500+ Head-Fier
Joined
Feb 4, 2012
Posts
634
Likes
37
I'm running Foobar2000 on Windows7.  Direct Sound (DS) and WASAPI work fine, but when I try to install the ASIO driver provided at the Foobar2000 website, the program crashes and can only be opened in safe mode.  What I am missing?  Any thoughts?
 
Feb 13, 2012 at 2:08 AM Post #2 of 13
Out of curiosity, what does ASIO do that WASAPI doesn't?  It is my understanding WASAPI is a superior solution and you won't have the unfortunate consequences of having other audio streams play at the same time.  For example, if listening to music and browsing the web at the same time, the experience of "Congratulations, you've just won a free Ipod Nano!" on top of your heavy metal double bass at full volume is altogether horrifying. 
 
It it my understanding WASAPI brings the best Windows bit-streaming functionality while not having the disadvantages of ASIO and Kernel Streaming.
 
 
Feb 13, 2012 at 5:16 AM Post #3 of 13
Personally I'd go back and use an older version of foobar, preferably 0.8.3.
 
I don't think WSAPI is superior to ASIO or vice versa, WSAPI just became flavour of the month. Both do bit perfect and unmangled audio, cheap cards don't support ASIO, hence the bias towards WSAPI now.
 
 
 
Feb 13, 2012 at 6:11 AM Post #4 of 13


Out of curiosity, what does ASIO do that WASAPI doesn't?  It is my understanding WASAPI is a superior solution and you won't have the unfortunate consequences of having other audio streams play at the same time.  For example, if listening to music and browsing the web at the same time, the experience of "Congratulations, you've just won a free Ipod Nano!" on top of your heavy metal double bass at full volume is altogether horrifying. 
 
It it my understanding WASAPI brings the best Windows bit-streaming functionality while not having the disadvantages of ASIO and Kernel Streaming.
 



 
 
What are these disadvantages of using ASIO you speak of? It works (or at least should work) exactly the same in regards to accessing the sound card exclusively; it doesn't let any other audio streams through.

In my case, what makes ASIO superior to WASAPI is the fact that when it's in exclusive mode, it doesn't interfere with other applications in any way at all. I can turn it on at any time, play some music, stop it and not have it cause any problems. WASAPI, on the other hand, will not let some games run when it's being used and it'll make some applications lose sound completely until they're restarted. It's probably sound card/driver dependent, so your mileage may differ.
 
Feb 13, 2012 at 8:25 AM Post #5 of 13


Quote:
Out of curiosity, what does ASIO do that WASAPI doesn't?  It is my understanding WASAPI is a superior solution and you won't have the unfortunate consequences of having other audio streams play at the same time.  For example, if listening to music and browsing the web at the same time, the experience of "Congratulations, you've just won a free Ipod Nano!" on top of your heavy metal double bass at full volume is altogether horrifying. 
 
It it my understanding WASAPI brings the best Windows bit-streaming functionality while not having the disadvantages of ASIO and Kernel Streaming.
 


What does ASIO do that WASAPI doesn't?  I don't know.  I'll let you know once and if I get ASIO to install.  It's altogether possible that it does not nothing beyond what WASAPI already does.
 
 
Feb 13, 2012 at 10:26 AM Post #6 of 13


Quote:
I'm running Foobar2000 on Windows7.  Direct Sound (DS) and WASAPI work fine, but when I try to install the ASIO driver provided at the Foobar2000 website, the program crashes and can only be opened in safe mode.  What I am missing?  Any thoughts?


..are you referring to the latest version of Foobar and ASIO?
I had a bit of an issue with ASIO and the latest foobar also, what I did was install an older version I had and use Foobar to update the plugin.
 
I am not sure what is going on with that plugin but I had issue with it also when installing the player on a new system.
 
 
Feb 13, 2012 at 10:36 PM Post #8 of 13


Quote:
Ya, I am running Foobar2000 v1.1.10.  I'll try it on an older version.  Thanks.



What I mean is try and find an older version of ASIO plugin, install it and then use Foobar to update it to the latest version.
That worked for me when I had this issue last night installing this on another system.
 
Feb 14, 2012 at 5:05 AM Post #9 of 13
I still fail to understand why WASAPI isolating the audio stream so other sources can't be injected isn't desirable.  I guess you've never had the luxury of casually browsing the web late at night, listening to some mild music, only to have a flash audio advertisement added to your music, and both the music and flash ad go to full volume.  It is astonishingly awful, although it does get the heart rate up, as well as the roommates :/  Speakers/subs could easily be damaged, in fact I'm surprised I haven't blown one doing this.
I used Firefox with Ad block and Flash block when I was listening to music, but that is pretty lame.  Then I just got a dedicated audio computer that I removed the internet gateway so that it can't even browse the web but I can still network it.  This was before Windows 7 and WASAPI...
I don't recall wanting to listen to more than one thing at a time anyways.  I find it very simple to hit the stop button on Foobar, then I can play what I want. 
 
Feb 14, 2012 at 7:11 AM Post #11 of 13


Quote:
 


Should probably read my post then.



My bad, reading fail. 
If I need more than one stream at a time, I usually just have another instance of Foobar configured normally without any kernel bypass.  That way I can have music and video games at the same time, etc.  I don't really need the increased audio quality with multiple streams.
One thing you can consider is installing Foobar twice (I do the portable install and regular install.)  That way you can configure each installation differently.  For example, one installation could be the new version with WASAPI, and the other the older version with ASIO.  If you don't need any of the features of the newer version of Foobar, then I suppose the old version is fine.
Just be careful with flash audio content, have you had any issues with it so far?
 
Feb 14, 2012 at 9:09 AM Post #12 of 13


Quote:
My bad, reading fail.  If I need more than one stream at a time, I usually just have another instance of Foobar configured normally without any kernel bypass.  That way I can have music and video games at the same time, etc.  I don't really need the increased audio quality with multiple streams.
One thing you can consider is installing Foobar twice (I do the portable install and regular install.)  That way you can configure each installation differently.  For example, one installation could be the new version with WASAPI, and the other the older version with ASIO.  If you don't need any of the features of the newer version of Foobar, then I suppose the old version is fine.
Just be careful with flash audio content, have you had any issues with it so far?

 
 
ASIO doesn't mix multiple streams of audio. It works exactly like WASAPI in that particular aspect (there are some differences in other areas). It's sound card/system/driver dependent (EssST/W7/latest from C-Media), so -- like I said -- it might work differently for you. I remember that KS in XP back when I was using an X-Fi based sound card would let other streams through, even though I don't think it should do that; not sure if ASIO behaved the same way.
 
Sorry for dragging it a little OT.
 
Feb 14, 2012 at 9:35 AM Post #13 of 13
I have a slightly different experience, although you do say multiple 'asio' streams and I usually mix types. ASIO, unlike WSAPI doesn't cut the card off completely.
 
If you have an Emu at least you can play foobar via ASIO and aslong as the sample rate matches what Windows/Games are producing then DirectSound etc still works. I regularly play Quake via DS and foobar via ASIO at the same time. If I mute Windows volume control it does not mute ASIO, so I can avoid the noises that way
 
Additionally all motherboards pretty much have onboard sound, so I connect that to some speakers and use that as my default device, all these annoying noises you talk about are then produced there, leaving the seperate audio card only doing what I direct to it output to the 'phones. (as you now have dual volume controls, one per card, leave the speakers on low)
 

Users who are viewing this thread

Back
Top