Windows Vista has a new audio output method called WASAPI which allows to bypass unnecessary processing levels, reducing latency. It would be very nice if someone could write a WASAPI output plugin for foobar2000. It could serve as a safe kernel streaming replacement for Vista.
It's been done but there are somewhat annoying bugs that I don't know how to workaround yet and the whole thing is unusable on large percentage of pre-SP1 machines because of documented Vista mixer bugs. This plug-in will definitely be released at some point.
Thanks for the fast reply, I am looking forward to the release of this plugin! And I'm certainly going to install SP1.
Oh i can't stand this stupid vista mixer, i want bit exact solution
When wasapi plugin will be released? Or i need to buy an asio soundcard?
"whole thing is unusable on large percentage of pre-SP1"
So it's working on sp1 vista? Then why haven't been released yet? Who don't have sp1 don't use it, it's simple
Awesome can't wait till this is implemented!
Thanx, Peter
Here it is: http://www.foobar2000.org/components (http://www.foobar2000.org/components)
I've done what I could to make this usable and the results are quite decent on all of my machines by now.
Unfortunately, some of the issues I've noticed still persist and I have no power over them as they're clear bugs in Microsoft's code still present as for Vista SP1 with latest updates. For an example, if you uncheck the Allow applications to take exclusive control of this device option in your device's properties, any apps currently playing audio in exclusive mode may crash.
This component has been in development since late 2007. First it got stalled because exclusive mode was completely broken on my workstation with pre-SP1 Vista x64. Then it got stalled because of weird behaviors occuring with various soundcards not using Microsoft's own audio drivers (the released version contains a workaround for these). I wouldn't recommend this component for regular use, it seems nobody else seriously used WASAPI before and Microsoft's QA decided to skip verifying whether it works properly.
I tried the plugin with the lastest foobar2000 release (0.9.5.3) under vista x64 SP1 and onboard HD audio codec (realtek alc660 with the lastest drivers, 1.91). So far it seems that...
a)8 bit audio "works" (lots of buzzing and distortion).
b)16 bit audio output works fine.
c)24bit audio output does not work (Unrecoverable playback error: Could not open device (8889000F)
d)32 bit audio output does not work either."Unrecoverable playback error: Could not open device: unsupported data format".
I don't know if this might be related to this behaviour, but in Xmplay there is a extra option in the WASAPI output plugin ("use native 32 bit resolution in shared mode").
Thanx for the plugin Peter but i'm having a problem with it.
I use a Edirol UA25 which is connected via usb. I have set it to output using WSAPI Edirol UA25. But when I try and play a track I get a "Unrecoverable Playback error: Could not open device (Device in use)".
If I set WASAPI to use the onboard soundcard it seems to playback.
I do not have any other audio programs open?
Cheers
a)8 bit audio "works" (lots of buzzing and distortion).
b)16 bit audio output works fine.
c)24bit audio output does not work (Unrecoverable playback error: Could not open device (8889000F)
d)32 bit audio output does not work either."Unrecoverable playback error: Could not open device: unsupported data format".
Similar problem here under Vista 32 bit using an m-audio transit usb soundcard. 8 bit audio, however, doesn't work either.
Thanx for the plugin Peter but i'm having a problem with it.
I use a Edirol UA25 which is connected via usb. I have set it to output using WSAPI Edirol UA25. But when I try and play a track I get a "Unrecoverable Playback error: Could not open device (Device in use)".
If I set WASAPI to use the onboard soundcard it seems to playback.
I do not have any other audio programs open?
Cheers
Look in Vista's mixer panel (the one that shows the volume levels of individual programs), and check to make sure that no other programs are showing-up there.
Edit: forgot to mention that there also seems to be a noticeable lag between moving the volume slider, and the volume actually changing.
Peter, thank you very much!
a)8 bit audio "works" (lots of buzzing and distortion).
b)16 bit audio output works fine.
c)24bit audio output does not work (Unrecoverable playback error: Could not open device (8889000F)
d)32 bit audio output does not work either."Unrecoverable playback error: Could not open device: unsupported data format".
For reference, I'm getting b/c/d too, and the "8889000F" error with 8-bit, on two different onboard audio chips with Microsoft audio drivers. MSDN doesn't mention what this error code (AUDCLNT_E_ENDPOINT_CREATE_FAILED) means in this context, it's probably a driver or OS bug.
I don't know if this might be related to this behaviour, but in Xmplay there is a extra option in the WASAPI output plugin ("use native 32 bit resolution in shared mode").
Shared mode is not really interesting for us - it still lets Vista's audio mixer mix our stream with other sounds but as far as I can tell it requires us to produce an audio stream in the exact format that the mixer works with (32-bit floating-point, sample rate matching Windows mixer settings and channel count matching soundcard specifications), so it's pretty much the same as DirectSound but more painful to use because Windows no longer does resampling or channel mixing behind the scenes for you when necessary.
Thanks! It works fine in 16bit mode. However, the volume control reacts a bit slow. Is that normal?
I wonder if this plugin offers anything new to n00bs like me
Explain, please
OHHHHHH yesss thank you!
Its working working on 16bit, but i have that unrecoverable playback error too @24/32bit.
Vista 64 SP1, Realtek ALC883 audio, R1.94 driver
But now i can put the bass to high level without distortion Now the "wall" are my ears, and my headphone
BTW 24bit mode in wasapi exclusive is working in xmplayer for me, just its doing random ctd-s, with unhandled exeption errormessage, and it have winamp like ui, and i hate that
Tried it in Vista SP1, but it says that it cannot open the device or something...
Using an Onkyo SE90-PCI card with the newest drivers...
edit: And, it works in XMPlay
BTW 24bit mode in wasapi exclusive is working in xmplayer for me, just its doing random ctd-s, with unhandled exeption errormessage, and it have winamp like ui, and i hate that
Perhaps I'm missing sth. but playing back an original 24 bit flac file in xmplay using wasapi exclusive mode shows "Output 96000 hz - stereo - 16 bit" in the console. It seems that the output resolution gets changed to 16 bit which also works just fine in foobar.
Here's a beta version of the component for you to test: [link removed, use the latest stable version instead]
Changes:
- Somewhat more informative error messages.
- 24-bit mode now works on more soundcards - 24-bit padded to 32-bit is used when possible.
Thanks, beta version works great in 24bit with my onboard Realtek ALC888 and latest drivers (R1.96)
now it's working for me. ALC883
"24-bit padded to 32-bit is used when possible." What does this mean?
@sanyigz: The eight extra bits utilized in 32-bit are padded as zeros. This allows you to have a 24-bit stream within a 32-bit container.
Still doesnt work for me...
Says the 44100hz @ 24bit @ 2CH is unsupported, although my soundcard can output 192khz @ 24bit @ 2CH, so i dont see the prob
yes! WASAPI now works fine with my setup (vista x64 SP1, realtek ALC660, 1.96 drivers).
As a side effect, 8 bit audio output is now broken:
"Unrecoverable playback error: Could not open device: unsupported data format: 44100 Hz / 8-bit / 2 channels"
New version (1.1) up.
Thank you very much and it works great with my Onkyo SE-200PCI
Can anyone explain me the differences between the WASAPI plugin and kernel streaming? They both should be bit-exact, or is kernel streaming not bit-exact on Vista?
Which of the two plugins is to favor, when I want bit-exact playback on a Vista SP1-machine?
Can anyone explain me the differences between the WASAPI plugin and kernel streaming? They both should be bit-exact, or is kernel streaming not bit-exact on Vista?
Which of the two plugins is to favor, when I want bit-exact playback on a Vista SP1-machine?
There is no kernel streaming on vista.
There is no kernel streaming on vista.
But the KS plugin works under Vista. If it does not work as real kernel streaming, what does it deliver then?
Edit: Also mentioned in this (http://www.hydrogenaudio.org/forums/index.php?showtopic=54367) thread.
Kernel Streaming does not work with with some of cards having native Vista drivers.
More info about WASAPI vs ASIO vs KS: http://wiki.hydrogenaudio.org/index.php?ti...foo_out_wasapi) (http://wiki.hydrogenaudio.org/index.php?title=Foobar2000:Components_0.9/WASAPI_output_support_(foo_out_wasapi))
Thanks for the explanation, Peter!
Although I did not have problems with my soundcard using kernel streaming under Vista, I switched to the WASAPI-plugin. It also works perfect with my soundcard. Most important thing for me is to keep the output bit-exact without resampling in the audio stream.
Awesome~! Thanx Peter!
Works great most of the time, but I get an error sometimes when it opens the next track in the playlist.
Opening track for playback: "P:\V.A\[2008.01.30] SUMMIT 04\01 - Venom.mp3"
WASAPI: 48000 Hz / 16-bit / 2 channels
Opening track for playback: "P:\V.A\fool's mate select omnibus seduction#1\04.exist+trace - SACRIFICE BABY.mp3"
Unrecoverable playback error: Could not open device (88890002)
Bug fixed in 1.2, thanks for reporting.
No problem, thanks for fixing it!
EDIT: Also have an issue with mono files:
Opening track for playback: "C:\Users\bb10\AppData\Local\Temp\En-uk-daylight-savings-time.ogg"
Unrecoverable playback error: Could not open device: unsupported data format: 44100 Hz / 16-bit / 1 channels
For mono files, the fix is pretty simple: use the "convert mono to stereo". DSP
Wasapi seems to be limited in a way not to support anything below 44100 hz, 16 bit stereo. I can't play 22khz and 32 khz mp3 files.The solution: resample to 44100 or higher with secret rabit or PPHS.
If I play music using this plugin I have to close foobar2000 and restart any other applications afterwards to unmute them. Isn't there another way to disable the exlclusive mode when I stop/pause playback?
I tried the WASAPI output 1.2, Vista SP1, Realtek ALC662 (driver 6.0.1.5391), fb2k 0.9.5.4b3.
with 2 files both FLAC 5.1 channels, 24bit. A) 48k, B) 96k sample rate.
with foobar2000 set to output 24 bits
I could play A) but got the "Could not open device (8007001F)" with B)
with foobar2000 set to 16 bit output, they played both.
Also when resampled to 48k they played both at 24 bit output.
As both did with the "Convert 5.1 to stereo" dsp and no resampling.
(4.0 at 24 bit/96kHz did raise the error again)
So I pinned my problem down to >2 channels, 24bit, 96000Hz output. Hope this helps to find something.
If I play music using this plugin I have to close foobar2000 and restart any other applications afterwards to unmute them. Isn't there another way to disable the exlclusive mode when I stop/pause playback?
In foobar plugin i didn't saw non exclusive switch, but its better to turn on directsound then, cuz if wasapi isnt in exclusive mode, so in shared mode, then it's no more bit exact.
First of all...THANK YOU!!!!
Now here is my setup:
Vista Ultimate 64 SP1 (using Default Format of 16bit, 44100Hz and both Exclusive Mode check boxes checked)
Auzen Prelude (using Audio Creation Mode - Bit Matched Playback) & latest driver
Foobar2000 v 0.9.5.4
WASAPI output v 1.2
My question is this...
Will WASAPI always play the source bit perfect and untouched???
Say I play a 16bit 44.1 wav source...will the end result be 16bit 44.1?
Then say I play a 24bit 96 wav source...do I have to change the default format in Windows sound properties and then change the Foobar output to 24bit???? ...or does WASAPI just play the raw source and the other settings have no effect (this would be the best method).
Again, thank you and hopefully I am not being too confusing. Just want this to be user friendly.
Not sure if this is a bug...
The WASAPI plugin seems to have a delay the length of the chosen buffer when resuming after pause.
So if I choose a 2000ms buffer, playback after pause will resume 2 seconds after I press play.
Not sure if this is a bug...
The WASAPI plugin seems to have a delay the length of the chosen buffer when resuming after pause.
So if I choose a 2000ms buffer, playback after pause will resume 2 seconds after I press play.
No, it's not a bug. It's a limitation.
Does this plugin do anything if I use an external usb dac? The dac when plugged in via usb already ignores the mixer. master volume doesnt work anymore without the plugin with the usb dac.
click on seek with WASAPI.
Is "click on seek"-problem another limitation of WASAPI output plugin?
WASAPI plugin works fine on Windows Server 2008 Enterprise x64 (with SP1) and ESI Juli@ sound-card (24-bit output data format).
Currently I am testing new Windows Server 2008 R2 x64 beta (based on Windows 7) and wasapi doesn't work and it takes 5-7 seconds before mp3 starting to play in foobar2000.However, DS:Primary Sound Driver output works fine.Computer specs: Intel Core2Quad Q6600 @ 3600Mhz, 4Gb of RAM, Windows Server 2008 R2 beta (only 64-bit).
I have tested foobar2000 0.9.6.1 + Wasapi output 1.2 under windows 7 x64 (public Beta 1, build 7000). So far, it works using realtek hd audio drivers for vista 64 (2.14). As in vista 64, 24 bit output is fine, but 32 bit will not work.
Still, they are both beta os and we can not expect everything to work "out of the box" right now.
Wasapi output in Foobar 2000 dont work correctly with DACs connected by USB ports. Sound very interrupts.
Wasapi plugin in Xmplay player working perfectly.
Wasapi output in Foobar 2000 dont work correctly with DACs connected by USB ports. Sound very interrupts.
Wasapi plugin in Xmplay player working perfectly.
I cannot reproduce that. For me WASAPI works like a charm with an USB-DAC.
(Vista Ultimate x64)
WASAPI output v 1.2, foobar 0.9.6
When I try to play 192/24 file on Realtek ALC883, i get
"Unrecoverable playback error: Could not open device (8007000E)"
Playing with DirectSound works, but i doubt of Vista internal processing.
Using ASIO4All works fine with 192/24, and it's like bit-perfect.
Using WASAPI output v 1.2 with Revo 5.1 playing 192/24 works fine, but with Realtek ALC883 I get error described above.
May be there is some error in WASAPI plugin, because ASIO4All can play 192k on Realtek and WASPI don't.
I found the thread to solution on some forums. I've changed output buffer size from 1000ms to 650ms and then WASAPI output on Realtek ALC883 playing 24/192 file started to work!
I found the thread to solution on some forums. I've changed output buffer size from 1000ms to 650ms and then WASAPI output on Realtek ALC883 playing 24/192 file started to work!
Thank you for this solution! My RME Multiface II PCIe now works in 24bit mode! Regards
the WASAPI plugin is working perfectly with my Trends Audio UD-10 USB transport
I'm trying the plugin with Windows 7 x64, it works at any buffer sizes under 4000ms, every sample rates up to 192kHz and works at 16-bit and 24-bit, can take exclusive mode, but it skips. No crackles, no pops, but it skips randomly in the played files. ASIO, DS, KS, no problem, but WASAPI skips. My sound card is an Audigy 2 ZS Platinum.
I've only tried it on one system, but to reproduce the problem :
1. Install and select WASAPI plugin.
2. Play a song.
EDIT:
XMplay's WASAPI plugin works on Windows 7 beta 1 without problems at any samplerate and bitrate, but unfortunately, XMplay isn't foobar2000.
Problem solved: the Kernel Streaming plugin works beautifully at 24/192 (ASIO works as well, but it doesn't , and gets exclusive use of the device, which wasn't the case with the DS plugin.
with the latest foobar v0.9.6.2 WASAPI plugin works fine on Windows Server 2008 R2 x64 (based on Windows 7) and ESI Juli@ sound-card but every 20-25 seconds there is a 1-2 second sound glitches, which repeating continuously. Also foobar can not start playback of lossless tracks from beginning, starting 10 -15 seconds later or even in the middle of a song.
i also got "Could not open device" errors, when trying audio books and this helped:
For mono files, the fix is pretty simple: use the "convert mono to stereo". DSP
Wasapi seems to be limited in a way not to support anything below 44100 hz, 16 bit stereo. I can't play 22khz and 32 khz mp3 files.The solution: resample to 44100 or higher with secret rabit or PPHS.
so resampler and channel mixer should stay in DSP just in case
and buffer set to around 650
[edit] just dumb sometimes
Just discovered this foobar plugin, and I'm eternally grateful to the person who made it. Just what I was looking for.
However, I'm getting an error message with my (admittedly pretty rare) 5ch (both 4.1 and 5.0) 96/24 audio files:
Unrecoverable playback error: Could not open device: unsupported data format: 96000 Hz / 24-bit / 5 channels
5ch 48kHz 16bit works without any problems. I have no 5ch 48/24 files to test with, though, so I don't know about them.
Any ideas? I'd rather not upmix to 5.1 (I like to keep my audio as it was intended), maybe adding 'blank' channels would work? (assuming, of course, that it's a problem caused by the unusual channel configuration...)
EDIT: I found a temporary solution to this problem. Using the Matrix Mixer plugin, I just transferred a minimal part (e.g. 0.001) of the left and right channels to the missing channel. This way the audio is perceived as containing 6 channels, though one of the channels will be inaudible.
Could not open device: unsupported data format: 96000 Hz / 24-bit / 5 channels
See my test results and findings at post #36 (http://www.hydrogenaudio.org/forums/index.php?showtopic=62653&view=findpost&p=574512). Somehow it doesn't work for multi channel (>=4.0) at 24b/96kHz.
Hint: another workaround is to set foobar's output to 16bit.
would be nice if it can be fixed, maybe a Windows thing though.
Windows 7 x86 build 7068 and 7077
WASAPI output:
Unrecoverable playback error: Could not open device (88890020)
in Windows 7 x86 build 7000/7022/7048/7057 WASAPI worked
The WASAPI plugin seems to have a delay the length of the chosen buffer when resuming after pause.
So if I choose a 2000ms buffer, playback after pause will resume 2 seconds after I press play.
No, it's not a bug. It's a limitation.
I have noticed this too, to be more precise, it not only pauses buffer length time, but it (in effect) skips that time. To say it different, foobar starts playing right away after unpause, but only some time later (buffer lenght) output starts. So you miss one buffer worth of sound This maybe the limitation.
Could, as a workaround, the buffer be filled with silence after unpause (if it works that way)? At the start of a track I never seem to miss a part and not such long delay either.
Another observation: when I pause a track, move the position slider and unpause, it starts playing without delay. Maybe there is a way to remove this limitation.
Windows 7 x86 build 7068 and 7077
WASAPI output:
Unrecoverable playback error: Could not open device (88890020)
in Windows 7 x86 build 7000/7022/7048/7057 WASAPI worked
WASAPI works fine here on 7077 x64.
Windows 7 x86 build 7068 and 7077
Unrecoverable playback error: Could not open device (88890020)
WASAPI works fine here on 7077 x64.
As WASAPI may work or not depending on buffersize, number of channels in combination with certain bit depths and sample rates, this doesn't say much on it's own.
Windows 7 x86 build 7068 and 7077
Unrecoverable playback error: Could not open device (88890020)
WASAPI works fine here on 7077 x64.
As WASAPI may work or not depending on buffersize, number of channels in combination with certain bit depths and sample rates, this doesn't say much on it's own.
Actually this is a result of a change to Windows 7, I've sent a PM to Peter to work on resolving the issue.
I use the Auzentech X-meridian with c-media's latest driver for 8787 and windows 7 beta x86 7048 with foobar, and I get no sound using wasapi. All I get is this weird lag when I click on play then I see foobar playing something but no sound comes out. I tried asio using foobar and it is stuck on 24 bit and 80ms. When I try to configure ASIO, it resets back to 24 bit and 80 ms automaticly so I am using kernel streaming with foobar now. Is there another audio player as good or better than foobar that works with wasapi or asio using windows 7 beta?
Windows 7 x86 build 7068 and 7077
WASAPI output:
Unrecoverable playback error: Could not open device (88890020)
in Windows 7 x86 build 7000/7022/7048/7057 WASAPI worked
Same here, got the exactly error message in Windows 7 RC build 7100
foobar2000 version is 0.9.6.5
Windows 7 x86 build 7068 and 7077
WASAPI output:
Unrecoverable playback error: Could not open device (88890020)
in Windows 7 x86 build 7000/7022/7048/7057 WASAPI worked
Same here, got the exactly error message in Windows 7 RC build 7100
foobar2000 version is 0.9.6.5
Same Here, Any Solution yet?
Same Here, Any Solution yet?
It's working fine here on 7100 x64.
Anyway, http://www.hydrogenaudio.org/forums/index....st&p=631925 (http://www.hydrogenaudio.org/forums/index.php?s=&showtopic=71665&view=findpost&p=631925) .
Windows 7 x86 build 7068 and 7077
WASAPI output:
Unrecoverable playback error: Could not open device (88890020)
in Windows 7 x86 build 7000/7022/7048/7057 WASAPI worked
Same here, got the exactly error message in Windows 7 RC build 7100
foobar2000 version is 0.9.6.5
You can set "Buffer Length"<=500
Thanks for the tips. It works when buff set to 500.
New version out, incompatibility with Windows 7 has been resolved.
New version out, incompatibility with Windows 7 has been resolved.
Thanks Peter, i'll try it and will report if there are some bug/limitation
Still having trouble with my after the update. Error when buffer above 500ms, garbled output when buffer below 500ms.
Why it not displaying playback statistic at console? And still cannot use bit depth under 16-bit and over 24-bit.
Thanks for new version. Finally i have sound.
Does anyone still have version 1.2? Unfortunately I overwrited it and I can't find it anymore. I'm pretty sure it didn't have delay while seeking...
EDIT: Hmm, maybe it isn't delay but some kind of strange clitch. I have Vista x64, Realtek ALC883 and sound driver version R2.24.
EDIT2: Found it. 1.2 has no seeking clitch like 2.0. So I'm staying with 1.2.
I have requested a WASAPI shared mode output mode for foobar2000 before but Peter is not interested in doing it.
SO now all I want is syncronized volume control with the mixer in Vista and Windows 7. As in when you change the volume for the foobar2000 app the volume slider in foobar2000 is updated as well.
Try WMP11/12 and then you see what I mean. Why is this so hard to do for foobar2000?
Just read up on the Audio Session stuff. You don't even have to use WASAPI for it to work.
There are also lots of samples in the Windows SDK that demonstrates this.
no more glitches for me with this new version! (windows vista, m-audio audiophile firewire, buffer: 1450, 24bits)
thanks a lot peter
Ahh, works great now. Thank you Peter!
v0.9.6.7 solves my playback problems. Thanks to the Foobar2000 developers!
Thanks for this new version.
I found out that playing with the buffer length make all the difference.
for example I could play a 5.1 48kHz 24bit track with a max. buffer length of 900 ms.
But to play a 5.1 96kHz 24 track I had to lower it to 450 ms.
So double the (output) bitrate, half the buffer time
(Is there an about 380kB buffer limitation somewhere?)
So, that's acceptable. The only thing left (for me) now is the "missing buffer's length of audio" after using pause.
read the thread and I cant seem to find a link to the wasapi developers page. Is there a page with descriptions of the versions and bugs, etc...?
Hello,
I am a noobie and trying to use WASAPI with my yellowtec external soundcard. I have got the relevant dll in the components folder but everytime I try to play I get the following error message:
Unrecoverable playback error: Unsupported stream format: 44100 Hz / 16-bit / 2 channels
I have tried different bit rates and played with buffer settings as some members mentioned but nothing seems to work. I also tried PPHS DSP but its also does not solve my issue. With DS it works fine.
My PC is Vista 32-bit with SP2 and foobar player version is latest 0.9.6.9.
I will appreciate any help as I am running out of ideas
Thanks
I have tried different bit rates and played with buffer settings
Also try different bit depths: 24-bit, 32-bit.
I have tried different bit rates and played with buffer settings
Also try different bit depths: 24-bit, 32-bit.
Sorry for my confused problem description. What I meant was I tried different output data formats (8, 16, 24 & 32), which I think is what you are referring to, and all of them give me the same error message.
Just tried using this plugin since recently moved to Vista 64bit. I get the following error on the console;
Playing
Opening track for playback: "S:\Music T to Z\The Gypsy Sons\The Gypsy Sons - 2009 - Walking On The Water\01 - Walking On the Water.mp3"
Unrecoverable playback error: Not enough storage is available to complete this operation. (0x8007000E)
... and yes there is oceans of room on S:!
Any ideas?
Is there any chance this plugin could support WASAPI shared mode too? (I just noticed iTunes 9 does it )
What would be the difference with DirectSound then?
The only thing left (for me) now is the "missing buffer's length of audio" after using pause.
Remove the Realtek driver and use the MS driver.
The only thing left (for me) now is the "missing buffer's length of audio" after using pause.
Remove the Realtek driver and use the MS driver.
Thanks, that works . Now the fading (at stop. seek, pause) don't work anymore, but that is less important to me. Strange are the ways of Windows Audio.
I've tried using the plugin but have run into issues with some 32 KHz samples. They give the unsupported format error when trying to output over S/PDIF (I forget the exact error message). Is there some sort of conditional resampler I could use to overcome this limitation?
The only thing left (for me) now is the "missing buffer's length of audio" after using pause.
Remove the Realtek driver and use the MS driver.
Thanks, that works .
I'm back to the Realtek driver . I wanted to switch back to a multi channel setup (4.0 for the moment) but the MS driver would not let me configure anything else than 2.0. The Realtek driver let's me choose between 2.0 4.0 and 5.1.
Just tried using this plugin since recently moved to Vista 64bit. I get the following error on the console;
Playing
Opening track for playback: "S:\Music T to Z\The Gypsy Sons\The Gypsy Sons - 2009 - Walking On The Water\01 - Walking On the Water.mp3"
Unrecoverable playback error: Not enough storage is available to complete this operation. (0x8007000E)
... and yes there is oceans of room on S:!
Any ideas?
Had the exact same problem after switching to Windows 7 x64 (from Vista x64). In my case, though, it only applied to 96/24 stereo FLAC (5.1 48/24 seems to work fine) in WASAPI mode. I managed to get it to work by reducing the buffer length to 450ms, but now the audio is skipping like mad after a while.
I'll keep messing with the buffer settings, we'll see if I can fix it, but if anyone has any suggestions, it'd be greatly appreciated.
Vista 32bit SP2 (+all security updates)
Maudio Revolution 5.1 (driver 5.10.0.5064)
foobar2k 0.9.6.9
wasapi 2.1
44,1khz 16bit audio runs fine with wasapi.
96khz 24bit and 48khz 24bit don't.
"Unrecoverable playback error: Unsupported stream format: 48000 Hz / 24-bit / 2 channels"
i'm using asio instead, should do the same for me(no resampling, bitexact)
thx!
Sorry to those who are irked by thread resurrections, I decided to please the anti-frivolous-thread-creation personalities instead.
What would be the difference with DirectSound then?
There probably isn't a difference in use, but is there a technical difference? I'm just wondering, since Windows 7 is out, if the WASAPI plugin can be updated to support all the latest essential functionality that WASAPI on Windows 7 provides. However, if Vista is the lowest common denominator here causing problems here and there with implementation, then I guess the plugin is sufficient as it is.
Can WASAPI shared mode (or even exclusive mode) work with playback crossfading in FB2K?
I've got a weird problem with this output plugin on my Win7 x64 system using an ATI 5670 and the Realtek ATI HDMI driver. The sound playback is perfect, but when I hit pause, I get a period of silence equal to the (buffer length - ~100ms), followed by the last 100ms or so of audio that was played. This repeats over and over until I hit play again. Changing the buffer length only seems to alter the amount of "silence" before the sound plays again.
I have weird skipping/popping sounds when using DS output so I'd REALLY like to use the WASAPI plugin, but if I can't pause that's kind of a problem.
The silence on resume becomes imperceptible to me with a 50ms buffer.
Is there a possibility for an option to release the exclusive mode control on pause?
Thanks.
Dear All,
I have an ATI 5830 card with the latest driver installed
My problem with WASAPI is that whenever I open a webpage or image etc during playback, sound mutes for a while
I tried playing with the buffer settings but the problem still persists
Any suggestions please?
Many thanks
Try really huge buffer size first. Like 2-4 seconds.
I've got a weird problem with this output plugin on my Win7 x64 system using an ATI 5670 and the Realtek ATI HDMI driver. The sound playback is perfect, but when I hit pause, I get a period of silence equal to the (buffer length - ~100ms), followed by the last 100ms or so of audio that was played. This repeats over and over until I hit play again. Changing the buffer length only seems to alter the amount of "silence" before the sound plays again.
I have weird skipping/popping sounds when using DS output so I'd REALLY like to use the WASAPI plugin, but if I can't pause that's kind of a problem.
Hi all. This my first post here.
I am having the exact same problem as described by Mordred. The WASAPI plugin works great in all respects except when I pause the audio I get the same repeating audio as he described. I also have Windows 7 x64 using ATI4850 and the Realtek ATI HDMI driver. Has anyone else had this problem or found a fix?
I love the WASAPI function and it is only a minor nuisance not to be able to use the PAUSE button, but it is a nuisance.
Those ATI HDMI outputs should work perfectly well without Realtek's drivers on your OS. Try uninstalling the driver and test WASAPI again. Also skipping with DS output suggests that there is something silly going on elsewhere in the machine. DPC Latency Checker (http://www.thesycon.de/eng/latency_check.shtml) will probably show spikes. Would be good idea to try and solve that.
Hi, Everyone
I've got Windows 7 Ultimate, an EMU 0404 soundcard (with the latest drivers), and foobar2000, v1.0.3.
I can't get the WASAPI plug-in to work at all. I consistently get the following error:
"Unrecoverable playback error: Endpoint creation failed (0x8889000F)"
Is there any hope?
Thanks in advance,
~esa
Those ATI HDMI outputs should work perfectly well without Realtek's drivers on your OS. Try uninstalling the driver and test WASAPI again. Also skipping with DS output suggests that there is something silly going on elsewhere in the machine. DPC Latency Checker (http://www.thesycon.de/eng/latency_check.shtml) will probably show spikes. Would be good idea to try and solve that.
This is in a HTPC and I need the Realtek HDMI drivers for surround sound. You were correct about the DS output though. I tried the DPC Latency Checker and turns out that my network card is at fault. My latency regularly reaches hits 40k microseconds. Turns out this is a pretty common problem with builtin Realtek NICs on Motherboards. I just ordered an Intel NIC which should fix the problem permanently and I can go back to using the DS driver.
Thanks for the troubleshooting tips.
Hi, Everyone
I've got Windows 7 Ultimate, an EMU 0404 soundcard (with the latest drivers), and foobar2000, v1.0.3.
I can't get the WASAPI plug-in to work at all. I consistently get the following error:
"Unrecoverable playback error: Endpoint creation failed (0x8889000F)"
Is there any hope?
Thanks in advance,
~esa
When I see this message it is because Windows is not recognizing the output device or speakers. I have to fiddle with things until I get Windows to see the device. Look at control panel/sound.
Those ATI HDMI outputs should work perfectly well without Realtek's drivers on your OS. Try uninstalling the driver and test WASAPI again. Also skipping with DS output suggests that there is something silly going on elsewhere in the machine. DPC Latency Checker (http://www.thesycon.de/eng/latency_check.shtml) will probably show spikes. Would be good idea to try and solve that.
Thanks for the reply. DPC Latency Checker showed no problem. The PAUSE button works with DS output. Again, I get perfect sound with WASAPI. It is only when I use the PAUSE button and I am using WASAPI HDMI output with 5.1 sound that I hear skipping. When I start to PLAY again the sound is fine. To be clear, normally I expect to hear nothing after pressing PAUSE, but I hear repeating sound.
When I see this message it is because Windows is not recognizing the output device or speakers. I have to fiddle with things until I get Windows to see the device. Look at control panel/sound.
Thanks for the reply.
I've experimented with several settings in Control Panel>Sound, but nothing's made any difference. Is there something, specifically, that I should be looking for?
Also, I forgot to mention that I'm using the 64-bit version of W7, if that makes any difference.
Thanks!
~esa
I am trying to use WASAPI with my ATI card.
My receiver supports 16, 20 and 24 bit files but the ATI card is forcing me to pick one sampling rate for all audio.
Everything seems fine with standard CD audio.
I get an unexpected error (0x800700F1) "hardware error" with my multi-channel WAV files.
These files are standard 5.1 24 bit 96kHz audio and play fine without the WASAPI component installed.
I am trying to use WASAPI with my ATI card.
My receiver supports 16, 20 and 24 bit files but the ATI card is forcing me to pick one sampling rate for all audio.
Everything seems fine with standard CD audio.
I get an unexpected error (0x800700F1) "hardware error" with my multi-channel WAV files.
These files are standard 5.1 24 bit 96kHz audio and play fine without the WASAPI component installed.
I am certainly no expert here. All I can suggest is to install the realtek drivers and decrease the buffer value in the WASAPI output settings. I have mine set to 230 msec.
[quote name='teddy2' date='Jul 16 2010, 13:25' post='714173
I am certainly no expert here. All I can suggest is to install the realtek drivers and decrease the buffer value in the WASAPI output settings. I have mine set to 230 msec.
[/quote]
I installed the Realtek drivers and there was no change. I changed the buffer value to <= 500msecs and got white noise out of the speakers.
I am trying to use WASAPI with my ATI card.
My receiver supports 16, 20 and 24 bit files but the ATI card is forcing me to pick one sampling rate for all audio.
Everything seems fine with standard CD audio.
I get an unexpected error (0x800700F1) "hardware error" with my multi-channel WAV files.
These files are standard 5.1 24 bit 96kHz audio and play fine without the WASAPI component installed.
Unlike DirectSound output, the WASAPI output passes audio to the soundcard
as is - i.e. it won't downmix or upmix channels, convert the samplerate or change the bit depth. Thus it is that, if your soundcard hasn't been set-up to output 5.1 24 bit 96kHz audio, you'll have an error when attempting to pass audio of that specification to the card.
To work-around this, try to change the soundcard settings to match the format of the files. If that isn't possible, then use DSPs such as "Convert 5.1 to stereo" and "Resampler" to modify the audio format, and be sure to use the correct bit depth settings in the preferences. If all else fails, do reconsider whether or not you actually
need to use the WASAPI output.
Hope this helps .
Unlike DirectSound output, the WASAPI output passes audio to the soundcard as is - i.e. it won't downmix or upmix channels, convert the samplerate or change the bit depth. Thus it is that, if your soundcard hasn't been set-up to output 5.1 24 bit 96kHz audio, you'll have an error when attempting to pass audio of that specification to the card.
To work-around this, try to change the soundcard settings to match the format of the files. If that isn't possible, then use DSPs such as "Convert 5.1 to stereo" and "Resampler" to modify the audio format, and be sure to use the correct bit depth settings in the preferences. If all else fails, do reconsider whether or not you actually need to use the WASAPI output.
Hope this helps .
Thanks for the response, but I don't think this makes anything clearer for me.
1) My audio card (ATI) only has a single setting for sampling rate and it is described as the maximum.
2) All my audio files seem to be upconverted to this driver rate if they are not already recorded in that format.
3) With the WASAPI plug-in, I can play CD tracks at the correct sampling rate.
4) I still cannot play the 96kHz tracks with WASAPI.
If I change the sound card setting I think everything will work just fine.
However it is really inconvenient to have to do that.
What sound card do you have? You may have to bite the bullet and change the setting.
I've got a weird problem with this output plugin on my Win7 x64 system using an ATI 5670 and the Realtek ATI HDMI driver. The sound playback is perfect, but when I hit pause, I get a period of silence equal to the (buffer length - ~100ms), followed by the last 100ms or so of audio that was played. This repeats over and over until I hit play again. Changing the buffer length only seems to alter the amount of "silence" before the sound plays again.
Hi all. This my first post here.
I am having the exact same problem as described by Mordred. The WASAPI plugin works great in all respects except when I pause the audio I get the same repeating audio as he described. I also have Windows 7 x64 using ATI4850 and the Realtek ATI HDMI driver. Has anyone else had this problem or found a fix?
I love the WASAPI function and it is only a minor nuisance not to be able to use the PAUSE button, but it is a nuisance.
My new network card greatly improved the problem with DS output, but it would return after a period of time. I have to periodically kill my networking application which is a pain and less than ideal.
I went back to WASAPI and was still having the repeated sound bug 99% of the time I paused. It also wouldn't go away when I had the sound output paused and then hit stop. I was constantly having to mute the sound on my receiver to avoid driving myself nuts. HOWEVER, last week, I figured out how to make this stop. I discovered (by accidentally hitting the wrong button on my remote when trying to mute) that the WASAPI plugin will not make any audio output if the position in the track is changed WHILE the song is paused. 5 minutes later I had adjusted my pause macro to have foobar pause, skip backward 1 second and then skip forward 1 second. My pauses are completely quiet now. It seems to pause and resume at the exact point in playback too, which is perfect.
I set this fix up using EventGhost and my remote control, but for those people who use the mouse to control playback I'm sure it'd be really easy to alter your pause button code to pause and then jump backward and then jump forward.
I found a bug with WASAPI using Win 7 32-but and Soundblaster Audigy 2 ZS with Foobar2000 1.1.1. The problem is that if I have replaygain in use track / apply gain, it sounds like WASAPI s not in the loop. If I turn off replaygain processing, then the sound is better like WaSAPI is in the loop. Can this be fixed please? I've had to resort to the Kernal Streaming plugin that seems to work.
I set this fix up using EventGhost and my remote control, but for those people who use the mouse to control playback I'm sure it'd be really easy to alter your pause button code to pause and then jump backward and then jump forward.
This is great news that a solution has been found. How would I go about altering the pause button code? Sorry, I am not much of a programmer, although I will try.
Thanks.
I found a bug with WASAPI using Win 7 32-but and Soundblaster Audigy 2 ZS with Foobar2000 1.1.1. The problem is that if I have replaygain in use track / apply gain, it sounds like WASAPI s not in the loop. If I turn off replaygain processing, then the sound is better like WaSAPI is in the loop. Can this be fixed please? I've had to resort to the Kernal Streaming plugin that seems to work.
ReplayGain scales the volume digitally. It is unlikely to affect the sound quality noticeably. Of course, at the maximum bit depth of 16 supported by your sound card. (24-bit is only supported by the Audigy series under specific circumstances, unless you're using the kX drivers, in which case I don't know.) Thus, ReplayGain may reduce the noise floor a bit, but again, it shouldn't be noticeable.
Also, it shouldn't really be possible to hear the difference between DirectSound and WASAPI, when using the same settings. Unless with your sound card that it somehow bypasses the EAX processing or other processing effects of the sound card.
I found a bug with WASAPI using Win 7 32-but and Soundblaster Audigy 2 ZS with Foobar2000 1.1.1. The problem is that if I have replaygain in use track / apply gain, it sounds like WASAPI s not in the loop. If I turn off replaygain processing, then the sound is better like WaSAPI is in the loop. Can this be fixed please? I've had to resort to the Kernal Streaming plugin that seems to work.
ReplayGain scales the volume digitally. It is unlikely to affect the sound quality noticeably. Of course, at the maximum bit depth of 16 supported by your sound card. (24-bit is only supported by the Audigy series under specific circumstances, unless you're using the kX drivers, in which case I don't know.) Thus, ReplayGain may reduce the noise floor a bit, but again, it shouldn't be noticeable.
Also, it shouldn't really be possible to hear the difference between DirectSound and WASAPI, when using the same settings. Unless with your sound card that it somehow bypasses the EAX processing or other processing effects of the sound card.
Well, to my ears it does sound different and not as good with WASAPI and replaygain on. The problem is that I would like others to give this a go as well.
This is great news that a solution has been found. How would I go about altering the pause button code? Sorry, I am not much of a programmer, although I will try.
Thanks.
Sorry, I didn't get notified that you had responded for some reason. Anyway, altering the pause button code is probably simple if you're using something like columns UI. I have no idea how you'd go about doing it for the default UI, or even if it's possible.
In my columns UI theme I went and found where the play/pause button was. It was displaying an image, and then at the end of the line it had the command to execute listed like this: ",COMMAND:'Playback/Play or Pause',"
I replaced the section in between the commas with this line:
",COMMAND:'Playback/Play or Pause',COMMAND:'Playback/Seek/Back by 1 second';COMMAND:'Playback/Seek/Ahead by 1 second',"
and now it works perfectly. Hope that will help you.
This is great news that a solution has been found. How would I go about altering the pause button code? Sorry, I am not much of a programmer, although I will try.
Thanks.
Sorry, I didn't get notified that you had responded for some reason. Anyway, altering the pause button code is probably simple if you're using something like columns UI. I have no idea how you'd go about doing it for the default UI, or even if it's possible.
In my columns UI theme I went and found where the play/pause button was. It was displaying an image, and then at the end of the line it had the command to execute listed like this: ",COMMAND:'Playback/Play or Pause',"
I replaced the section in between the commas with this line:
",COMMAND:'Playback/Play or Pause',COMMAND:'Playback/Seek/Back by 1 second';COMMAND:'Playback/Seek/Ahead by 1 second',"
and now it works perfectly. Hope that will help you.
Thanks again for the info. I did figure out that I needed columns UI. I wasn't sure how to insert multiple commands; ie Pause, ahead, back.
This is great news that a solution has been found. How would I go about altering the pause button code? Sorry, I am not much of a programmer, although I will try.
Thanks.
Sorry, I didn't get notified that you had responded for some reason. Anyway, altering the pause button code is probably simple if you're using something like columns UI. I have no idea how you'd go about doing it for the default UI, or even if it's possible.
In my columns UI theme I went and found where the play/pause button was. It was displaying an image, and then at the end of the line it had the command to execute listed like this: ",COMMAND:'Playback/Play or Pause',"
I replaced the section in between the commas with this line:
",COMMAND:'Playback/Play or Pause',COMMAND:'Playback/Seek/Back by 1 second';COMMAND:'Playback/Seek/Ahead by 1 second',"
and now it works perfectly. Hope that will help you.
What version Columns UI are you using?
Hello,
Windows 7 x64, Lynx L22, Foobar 1.1, Wasapi plugin 2.1.
44.1 kHz, 2 channels, 16bit works ok, but
192 kHz, 2 channels, 24bit: Unrecoverable playback error: Device not functioning (0x8007001F)
Any idea?
Hello,
Windows 7 x64, Lynx L22, Foobar 1.1, Wasapi plugin 2.1.
44.1 kHz, 2 channels, 16bit works ok, but
192 kHz, 2 channels, 24bit: Unrecoverable playback error: Device not functioning (0x8007001F)
Any idea?
Are you using the digital output channels or analog? It looks like your card only supports 192 kHz when using analog output.
I am using analog (AES) output... In ASIO foobar plugin works every frequence... so i think it should something to do with wasapi plugin (not shure)..
Is there any setup window for WASAPI? Beacuase I change PCI slot for Lynx, and now I cannot play anything through WASAPI.. Ive got Unrecoverable playback error: Device not functioning (0x8007001F)
What about a wasapi NON exclusive plugin, to replace the directsound output. Since the directsound is obsolete and it's "translated" wasapi output in real time in vista or win7, the directsound is an unnecessary step, and the non exclusive native wasapi output also gives much lower latency than the ds output.
Sanyigz, you're mistaken/misinformed on multiple issues.
- DirectSound is necessary because not all hardware/drivers is capable of multiple-WASAPI hardware mixing.
- DirectSound APIs are by no mean obsolete, it has just been redesigned in Vista to avoid the multiple design issues that XP's kmixer had.
- For normal playback purposes, higher latency is better as the buffer provides protection against skipping.
Sanyigz, you're mistaken/misinformed on multiple issues.- DirectSound is necessary because not all hardware/drivers is capable of multiple-WASAPI hardware mixing.
- DirectSound APIs are by no mean obsolete, it has just been redesigned in Vista to avoid the multiple design issues that XP's kmixer had.
- For normal playback purposes, higher latency is better as the buffer provides protection against skipping.
i talked about non exclusive wasapi. The non exclusive wasapi is same as the direct sound, no need for hardware mixing, but it skips the directsound-> wasapi conversion on vista/7(because from vista, the ds in only emulated, not native), so it needs less cpu time, less latency, but same funcionality as ds.
the buffer is a different topic, it is not depends on output... you can set 5 sec buffer on wasapi exclusive, or asio too.
BTW this not means that the full DS output should be removed, the ds, wasapi, and wasapi exclusive can exist at same time, it's just a plugin as asio or wasapi exclusive.
vista/7 audio stack (http://en.wikipedia.org/wiki/WASAPI#Audio_stack_architecture)
So basically, you want Peter to spend his time implementing a new feature which bring nothing new in functionality and supposedly (no proven documentation) use less CPU time and has less latency. Considering that how much CPU time foobar uses now compared to current processor, is that productive? Not to mention, as you implied in your post, regardless of the cause latency does not affect audio playback.
So basically, you want Peter to spend his time implementing a new feature which bring nothing new in functionality and supposedly (no proven documentation) use less CPU time and has less latency. Considering that how much CPU time foobar uses now compared to current processor, is that productive? Not to mention, as you implied in your post, regardless of the cause latency does not affect audio playback.
i don't want, but it would be good... BTW sooner or later, the ds emulation will be removed too from newer win releases.
If the exclusive mode is working, then this is the same api. so maybe the implementation of this, is just a simple switch (exclusive or non exclusive switch)...
Is there any setup window for WASAPI? Beacuase I change PCI slot for Lynx, and now I cannot play anything through WASAPI.. Ive got Unrecoverable playback error: Device not functioning (0x8007001F)
Anyone has idea?
From some MS sources it seems, that in W7 (unlike WV, but i'm not sure in that) the audio stream played back in shared mode can also reach low latency through "pulling" the data by one pipeline component from the previous one (if all dsps are disabled it is mostly between driver and audio engine). The latency isn't crucial for normal audio playback, but the advantage in this pull mode mechanism seems in better glitch/skip resistance.
It seems something similar can be applied in exclusive mode also, where it can be even more helpful (e.g. WaveRT).
So i wanted just to ask which "mode" is used by fb2k wasapi output component, pull or push (i suppose here it is up to audio app to control the data amount, that it will push to the driver) mode?
This thread seems to be dead or ignored. It wouldn't be bad to add the operating mode of this plugin (see my previous post) into fb2k wiki pages, because this info could be quite essential for some kind of audio peripherals (e.g. usb devices). Maybe this plugin is designed to allow fb2k to work only (what would be fine) in pull (event) mode, but Peter doesn't mention it nowhere and moreover he doesn't provide the source code, pity.
Anyway, i've tried to distinguish the behavior between these two modes with process explorer and NAudio library through its demo application, the difference (among others, e.g. buffer size set) is in CPU cycles used, builded audio endpoint uses them in much lesser extend in the case of pull (event) mode. When comparing it with fb2k and wasapi, according the cycles it seems the pull mode is used, but this couldn't be taken as a proof, of course.
Peter or anyone, who knows, please add the info about it in the wiki pages or to this thread at least, thanks.
I went back to WASAPI and was still having the repeated sound bug 99% of the time I paused. It also wouldn't go away when I had the sound output paused and then hit stop. I was constantly having to mute the sound on my receiver to avoid driving myself nuts. HOWEVER, last week, I figured out how to make this stop. I discovered (by accidentally hitting the wrong button on my remote when trying to mute) that the WASAPI plugin will not make any audio output if the position in the track is changed WHILE the song is paused. 5 minutes later I had adjusted my pause macro to have foobar pause, skip backward 1 second and then skip forward 1 second. My pauses are completely quiet now. It seems to pause and resume at the exact point in playback too, which is perfect.
I just joined the WASAPI + ATI HDMI out bandwagon this week and I have the same problem. Is it possible for the original component author to fix this in the component? The pause-jump-back-and-forth is a hack and I can't map global hotkeys to multiple actions to do this. I've mapped my paused key to simply "stop" for now.
This thing is great. Thanks for saving us from the Windows Mixer!
I went back to WASAPI and was still having the repeated sound bug 99% of the time I paused. It also wouldn't go away when I had the sound output paused and then hit stop. I was constantly having to mute the sound on my receiver to avoid driving myself nuts. HOWEVER, last week, I figured out how to make this stop. I discovered (by accidentally hitting the wrong button on my remote when trying to mute) that the WASAPI plugin will not make any audio output if the position in the track is changed WHILE the song is paused. 5 minutes later I had adjusted my pause macro to have foobar pause, skip backward 1 second and then skip forward 1 second. My pauses are completely quiet now. It seems to pause and resume at the exact point in playback too, which is perfect.
I just joined the WASAPI + ATI HDMI out bandwagon this week and I have the same problem. Is it possible for the original component author to fix this in the component? The pause-jump-back-and-forth is a hack and I can't map global hotkeys to multiple actions to do this. I've mapped my paused key to simply "stop" for now.
My guess is that the component author feels it's working perfectly, and that the issues are on users' systems. I think a hack is the best you can hope for.
On the plus side, I found out a couple months ago that after I installed Win 7 SP1 my DS plays fine with no skipping. I no longer have to use WASAPI at all which is nice.
My guess is that the component author feels it's working perfectly, and that the issues are on users' systems. I think a hack is the best you can hope for.
On the plus side, I found out a couple months ago that after I installed Win 7 SP1 my DS plays fine with no skipping. I no longer have to use WASAPI at all which is nice.
Which is probably the situation: something specific to HDMI out over ATI video card. DS works for me too except that Windows insists on sending stereo input as 5.1 out: two channels of audio with 3 channels of silence.
I went back to WASAPI and was still having the repeated sound bug 99% of the time I paused. It also wouldn't go away when I had the sound output paused and then hit stop. I was constantly having to mute the sound on my receiver to avoid driving myself nuts. HOWEVER, last week, I figured out how to make this stop. I discovered (by accidentally hitting the wrong button on my remote when trying to mute) that the WASAPI plugin will not make any audio output if the position in the track is changed WHILE the song is paused. 5 minutes later I had adjusted my pause macro to have foobar pause, skip backward 1 second and then skip forward 1 second. My pauses are completely quiet now. It seems to pause and resume at the exact point in playback too, which is perfect.
I just joined the WASAPI + ATI HDMI out bandwagon this week and I have the same problem.
I have exactly the same issue, and yes, it's ATI HDMI. There is clearly a problem, are here any chances that it will be fixed? Skipping hack doesn't seem to work for me...
Is there any setup window for WASAPI? Beacuase I change PCI slot for Lynx, and now I cannot play anything through WASAPI.. Ive got Unrecoverable playback error: Device not functioning (0x8007001F)
I had the same message error with my Lynx L22 on win7 64, and i set buffer lenght to 500ms, so it works fine, but if i set higher than 500ms, i have this message error like you.
Sorry to bump such an old thread, but I got the same error ("Unrecoverable playback error: Unknown error (88890002)"), but I can verify the track without problems, or scan for the replay-gain, and also play it with MPC without problems. Never had this problem before, must be the WASAPI switch. Got this problem on all mono tracks. Can't you add a functionality that switches a stereo duplication on if you want to play mono through WASAPI?
What a weird error: AUDCLNT_E_ALREADY_INITIALIZED
What a weird error: AUDCLNT_E_ALREADY_INITIALIZED
You get that, for one, if you try to do something that has to be done before the client initialize, but do it after.
When I don't use any DSP at all and play stereo music, I get sound coming from my surround speakers. Any idea why?
I'm using WASAPI with a Xonar Essence STX II 7.1 and I made sure no surround or stereo upmix is enabled in the Xonar Control Center.
Assuming you are using WASAPI in shared mode: Is your system audio output set to 2 channel/stereo for your device?
edit: I don't know if the "Xonar Control Center" you mentioned actually replaces the default windows 10 sound settings.
edit2: actually forget about what I wrote as it seems to be just bit depth and sampling rate you set there. You could try WASAPI in exclusive mode with allowing applications having sole control over the device in the sound settings.
Hi The Link, I'm running WASAPI in exclusive mode. My audio is set to 7.1 speakers. Seems like when there are surround speakers WASAPI automatically copies the front left and right to the surrounds?
I‘m sure that WASAPI in exclusive mode sends the audio data exactly as the source is (given no dsps are applied) to the device. Any alteration must be done by either the system or the device driver/software.
I have installed foobar2000_v1.6.7_beta_4 and I get the following error (image). However everything works normally. If I install version 1.6.6 the error disappears. Does anyone know anything about this matter?
@ josemescud
Read it carefully
Don't need WASAPI output support (foo_out_wasapi), so please delete it
foobar2000 change log 1.6.7
https://www.foobar2000.org/changelog
>Built-in WASAPI exclusive output.
@ josemescud
Read it carefully
Don't need WASAPI output support (foo_out_wasapi), so please delete it
foobar2000 change log 1.6.7
https://www.foobar2000.org/changelog
>Built-in WASAPI exclusive output.
Thanks.
I have removed the Wasapi component.
Now I have 2 Device for my DAC:
-
Default: Speakers (YOUNG MKIII UAC2) [exclusive]-
Speakers (YOUNG MKIII UAC2) [exclusive]What is the difference between the 2. Which is more convenient to choose?
Default: DAC Driver [exclusive] → WASAPI exclusive mode
Please check for yourself
https://lnx.m2tech.biz/wp-content/uploads/2017/06/Young-MkIII-User-Manual-PrA.pdf
Default: DAC Driver [exclusive] → WASAPI exclusive mode
Please check for yourself
https://lnx.m2tech.biz/wp-content/uploads/2017/06/Young-MkIII-User-Manual-PrA.pdf
Thanks.
I have installed Beta 5 on a DELL laptop with S.O. Windows 10 Pro 21H1
I don't have a sound system connected. I have the music in the internal DSD of the pc.
So far I have used Device: WASAPI (push): Speakers / Headphones (Realtek Audio) and everything sounded great.
I have changed the Device: Default: Speakers / Headphones (Realtek Audio) [exclusive] and it has been a disaster. Only noise is reproduced at maximum volume.
I do not know if there is something I am doing wrong or is that the version has debugging and adjustments left.
------------------------
I have also installed it on my Intel NUC with S.O. Windows 10 Pro 21H1
I have it connected to a Marshall Speaker by RCA cable
I changed the Device: WASAPI (push): Lautsprecher (Realtek® Audio) to Default: Lautsprecher (Realtek® Audio) [exclusive]
The sound is good, but the problem is that sporadically, when tagging from the Playlist View (properties) the sound gets stuck and farts. Reboot and everything OK.
I have the doubt of which is the Device that I have to choose:
- Default: Lautsprecher (Realtek® Audio) [exclusive]
- Lautsprecher (Realtek® Audio) [exclusive]
What is the difference between the two?
I also have it connected to a Young MKIII DAC via USB
I changed the Device: WASAPI (event): Speakers (YOUNG MKIII-BB09 Stereo) to Default: Speakers (YOUNG MKIII-BB09 Stereo) [exclusive]
The sound is also good and I have only noticed that, sporadically, when tagging from the Playlist View (properties) the sound stops for a moment while the metadata is being recorded.
Here I also have the doubt of which is the Device that I have to choose:
- Default: Speakers (YOUNG MKIII-BB09 Stereo) [exclusive]
- Speakers (YOUNG MKIII-BB09 Stereo) [exclusive]
What is the difference between the two?
It seems the current beta using WASAPI does not support multichannel:
Unrecoverable playback error: Unsupported stream format: 96000 Hz / 24-bit / 4 channels (0x603)
1.6.6 with the WASAPI plugin can play it.
It seems the current beta using WASAPI does not support multichannel:
Unrecoverable playback error: Unsupported stream format: 96000 Hz / 24-bit / 4 channels (0x603)
1.6.6 with the WASAPI plugin can play it.
Just wanted to say this was fixed somewhere between beta 8 and beta 15 and Beta 15 is working quite well.