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.

8 Pages V   1 2 3 > »   
Closed TopicStart new topic
WASAPI plug-in version 3.0 beta [closed], Discussion & feedback
Peter
post May 11 2012, 12:58
Post #1





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



Closed: stable version out - get it here

What is this?
This plug-in adds Windows Audio Session API exclusive mode output support, allowing bit-exact output and muting all other sounds. Windows Vista or newer required.

Notable changes from the 2.x series:
* 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.

New in beta 6:
* Made internal buffer sizes tweakable through Advanced Preferences for hopefully better compatibility.
* Increased internal buffer size for event mode for hopefully better glitch resilience on most systems.
* Changed output mode naming (now: "WASAPI (push)" and "WASAPI (event)").

How to install:
Double-click the .fb2k-component file.
If the above does not load the component into foobar2000, read here.

Preemptive replies:
"I've installed the component using means other than mentioned above and it doesn't work" => no we don't want to hear about it.
"I can't install .fb2k-component because I'm running an old foobar2000 version" => nope we don't want to hear about it either.
"The component doesn't work, I run Windows XP" => WASAPI requires Windows Vista or newer.

Download:
[s]Version 3.0 beta 6[s]

Enjoy.


--------------------
This job would be great if it wasn't for the users.
Go to the top of the page
+Quote Post
Emre
post May 11 2012, 20:02
Post #2





Group: Members
Posts: 14
Joined: 11-January 08
From: Turkey
Member No.: 50385



gave me error on my setup

CODE
Unrecoverable playback error: Unkonwn error (80070057)

Win7 64bit foobar2000 1.1.12 beta 5
Auzentech X-fi Forte
Go to the top of the page
+Quote Post
WarZard-X
post May 13 2012, 18:26
Post #3





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



Thank you! Works perfect with Win7 64bit & foobar2000 1.1.11.
Go to the top of the page
+Quote Post
Sandrine
post May 13 2012, 20:25
Post #4





Group: Members
Posts: 319
Joined: 2-July 10
Member No.: 81991



Added bonus: Now I can bitstream DTS files when using SPDIFER!
Go to the top of the page
+Quote Post
jaro1
post May 13 2012, 22:27
Post #5





Group: Members
Posts: 76
Joined: 22-November 08
Member No.: 62952



Thanks Peter for upgrading the component, i've only one stupid comment as actually there isn't a possibility for me to try it, it wasn't directly mentioned in the changelog and there isn't additional options for the component as it wasn't before also. Does it now use WaveRT if supported by the driver, so it can use low latency pull mode? For your answer, thanks in advance.
Go to the top of the page
+Quote Post
SoNic67
post May 14 2012, 01:03
Post #6





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



Thanks Peter!
It works good on Win7 x64 and E-MU 1820m (I was usually using ASIO). Latest Foobar beta: 1.1.12 Beta 6.
Will it update via normal Foobar way or I need to follow this tread?

This post has been edited by SoNic67: May 14 2012, 01:04
Go to the top of the page
+Quote Post
kode54
post May 14 2012, 03:12
Post #7





Group: Admin
Posts: 4502
Joined: 15-December 02
Member No.: 4082



You will need to download it from this topic until a stable release is uploaded to the components repository.
Go to the top of the page
+Quote Post
Trondis
post May 14 2012, 17:48
Post #8





Group: Members
Posts: 53
Joined: 19-September 06
From: Trondheim
Member No.: 35393



I have been trying to play back dts files through S/PDIF, to have it decoded for surround by my receiver. But I have problems. In theory this should work with this beta of WASAPI plus SPDIFER, shouldn't it?

I have two sound cards: an integrated Realtek card, plus EMU0404. My receiver is connected to the optical out of the Realtek card and the analogue out of the EMU card.

If I set the output to my Realtek card, I get an error message: device is in use. But now to the strange part: If I use the EMU card, I do get perfect 5.1 surround from dts files now. How could that happen?
However, only dts and ac3 files will play back from the EMU card. For all other files I have to switch to Realtek again.

