Skip to main content

Topic: WASAPI output component version 3.0 final (Read 122532 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • db1989
  • [*][*][*][*][*]
  • Global Moderator
WASAPI output component version 3.0 final
Version 3.2.3:

Quote
WASAPI output support
By: Peter
Adds Windows Audio Session API exclusive mode output support, allowing bit-exact output and muting all other sounds. Windows Vista SP1 or newer required.

3.2 version highlights:
• Different default hardware buffer size for event mode - known to work better with specific soundcards.
• Different detection of stream formats supported by the device - should improve compatibility with certain SPDIF receivers.
3.2.1 version highlights:
• Fixed a crash bug from version 3.2.
Quote
3.2.2 version highlights:
* Compatibility improvements - removed the advanced preferences switch; the correct behavior is now determined automatically.
3.2.3 version highlights:
* Fixed 3.2.3 regression that made certain channel layouts not work.

Download: use the link on that page, as it is dynamically generated
Documentation: http://wiki.hydrogenaudio.org/index.php?ti.../foo_out_wasapi

[original post below]



In case it generates a lot of discussion as its pre-releases did, I think it may be best that we try to keep things in one thread. Worth a try, anyway!

Quote
2012-09-02
The long-awaited update of the WASAPI output component has been released.
Component page

Quote
WASAPI output support
By: Peter
Adds Windows Audio Session API exclusive mode output support, allowing bit-exact output and muting all other sounds. Windows Vista SP1 or newer required.

3.0 version highlights:
* Faster volume control
* 32bit integer mode if 32bit floating-point is not supported by the device
* Operates in two different modes, regular and event-driven - the latter seems to be more compatible with USB devices, but not supported by some other devices.
* Separate process sandbox for improved stability.

Current version
3.0, released on 2012-09-02

Links
Download
Documentation
  • Last Edit: 12 March, 2013, 05:15:10 AM by db1989

  • SoNic67
  • [*][*][*]
WASAPI output component version 3.0 final
Reply #1
Thanks! I am using it now and I cannot find any faults...

WASAPI output component version 3.0 final
Reply #2
Thanks for this. 

  • monstrum
  • [*]
WASAPI output component version 3.0 final
Reply #3
Thanks ! Using "Event mode" on HRT Music Streamer II firmware 2.2 within foobar 1.1.14a/W7HP64bit, 1030 msec  buffer, 24bit. Works perfectly.

  • Porcus
  • [*][*][*][*][*]
WASAPI output component version 3.0 final
Reply #4
Is the WASAPI component supposed to work with ReplayGain compensation applied? I've hit Apply gain and prevent clipping according to peak (album mode), and fb2k sure as hell doesn't prevent clipping. The album in question has positive gain. I have a +0.0 for albums with RG info. Problem appears to be independent of push vs event mode chosen.

Furthermore, it often simply refuses to play, after it has been fed one of these albums. Even switching over to DS does not always work – I might have to restart foobar2000.


Using: 1.15 beta 1 with WASAPI 3.0.  It is a fresh computer, so I have not tried any older version of the component.
  • Last Edit: 09 September, 2012, 07:00:05 AM by Porcus

  • felimz
  • [*][*]
WASAPI output component version 3.0 final
Reply #5
I am getting a possible bug when performing the following steps:

1) Play a song

2) Click on Playback > Stop

3) Adjust system volume via taskbar icon so that the volume change sound gets triggered

4) Immediately try to resume playback (within 1 second after sound finishes playing)

5) Get playback error: "Unrecoverable playback error: Device in use"

Also, it would be great if the component would allow for sounds to be played while the sound is "Paused" versus "Stopped."

System Specs: foobar 1.1.14a, Win 7 x64, component version 3.0 final

Edit: Exclusive Mode in "Speaker Properties" is set to "Give exclusive mode applications priority," which may be the reason this is occurring.
  • Last Edit: 09 September, 2012, 04:25:54 PM by felimz

  • miyagi1
  • [*]
WASAPI output component version 3.0 final
Reply #6
Event mode sounds great. I didn't think there would be such a big difference between the two modes.

  • db1989
  • [*][*][*][*][*]
  • Global Moderator
WASAPI output component version 3.0 final
Reply #7
Can you qualify that claim according to #8 of the terms of service?

  • Porcus
  • [*][*][*][*][*]
WASAPI output component version 3.0 final
Reply #8
Is the WASAPI component supposed to work with ReplayGain compensation applied? I've hit Apply gain and prevent clipping according to peak (album mode), and fb2k sure as hell doesn't prevent clipping.


Update: might be a quirky USB device. I have at one instance managed to provoke it to clip on a file without ReplayGain. But not (yet) after a fresh restart.

  • WarZard-X
  • [*]
WASAPI output component version 3.0 final
Reply #9
Should I use push mode or event mode for an onboard soundcard?
Why is the hardwarebuffer 200ms for push mode and only 10ms for event mode?

  • lumi
  • [*]
WASAPI output component version 3.0 final
Reply #10
im having issues with foobar 1.1.15 and wasapi 3 with my usb dac it just doesnt work anymore

was ok in 1.1.13 and earlier 2.1 wasapi

it now tries to start playing n locks like it cant find the place to start playing

i uninstalled foobar and the dacs driver and reinstalled everything and still no joy

its a recent install of win 7 also ran fidleizer on it

i put the older wasapi 2.1 component back in and it works
  • Last Edit: 25 September, 2012, 07:24:50 PM by lumi

  • Kohlrabi
  • [*][*][*][*][*]
  • Global Moderator
WASAPI output component version 3.0 final
Reply #11
its a recent install of win 7 also ran fidleizer on it
You might want to avoid using useless scam software like that, which affects system performance and stability.

