IPB

Welcome Guest ( Log In | Register )

> foobar2000 General Forum Rules

This is NOT a tech support forum.
Tech support questions go to foobar2000 Tech Support forum instead.

See also: Hydrogenaudio Terms of Service.

5 Pages V   1 2 3 > »   
Reply to this topicStart new topic
WASAPI output component version 3.0 final, 2013-03-09: v3.2.3
db1989
post Sep 2 2012, 23:43
Post #1





Group: Super Moderator
Posts: 5275
Joined: 23-June 06
Member No.: 32180



Version 3.2.3:

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! wink.gif

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

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


This post has been edited by db1989: Mar 12 2013, 10:15
Go to the top of the page
+Quote Post
SoNic67
post Sep 3 2012, 00:54
Post #2





Group: Members
Posts: 108
Joined: 3-February 11
Member No.: 87877



Thanks! I am using it now and I cannot find any faults...
Go to the top of the page
+Quote Post
jologsmaster
post Sep 5 2012, 13:19
Post #3





Group: Members
Posts: 9
Joined: 17-December 11
Member No.: 95853



Thanks for this. smile.gif
Go to the top of the page
+Quote Post
monstrum
post Sep 8 2012, 14:13
Post #4





Group: Members
Posts: 1
Joined: 8-September 12
Member No.: 102988



Thanks ! Using "Event mode" on HRT Music Streamer II firmware 2.2 within foobar 1.1.14a/W7HP64bit, 1030 msec buffer, 24bit. Works perfectly.
Go to the top of the page
+Quote Post
Porcus
post Sep 9 2012, 11:59
Post #5





Group: Members
Posts: 1903
Joined: 30-November 06
Member No.: 38207



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.

This post has been edited by Porcus: Sep 9 2012, 12:00


--------------------
One day in the Year of the Fox came a time remembered well
Go to the top of the page
+Quote Post
felimz
post Sep 9 2012, 21:21
Post #6





Group: Members
Posts: 68
Joined: 15-February 09
Member No.: 67003



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.

This post has been edited by felimz: Sep 9 2012, 21:25
Go to the top of the page
+Quote Post
miyagi1
post Sep 10 2012, 01:47
Post #7





Group: Members
Posts: 6
Joined: 24-March 07
Member No.: 41800



Event mode sounds great. I didn't think there would be such a big difference between the two modes.
Go to the top of the page
+Quote Post
db1989
post Sep 10 2012, 02:37
Post #8





Group: Super Moderator
Posts: 5275
Joined: 23-June 06
Member No.: 32180



Can you qualify that claim according to #8 of the terms of service?
Go to the top of the page
+Quote Post
Porcus
post Sep 14 2012, 00:41
Post #9





Group: Members
Posts: 1903
Joined: 30-November 06
Member No.: 38207



QUOTE (Porcus @ Sep 9 2012, 12:59) *
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.


--------------------
One day in the Year of the Fox came a time remembered well
Go to the top of the page
+Quote Post
WarZard-X
post Sep 22 2012, 18:33
Post #10





Group: Members
Posts: 20
Joined: 11-February 11
From: Switzerland
Member No.: 88089



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?
Go to the top of the page
+Quote Post
lumi
post Sep 26 2012, 00:18
Post #11





Group: Members
Posts: 6
Joined: 25-September 12
Member No.: 103424



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

This post has been edited by lumi: Sep 26 2012, 00:24
Go to the top of the page
+Quote Post
Kohlrabi
post Sep 26 2012, 08:21
Post #12





Group: Super Moderator
Posts: 1081
Joined: 12-March 05
From: Kiel, Germany
Member No.: 20561



QUOTE (lumi @ Sep 26 2012, 01:18) *
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?

This post has been edited by Kohlrabi: Sep 26 2012, 08:25


--------------------
Ceterum censeo Masterdiskem esse delendam.
Go to the top of the page
+Quote Post
lumi
post Sep 26 2012, 14:57
Post #13





Group: Members
Posts: 6
Joined: 25-September 12
Member No.: 103424



QUOTE (Kohlrabi @ Sep 26 2012, 07:21) *
QUOTE (lumi @ Sep 26 2012, 01:18) *
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

This post has been edited by lumi: Sep 26 2012, 15:19
Go to the top of the page
+Quote Post
Xin-Hong
post Sep 30 2012, 18:15
Post #14





Group: Members
Posts: 26
Joined: 4-November 07
From: France
Member No.: 48473



It seems there is a little cosmetic problem: WASAPIHost64 instead of foobar2000



Using foobar2000 on Win7 x64
Go to the top of the page
+Quote Post
hkwong
post Oct 2 2012, 18:01
Post #15





Group: Members
Posts: 6
Joined: 26-July 12
Member No.: 101778



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.
Go to the top of the page
+Quote Post
Peter
post Oct 2 2012, 21:08
Post #16


foobar2000 developer


Group: Admin
Posts: 3292
Joined: 30-September 01
Member No.: 84



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.
Go to the top of the page
+Quote Post
e2012
post Oct 2 2012, 21:36
Post #17





Group: Members
Posts: 1
Joined: 25-September 12
Member No.: 103420



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.
Go to the top of the page
+Quote Post
Bojamijams
post Oct 2 2012, 22:54
Post #18





Group: Members
Posts: 3
Joined: 24-November 10
Member No.: 85995



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 sad.gif
Go to the top of the page
+Quote Post
A_Man_Eating_Duc...
post Oct 3 2012, 03:47
Post #19





Group: Members
Posts: 936
Joined: 21-December 01
From: New Zealand
Member No.: 705



what USB Dac are you using?


--------------------
Who are you and how did you get in here ?
I'm a locksmith, I'm a locksmith.
Go to the top of the page
+Quote Post
Bojamijams
post Oct 4 2012, 02:02
Post #20





Group: Members
Posts: 3
Joined: 24-November 10
Member No.: 85995



Anedio D1.

However its fed by a USB-to-COAX digital interface (Audio-gd DI-DSP) which uses the Tenor TE8802 chip (asynchronous USB)
Go to the top of the page
+Quote Post
hkwong
post Oct 4 2012, 17:32
Post #21





Group: Members
Posts: 6
Joined: 26-July 12
Member No.: 101778



QUOTE (Peter @ Oct 2 2012, 21:08) *
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.
Go to the top of the page
+Quote Post
Anakunda
post Oct 5 2012, 07:11
Post #22





Group: Members
Posts: 473
Joined: 24-November 08
Member No.: 63072



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.

This post has been edited by Anakunda: Oct 5 2012, 07:12
Go to the top of the page
+Quote Post
Peter
post Oct 5 2012, 08:22
Post #23


foobar2000 developer


Group: Admin
Posts: 3292
Joined: 30-September 01
Member No.: 84



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
Go to the top of the page
+Quote Post
luigidox
post Oct 9 2012, 08:37
Post #24





Group: Members
Posts: 2
Joined: 9-October 12
Member No.: 103729



QUOTE (hkwong @ Oct 4 2012, 17:32) *
QUOTE (Peter @ Oct 2 2012, 21:08) *
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.
Go to the top of the page
+Quote Post
luigidox
post Oct 9 2012, 08:40
Post #25





Group: Members
Posts: 2
Joined: 9-October 12
Member No.: 103729



I'm considering to upgrade to mytek 192 DSD DAC. Does WASAPI 3.0 work with it ?

Go to the top of the page
+Quote Post

5 Pages V   1 2 3 > » 
Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 21st October 2014 - 18:43