Since I don't use the dts decoder, I can't tag the files, and they won't add to the library. Is there a solution for this?



Go to the top of the page
+Quote Post
Peter
post May 17 2012, 08:10
Post #9





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



QUOTE (Emre @ May 11 2012, 20:02) *
gave me error on my setup

CODE
Unrecoverable playback error: Unkonwn error (80070057)

Win7 64bit foobar2000 1.1.12 beta 5
Auzentech X-fi Forte

Anybody else getting this? Seems to be isolated to Auzentech X-Fi cards, probably a driver bug, there's no E_INVALIDARG (80070057) defined for such scenario in the documentation.

QUOTE (jaro1 @ May 13 2012, 22:27) *
Thanks Peter for upgrading the component, i've only one stupid comment as actually there isn't a possibility for me to try it, it wasn't directly mentioned in the changelog and there isn't additional options for the component as it wasn't before also. Does it now use WaveRT if supported by the driver, so it can use low latency pull mode? For your answer, thanks in advance.

The new WASAPI plug-in is entirely based on "event driven mode", or "pull mode" as you name it.


--------------------
This job would be great if it wasn't for the users.
Go to the top of the page
+Quote Post
Helios61
post May 17 2012, 08:49
Post #10





Group: Members
Posts: 17
Joined: 10-September 08
Member No.: 58108



QUOTE (Peter @ May 17 2012, 09:10) *
Anybody else getting this?

Yes me!

CODE
Unrecoverable playback error: Unkonwn error (80070057)
Win7 64bit foobar2000 1.1.12 beta 6
AMD Radeon HD 6670


Thanks for development of the WASAPI stuff! Best regards,
H
Go to the top of the page
+Quote Post
Alex B
post May 17 2012, 10:21
Post #11





Group: Members
Posts: 1303
Joined: 14-September 05
From: Helsinki, Finland
Member No.: 24472



Thanks. It works for me just fine. Though also the old version worked without problems.

I tested the new component quickly on three different HW setups: Windows 7 32-bit & Terratec DMX 6Fire 24/96 PCI, Windows 7 64-bit & onboard Realtek HD Audio, and out of curiosity Windows 7 64-bit & an old USB connected Philips boombox that precedes Vista (this uses a default Windows 7 device driver).


--------------------
http://listening-tests.freetzi.com
Go to the top of the page
+Quote Post
WarZard-X
post May 17 2012, 11:16
Post #12





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



QUOTE (Alex B @ May 17 2012, 11:21) *
Thanks. It works for me just fine. Though also the old version worked without problems.

I tested the new component quickly on three different HW setups: Windows 7 32-bit & Terratec DMX 6Fire 24/96 PCI, Windows 7 64-bit & onboard Realtek HD Audio, and out of curiosity Windows 7 64-bit & an old USB connected Philips boombox that precedes Vista (this uses a default Windows 7 device driver).

Found an issue.
When browsing the Internet (IE9) while listening to Music with Foobar 1.1.11 & Wasapi Plugin 3.0 Beta, the Music sometimes skips (a few milliseconds noise is heard). This never happened with Wasapi 2.1 Plugin.
I can't reproduce it, it happens occasionally. I'm not sure, but I believe it only happens when a site has heavy loading or Flash Ads are playing.
Go to the top of the page
+Quote Post
pyr0rrzzz
post May 17 2012, 12:41
Post #13





Group: Members
Posts: 52
Joined: 26-January 07
From: Germany
Member No.: 40023



Upgraded, seems to work. (Win Vista 32bit, fb 1.1.11)
Go to the top of the page
+Quote Post
Peter
post May 17 2012, 14:26
Post #14





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



QUOTE (WarZard-X @ May 17 2012, 11:16) *
Found an issue.
When browsing the Internet (IE9) while listening to Music with Foobar 1.1.11 & Wasapi Plugin 3.0 Beta, the Music sometimes skips (a few milliseconds noise is heard). This never happened with Wasapi 2.1 Plugin.
I can't reproduce it, it happens occasionally. I'm not sure, but I believe it only happens when a site has heavy loading or Flash Ads are playing.

