• AnyStream is having some DRM issues currently, Netflix is not available in HD for the time being.
    Situations like this will always happen with AnyStream: streaming providers are continuously improving their countermeasures while we try to catch up, it's an ongoing cat-and-mouse game. Please be patient and don't flood our support or forum with requests, we are working on it 24/7 to get it resolved. Thank you.

WASAPI Support

James said:
Hmm... maybe I'm doing something wrong with 24bit?
OTOH... there isn't much I can do wrong when calling IAudioClient::Initialize

http://msdn.microsoft.com/en-us/library/dd370875(VS.85).aspx
Click to expand...

Your implementation is fine. Foobar's output plugin "cheats".

I'm using Reclock in WASAPI mode exclusively now (no pun intended) and it is working flawlessly for everything. I had to set up a couple of rules+presets in ffdshow to handle some corner cases (mono audio plays back in Left channel only and <32k sample rate audio isn't supported by my audio device), but other than that it's handled everything I've throw at it.
 
The last renethx`s Update on WASAPI excluded mode (ATI and Nvidia HDMI audio)

http://www.avsforum.com/avs-vb/showpost.php?p=16032183&postcount=1258

192 kHz PCM is supported :agree:


mrcorbo said:
Your implementation is fine. Foobar's output plugin "cheats".

I'm using Reclock in WASAPI mode exclusively now (no pun intended) and it is working flawlessly for everything. I had to set up a couple of rules+presets in ffdshow to handle some corner cases (mono audio plays back in Left channel only and <32k sample rate audio isn't supported by my audio device), but other than that it's handled everything I've throw at it.
Click to expand...

Foobar's output plugin "cheats" means 24-bit padded to 32-bit (the eight extra bits utilized in 32-bit are padded as zeros)?
So internaly Foobar outputs 32-bit stream?

JAMES
And why Reclock+WASAPI (Nvidia HDMI audio) does not support 32-bit stream and Foobar does (internally 24 padded to 32bit)?

GeForce 9400 HDMI/v1.00.0.41

- ReClock+WASAPI exclusive mode: Up to 7.1 channel, 16 bit, 48/96/192 kHz PCM (24/32 bit are not supported; 44.1 kHz is not supported [mute sound].)
- foobar2000+WASAPI exclusive mode: Up to 7.1 channel, 16/24 bit, 48/96 kHz PCM (24 bit is supported only with Buffer Length < 900 ms; 44.1/192 kHz is not supported.)
 
Last edited:
mrcorbo said:
Your implementation is fine. Foobar's output plugin "cheats".

I'm using Reclock in WASAPI mode exclusively now (no pun intended) and it is working flawlessly for everything. I had to set up a couple of rules+presets in ffdshow to handle some corner cases (mono audio plays back in Left channel only and <32k sample rate audio isn't supported by my audio device), but other than that it's handled everything I've throw at it.
Click to expand...


Yep, I've done similar in ffdshow audio.


And here's a fun question...

If foobar pads 24bit to 32bit for WASAPI....how come selecting 32 bit directly in foobar no workee? Eh? Eh?
 
Just wondering, with WASAPI mode, when you first start playing a mkv w/ flac in TMT, the Clocks correction numbers in Reclock properties sometimes go waay out and the audio pitch goes off (usually down, sounds funny) a few seconds in, then it stabilises a few seconds later.

Is this normal?
 
Mark_A_W said:
Yep, I've done similar in ffdshow audio.


And here's a fun question...

If foobar pads 24bit to 32bit for WASAPI....how come selecting 32 bit directly in foobar no workee? Eh? Eh?
Click to expand...

Padding 24bit int to 32bit int for the former and using 32bit float for the latter? Since foobar doesn't specify there's no way to know for sure. I know, though, that on my setup 32bit int works and 32 bit float doesn't so it's a plausible explanation.

Also note that according to the fb2k developer 24-bit is padded to 32bit "when possible". Obviously, when your soundcard doesn't support 32bit it won't be used.
 
Yes, it must be using 32 bit integer when you pick 24 bit, and 32 bit float when you pick 32 bit.

If this was the case then the results match Reclock.
 
Has anyone tested HDMI on non ATI/NVidia chipsets namely Intel G45?

If I leave bit depth at 16bit then I have no problems and the sample rate and number of speakers changes as it should. If I try 24 bit, 32bit or 32 bit float I get a hardware not supported.

I could accept that maybe the Intel hardware or drivers doesn't support it but I have tried foobar2000 with its WASAPI plugin and it plays back 24 bit depth but not 32 bit.
 
briandarroch said:
Has anyone tested HDMI on non ATI/NVidia chipsets namely Intel G45?

If I leave bit depth at 16bit then I have no problems and the sample rate and number of speakers changes as it should. If I try 24 bit, 32bit or 32 bit float I get a hardware not supported.

I could accept that maybe the Intel hardware or drivers doesn't support it but I have tried foobar2000 with its WASAPI plugin and it plays back 24 bit depth but not 32 bit.
Click to expand...
Question is - does it really? Can you verify 24 bit output with your receiver/amp?
 
James said:
Question is - does it really? Can you verify 24 bit output with your receiver/amp?
Click to expand...

I'm not sure if it really does. I know foobar works on 16 and 24 but not 32bit, although working on a selection and actually using it are two different things. My Onkyo receiver (TX-SR875) can tell me the sample rate but it doesn't tell me the bitdepth, so it could be that foobar is at fault. I do know that the receiver supports it. Any tricks trying to figure out if it really is working?
 
briandarroch said:
Has anyone tested HDMI on non ATI/NVidia chipsets namely Intel G45?

If I leave bit depth at 16bit then I have no problems and the sample rate and number of speakers changes as it should. If I try 24 bit, 32bit or 32 bit float I get a hardware not supported.

I could accept that maybe the Intel hardware or drivers doesn't support it but I have tried foobar2000 with its WASAPI plugin and it plays back 24 bit depth but not 32 bit.
Click to expand...

i have also tried 24bit, 32bit with the intel g35/45chipset with no luck.
So im stuck with my ati card for now... i think its a intel driver limitation, not hardware. So i guess we should go to the guys at intel with this problem, I dont think James can help us here... ( even if he seems to be able to solve anything you throw at him :D)
 
Hello everybody... just signed in to report a minor issue with wasapi excl. mode

I have problems playing blu-ray movies from universal pictures (examples being casino, american gangster or the bourne trilogy) which have a particular type of menus that play a catchy metal chime when mouse or keyboard are browsing them. This chime seems to be incompatible with reclock under wasapi mode, as a matter of fact it is mute, which is no big deal. Unfortunately, failing to play the sound also results in player (pdvd or tmt) to freeze and crash whenever I select a menu button, and this is of course a big deal. I tried to run it without reclock or setting it to dsound or wave and this solves the issue, I get to play menu sounds and movie, but I still would like to have my cake and eat it too (playback AND wasapi).

Here is my configuration: Vista premium 32 bit (no service pack) pdvd 9/tmt 3 (no anydvd hd), nvidia 9600gt hooked to pioneer kuro via hdmi latest drivers, realtek 883 integrated sound latest drivers, reclock latest version

As a matter of fact it is very frustrating to think that if only I could get the movie to play without pressing a button on the menu this would solve the problem. Also disabling the menu exploration sounds is not an option as this requires menu buttons to work and before i get there, the player has frozen. :(
 
On your audio device properties, do you have checked "allow applications to take exclusive control of this device" and "give exclusive mode applications priority? Right click on the windows volume icon in the taskbar, "playback devices", double-click on your audio device, Advanced.

The menu buttons don't work because exclusive mode can only play one track, so no mixing the button sounds with the movie/menu audio can happen.
 
I have them both checked. Thanks for help, I now understand why it's not playing sound :clap:, but I don't know why it's freezing the player. TMT is actually less affected but I prefer pdvd because it has quadro speaker configuration which I need :bang:
 
Hmm I can't think of anything other than bugs though. I returned PowerDVD 9 and am stuck in PowerDVD 8.0.2217 because later versions had bugs and some were unstable and would crash, but it's weird that it only happens when using WASAPI exclusive for you. Does it happen with ALL the titles that have menu sounds, or just Universal titles like the ones you mentioned?
 
I can also confirm the problem that GrandeBoma is reporting. With Reclock set to wasapi excl mode, blu-ray movies from Universal Studios (and only from Universal Studios) cause the player to freeze. In my case, I use pdvd 8 build 3017. I do not have access to tmt but with GrandeBoma reporting the same problem on tmt, it seems the issue is generic across different players.


My general configuration is as follows:

OS - Vista Ultimate 32 bit (no service pack)
Player - pdvd 8 build 3017
Graphics Chip - NVidia GeForce 9400 (integrated Gigabyte GA-E7AUM-DS2H motherboard chipset)
Hooked to Onkyo receiver via hdmi
HDMI Audio Driver - 1.00.0.42
Reclock version - 1.8.4.8

I have a second box that is hooked up via SPDIF but otherwise using the same configuration that also exhibits exactly the same freeze behavior on pdvd. On both boxes I have tried multiple remove/re-install attempts of the reclock and pdvd and they always result in the same problem.

Any insight or suggestions would be great.
 
It turned out that freezing of tmt was due to another problem. hence the issue is confined to cyberlink
 
joenobody do you have AnyDVD HD? If so, you might wanna try an earlier build of PowerDVD 8. Build 2217 (not 2217a) is the ideal one, after that it went downhill fast. If you don't have AnyDVD HD, you probably have to keep using the latest builds, which suck.

GrandeBoma, since contemporaneous builds of PowerDVD 8 and 9 (and I think 7.3 too) have similar problems, you might be stuck, since there was no PDVD9 when 8.0.2217 came out. You might wanna figure out if others with PowerDVD 9 are having this trouble. I know PowerDVD 9 didn't allow ReClock to run at first, but James discovered a method to trick it.
 
I can just solve the problem by selecting direct3d as output... although I am not sure how that affects the audio quality
 
You must log in or register to reply here.
Back
Top