Its probably not working because the device is already in use by other programs. If so, there will be a red X shown in the ASIO control panel, like this:
The best thing to do is to set your default sound card in windows to something else, before starting ASIO playback. That way nothing will prevent ASIO from taking exclusive control of the DAC/sound card.
I doubt you want to uninstall audio devices from your computer just because they are listed in ASIO4ALL. Set it to your preferred output device and forget about it. It shouldn't be a problem.
I doubt you want to uninstall audio devices from your computer just because they are listed in ASIO4ALL. Set it to your preferred output device and forget about it. It shouldn't be a problem.
I am using a Creative Omni and for ASIO device it shows my soundcard. Should I install the ASIO4all driver? Since when I do that nothing comes out. WASAPI wise, I cant seem to get that or VST plugins to work. I can get sound using the ASIO device as my soundcard though
I've just stepped over my snobbery and started using the native client with a DirectSound output. Fidelify is missing the features I need like Radio and I don't hear any difference in SQ, so...
I've just stepped over my snobbery and started using the native client with a DirectSound output. Fidelify is missing the features I need like Radio and I don't hear any difference in SQ, so...
In my work speaker rig I hardly hear the difference until I'm doing over time late night stuff while closed and the speakers are WORKING. However with my headphone rig it is very noticeable.
I'm still using it daily however, at work and home.
I've just started using Fidelify too, mainly because I will have a DAC/Amp arriving soon and so want to feed it the best source through Spotify - that's if I don't switch to a lossless streaming company.
At the moment I'm using a modded Asus Xonar DS sound-card fed to a pre-amp/intergrated amp.
Now with Fidelify I can go into settings and select the ASIO driver and choose my Asus Xonar soundcard as it comes with ASIO driver / capability and the audio is clear but quieter (not an issue when using the amp to crank the volume) - much clearer than the ASIO4ALL option so I uninstalled them.
However I wanted to experiment with WASAPI, when I select it with Fidelify I have a HUGE list of devices, in-fact it lists every single audio device possible; be it HDMI, AUX or microphone etc. So I would select the "Speakers" (Asus Xonar DS) option (which is listed 4 times - tried them all) and kept getting the following error message.
"Could not start WASAPI drivers!"
I'm new to this whole audiophile scene and setup so any help would be appreciated and I apologise if I'm being a huge amateur here.
I was under the impression WASAPI came with Windows 7 x64 and that it would just work when selecting the audio device. Unless I have some how accidently disabled its process or service?
My setup is Xonar DS > headphone lead to RCA on Intregrated/pre-amp Cambridge Audio Azur540A > HD600 headphones.
So when using Windows DirectSound it displays my audio device output as Speakers (Asus Xonar DS) - which is why I tried selected these options in the WASAPI drop down menu out of the 50+ other device options.
Thanks in advance and I appreciate any help/ideas regarding my issue.
You'll either need to allow exclusive control of your sound device you're trying to us with wasapi under sound properties or possibly another software is using it and has exclusive control of it.
EDIT: Also if you've moved your Sonar to different USB ports the drivers get reinstalled but Fidelify keeps all previously used drivers, plugged in or not. So there could be a 2nd driver listing on there that's the right Sonar.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.