Thanks for the report, I was kind of expecting this issue to show up.
Event mode in fact provides worse protection against CPU usage spikes than push mode (as seen in earlier versions of this plug-in) because we queue less data with the driver at a time and must wake up and send more data at regular intervals. However, event mode seems necessary to peacefully cooperate with certain devices, USB ones in particular.
Manually overriding priorities of fb2k & WASAPI host exe processes in task manager might help you. I'll look into other means to improve resistance to system resource usage spikes.


--------------------
This job would be great if it wasn't for the users.
Go to the top of the page
+Quote Post
pyr0rrzzz
post May 17 2012, 20:02
Post #15





Group: Members
Posts: 52
Joined: 26-January 07
From: Germany
Member No.: 40023



Actually, now I noticed that there are lots of artifacts in the form of "crackling", it sounds like an old broken speaker.
Go to the top of the page
+Quote Post
Erich_2
post May 17 2012, 20:52
Post #16





Group: Members
Posts: 239
Joined: 10-September 08
Member No.: 58107



QUOTE (pyr0rrzzz @ May 17 2012, 20:02) *
Actually, now I noticed that there are lots of artifacts in the form of "crackling", it sounds like an old broken speaker.

Here too. Terrible crackling.
Win7 32Bit, Foobar2000 1.1.11, M-Audio Delta Audiophile 2496 (driver V. 6.0.8)
Go to the top of the page
+Quote Post
Moofasa~
post May 18 2012, 02:48
Post #17





Group: Members
Posts: 8
Joined: 9-February 08
Member No.: 51151



I assume this plug-in will only support exclusive mode? I was wondering if there could be any benefits of using wasapi (non-exclusive) over directsound (lower latency maybe?).
Go to the top of the page
+Quote Post
Mr.Grey
post May 18 2012, 08:24
Post #18





Group: Members
Posts: 16
Joined: 20-October 10
Member No.: 84761



QUOTE (Moofasa~ @ May 18 2012, 03:48) *
I assume this plug-in will only support exclusive mode?

working together a foobar2000 (exclusive mode) & other programs (non-exclusive)
with the previous version of plugin this was not possible

LynxTWO card



This post has been edited by Mr.Grey: May 18 2012, 08:25
Go to the top of the page
+Quote Post
Jackal29a
post May 18 2012, 09:23
Post #19





Group: Members
Posts: 36
Joined: 28-May 11
Member No.: 91053



Working fine here (i3 2100, W7 x86), no crackling whatsoever but...

Does this plugin check available sampling rates against the driver reported DS capabilities? I'm asking because like with V 2.1 it doesn't let me play 88.2 or 176.4KHz with my Xonar ST whereas J River plays both sample rates fine on the same configuration using WASAPI.
Also I have another issue with my Musiland 02 Monitor 02US, J River allows 32bit on all sample rates in WASAPI mode but if I try to use 32bit with V 2.1 or 3.0 beta Foobar freezes having to set it to 24bit max in order to play, not that it is a problem but I was wondering why if hardware supports it why the plugin doesn't.

Would it be possible to add a configuration section under "Advanced" where we could tune the plugin to our system?

Cheers
Go to the top of the page
+Quote Post
Moofasa~
post May 18 2012, 13:24
Post #20





Group: Members
Posts: 8
Joined: 9-February 08
Member No.: 51151



QUOTE (Mr.Grey @ May 18 2012, 02:24) *
QUOTE (Moofasa~ @ May 18 2012, 03:48) *
I assume this plug-in will only support exclusive mode?

working together a foobar2000 (exclusive mode) & other programs (non-exclusive)
with the previous version of plugin this was not possible


When I try to use non-exclusive mode I get the error "Unrecoverable playback error: Unsupported stream format: 44100 Hz / 24-bit / 4 channels" (I mirror stereo to the back channels, but the error occurs regardless of sample rate/bit-depth/number of channels). Works perfectly fine in exclusive mode (which is why I asked if this plug-in was ever intended to work in non-exclusive mode).
Go to the top of the page
+Quote Post
Case
post May 18 2012, 16:22
Post #21