You probably tried both "push" and "event" mode of WASAPI 3.0?
  • Last Edit: 26 September, 2012, 03:25:08 AM by Kohlrabi
It's only audiophile if it's inconvenient.

  • lumi
  • [*]
WASAPI output component version 3.0 final
Reply #12
its a recent install of win 7 also ran fidleizer on it
You might want to avoid using useless scam software like that, which affects system performance and stability.

You probably tried both "push" and "event" mode of WASAPI 3.0?


i did try both yes...why do u say? is there a issue with doing that? could u be a bit more helpful and expand on that statement?

anyways this isnt about fidleizer. i can take that outta the equation anyways.

the older wasapi 2.1 works when put back in, could u expand on your statement of .. 'you prob tried both' instead of leaving me hanging thinking yes and and ....... what effect does that have? is it a known issue? etc
  • Last Edit: 26 September, 2012, 10:19:19 AM by lumi

  • Xin-Hong
  • [*]
WASAPI output component version 3.0 final
Reply #13
It seems there is a little cosmetic problem: WASAPIHost64 instead of foobar2000



Using foobar2000 on Win7 x64

  • hkwong
  • [*]
WASAPI output component version 3.0 final
Reply #14
I have this bug also. When foobar is playing a song, and i double click other song, it hangs immediately. I see a process something like wasapihost64.exe, and  cannot stop this process. I need to restart the computer and change back to V2.1.

  • Peter
  • [*][*][*][*][*]
  • Administrator
WASAPI output component version 3.0 final
Reply #15
If you cannot stop the process, it's stuck in a driver call; therefore it's the your driver that's broken. Also, posting exact info about your which exact soundcard you're using would be very helpful.

  • e2012
  • [*]
WASAPI output component version 3.0 final
Reply #16
I can report after a few days usage that the new version works perfectly for me on Windows 7 x64. Both event and push modes seem flawless driving a Benchmark DAC through USB.

One difference I noted between v2.1 and v3 is that I could not increase the buffer size much above 1000mS using v2.1, but its full range is functional for me in v3.0. This is useful for handling imperfect data delivery systems (e.g. a Samba share on my NAS.) So, although v2.1 worked for me, I see v3.0 as a real improvement. Many thanks to Peter.

I can see the effect noted by Xin-Hong above but I don't see it as a bug. As described by Peter the WASAPI code now runs in a separate process, so that is what connects to the output device and therefore is displayed by Microsoft in the mixer window. If you are using WASAPI you could not use the mixer so the fact that it displays the name of the host process that has exclusive access to the output device is not really important. It might be nice if Microsoft indicated in some way that the whole mixer channel is non-functional once an exclusive mode application has claimed the output device.

  • Bojamijams
  • [*]
WASAPI output component version 3.0 final
Reply #17
Same issue as above.  Cannot play files anymore with either WASAPI mode on my USB DAC. 

The play speed increases at 1/10th of the speed.  IE. After 10 seconds I see the timer go from 0:00 to 0:01.

Going to revert back to 2.1

WASAPI output component version 3.0 final
Reply #18
what USB Dac are you using?
Who are you and how did you get in here ?
I'm a locksmith, I'm a locksmith.

  • Bojamijams
  • [*]
WASAPI output component version 3.0 final
Reply #19
Anedio D1.

However its fed by a USB-to-COAX digital interface (Audio-gd DI-DSP) which uses the Tenor TE8802 chip (asynchronous USB)

  • hkwong
  • [*]
WASAPI output component version 3.0 final
Reply #20
If you cannot stop the process, it's stuck in a driver call; therefore it's the your driver that's broken. Also, posting exact info about your which exact soundcard you're using would be very helpful.


My system config
win7 x64
Creative 0404usb
Foobar 1.1.5

i hope the information is enough.

  • Anakunda
  • [*][*][*][*][*]
WASAPI output component version 3.0 final
Reply #21
Maybe I have overlooked something but actually neither of the two playback methods doesnot produce any sound when trying to play SACD album (88.2kHz / 2channels / 24bps), although my soundcard is setup to play at 96kHz and 24bit:




I'm getting "Unrecoverable playback error: Unsupported stream format: 88200 Hz / 24-bit / 2 channels" message.
At standard CD album both method seems to play OK however.  Is this due some missing component in my system or hardware limitation of my soudcard? I'm having Realtek HD audio.
  • Last Edit: 05 October, 2012, 02:12:23 AM by Anakunda

  • Peter
  • [*][*][*][*][*]
  • Administrator
WASAPI output component version 3.0 final
Reply #22
Sounds like your soundcard does not support 88200Hz and you need to resample, or simply use DirectSound which resamples unsupported formats automatically for you.

See also: http://wiki.hydrogenaudio.org/index.php?ti...g_Windows_Mixer
  • Last Edit: 05 October, 2012, 03:26:39 AM by Peter

  • luigidox
  • [*]
WASAPI output component version 3.0 final
Reply #23
If you cannot stop the process, it's stuck in a driver call; therefore it's the your driver that's broken. Also, posting exact info about your which exact soundcard you're using would be very helpful.


My system config
win7 x64
Creative 0404usb
Foobar 1.1.5

i hope the information is enough.


I'm using the same gear and hv exactly the same problem. I had to switch back to WASAPI 2.1.

Surprisingly, my old Harman Kardon soundsticks (USB) works with WASAPI 3.0. I think it is a EMU 0404 driver issue.

  • luigidox
  • [*]
WASAPI output component version 3.0 final
Reply #24
I'm considering to upgrade to mytek 192 DSD DAC. Does WASAPI 3.0 work with it ?