Group: Developer (Donating)
Posts: 2136
Joined: 19-October 01
From: Finland
Member No.: 322



QUOTE (Moofasa~ @ May 18 2012, 03:48) *
I assume this plug-in will only support exclusive mode? I was wondering if there could be any benefits of using wasapi (non-exclusive) over directsound (lower latency maybe?).


The component is for exclusive mode only. There is no benefit to develop shared mode component, the output would not be any more direct than with directsound. And latency is irrelevant in an audio player.
Go to the top of the page
+Quote Post
Case
post May 18 2012, 16:26
Post #22





Group: Developer (Donating)
Posts: 2136
Joined: 19-October 01
From: Finland
Member No.: 322



QUOTE (Jackal29a @ May 18 2012, 10:23) *
I'm asking because like with V 2.1 it doesn't let me play 88.2 or 176.4KHz with my Xonar ST whereas J River plays both sample rates fine on the same configuration using WASAPI.
Also I have another issue with my Musiland 02 Monitor 02US, J River allows 32bit on all sample rates in WASAPI mode but if I try to use 32bit with V 2.1 or 3.0 beta Foobar freezes having to set it to 24bit max in order to play, not that it is a problem but I was wondering why if hardware supports it why the plugin doesn't.


It looks like J River does some signal processing (resampling) in its outputs. Your Xonar does not support the sample rates you mentioned (specs). And your Musiland does not support 32-bit output, 24-bits is max (specs).
Go to the top of the page
+Quote Post
Case
post May 18 2012, 16:29
Post #23





Group: Developer (Donating)
Posts: 2136
Joined: 19-October 01
From: Finland
Member No.: 322



QUOTE (WarZard-X @ May 18 2012, 14:47) *
Is it possible that I hear a difference in sound between 2.1 & 3.0 beta?


Version 2.1 uses push mode and it is problematic to at least USB devices. If the buffer is too large the output will have glitching. There shouldn't be any other difference. There may be differences in response speed to volume changing and some glitching on seek/pause caused by driver issues, but normal playback is identical.
Go to the top of the page
+Quote Post
jaro1
post May 18 2012, 16:48
Post #24





Group: Members
Posts: 76
Joined: 22-November 08
Member No.: 62952



Under some hardware configurations low latency pull mode (wavert) won't function properly at all. It has to be supported by hardware and its software driver (WV/7 logo), only in this case there shouldn't be any crackling or skips in sound during playback and this new component will represent an advantage over the old one. For all other configs, push mode (wasapi component 2.1) is the way to go.
This would be good to realize before reporting some unlegitimate problems.
(http://msdn.microsoft.com/en-us/windows/hardware/gg463068.aspx, the part about WaveRT Event-Driven Mode Support)

This post has been edited by jaro1: May 18 2012, 17:03
Go to the top of the page
+Quote Post
Jackal29a
post May 18 2012, 18:39
Post #25





Group: Members
Posts: 36
Joined: 28-May 11
Member No.: 91053



QUOTE (Case @ May 18 2012, 17:26) *
It looks like J River does some signal processing (resampling) in its outputs. Your Xonar does not support the sample rates you mentioned (specs). And your Musiland does not support 32-bit output, 24-bits is max (specs).


Forget the specs of both cards Case, they were written according to the original drivers and have not been updated to show current capabilities. The Xonar ST has been accepting those sampling rates for over 2 years, same for my other D2X Xonar. The same happens with the Musiland specs, the USB receiver chip will accept 32bit from driver V. 2.2.xxxx onwards though the DAC IC is a 24bit TI PCM1793 so the last 8 bits will be truncated at some point.
Go to the top of the page
+Quote Post

8 Pages V   1 2 3 > » 
Closed TopicStart new topic
2 User(s) are reading this topic (2 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 19th April 2014 - 18:25