INTERACT FORUM
More => Old Versions => Media Center 13 (Development Ended) => Topic started by: KingDoughnut on December 07, 2008, 01:56:02 pm
-
My hardware can support 24/96 yet I can only get 16/48 out of wasapi with JRiver.....this should not be.
In exclusive mode I am able to get the full 24/96 out with other players using wasapi.
What gives???
-
I found out why...
Wasapi likes to be as real time as possible, where as any delay in the signal will create an error and it will not be able to lock on the signal. This is why the buffer in the control panel needs to be as low as possible....however this is still not low enough to get the full upsampled signal out for a lock with wasapi. The buffer in the registry entry needs to be adjusted slightly to lower from 6 seconds to about 4 seconds. Therefore if you change the number from 1770 to 1000 [6 sec to about 4 sec] you can get up to 16/96 out to your sound card. Note, if you lower this too much like to 1 sec there will be problems.
JRiver et.al might want to change this in the versions of 13 so that everyone can enjoy a greater benefit of upsampling without getting errors of "sample rate not supported by hardware"....or maybe not. There might be more to it than just a lower buffer because I still cant get a full 24bits out...16bit max....no matter how low I lower the buffer.
-
I wonder how feasible this would be.
If a user selects Wasapi output the reg key automatically changes to something less than 6 seconds to insure the ability to upsample without errors and the buffer slider becomes disabled and set to min. Once the user selects a different mode to output the reg key goes back to 6 and the buffer slider is adjustable. This might ad some robustness because it will reduce the probability of error messages and lock ups due to buffer issues.
-
I take it no one found this useful ??
Oh well, hope it helped someone....
-
Hi KD,
I found the thread of interest as I am am really pleased that MC13 has WASAPI support on my HTPC, which for me is working without any issues. For me it allows correct switching to 2ch PCM at 44.1kHz over my HDMI setup (instead of 5.1 with 3.1 blank channels) for 2CH "CD" Audio playback. My preference is for the output sample rate = source material. As I can only get WASAPI for 2ch PCM Audio with MC the 44.1kHz output is a good one for my CD's.
I'd still be interested in a WASAPI DirectShow filter for other media playback (video etc) if anyone has come across such a thing.
Thank and keep up the WASAPI work!
Nathan
-
Any idea why I can't get 24bit out while using WASAPI??
Is there anything that can be done on JRiver side that could make this happen?
Reducing the buffer has no affect...
-
Any resolution on this?
Can anyone confirm the inability to get a bit rate greater than 16bits out via WASAPI...
-
I can report mixed results with greater than 16 bits over WASAPI.
In my HTPC I have an Auzen Fusion sound card and an ATI 4550 graphics card with HDMI out. Both are connected to an Integra 9.8 preamp/processor.
With the Auzen Fusion connected over SPDIF, 2ch 16/44.1 and 2ch 24/96 works.
Over the HDMI connection 2ch 16/44.1 works but 2ch 4/96 only results in static.
I flac encoded dts trac (ripped from a dts CD) works over the fusion SPDIF but not over the HDMI. This is usually the ultimate test that a bit perfect connection is in place as any manipulation of the stream by the player or the OS will result in static. Thus, I can only conclude that the WASAPI connection over the HDMI is not quite bit prefect.
I also tried 2ch 24/192 and 5.1 24/96 over HDMI (pointless over SPDIF as it does not support those formats) and of course failed as well, although MC may have posted an error message saying the HW is not supported (which it is).
I'll try again and post back here.
I have to say I'm pleased MC has added support for WASAPI. I could never get ASIO to work with the Fusion, so have not been able to play back e.g. dts tracks through MC since I upgraded from XP and an m-audio 411 card a year or so ago.
So based on these findings, it seems MC's implementation may not have an issue, but rather our sound card drivers may be at fault? I'm using Realtek's ATI HDMI Device, V2.09 for the HDMI sound driver and it has passed bit perfect (i.e. dolby digital, dts) sound tracks from e.g. powerDVD and Vista Media Center.
-
Thank you for the reply, at least now I have some information to start trouble shooting.
I too have a Auzen sound card with a custom driver which allows me to get 24/96 but not with MC....with other media players it works.
I'm afraid at my level I can only play with buffer type settings and not get into the real code which may be needed to resolve this....
Thanks again for you support!
-
King D, you said you can get only 16/48. Do you mean that a track of a higher sample rate or bit depth does not play at all or do you mean it plays, but it is resampled to 48 Hz and/or the full bit depth is not delivered? If the latter is true how do you know what is the output format? The sound card's control panel or the receiver can indicate the sample rate, but I don't think there is a simple method for checking the outputted bit depth. 16-bit already provides a S/N ratio of 96 dB and it is not easy to hear differences when it is compared with higher bit depths.
... so have not been able to play back e.g. dts tracks through MC since I upgraded from XP and an m-audio 411 card a year or so ago.
... and you call that an upgrade. :) BTW, I am not aware of M-Audio 411. Do you mean M-Audio Delta 410?
In general, I don't understand why do you guys use Vista if it does not work. ASIO & XP works fine for me.
-
In general, I don't understand why do you guys use Vista if it does not work. ASIO & XP works fine for me.
For the record Vista works perfectly fine.
When playing a track that is sampled at 16/44.1 upsampled via MC to anything higher than 48 Hz I [was] not able to get playback without an hardware error. When I changed the reg key to about 4.5 seconds vs 6 seconds I was able to get 96Hz but nothing higher that 16bits.
After I changed the reg key to about 4.5 seconds I was able to get the full 96hz but not anything higher than 16 bits.
Other users have reported errors as well but just lowering the buffer via the gui is enough to attain normal playback of 16/44.1
-
For the record Vista works perfectly fine. ...
...not able to get playback without an hardware error.
Does it work or not? :)
For the record, I can play real 24-bit/96 Hz source files without setting anything on XP. My sound card changes the sample rate automatically and it plays up to 24-bit without problems (there is nothing to set for the bit depth). I'd say it's something that works. I don't really need to see the OS much on my dedicated player PC so anything that works is fine for me.
Upsampling 44.1 kHz source files is a waste of processor cycles if the sound device can play 44.1 kHz natively. Upsampling can only degrade audio quality (- in theory, practically the difference is not audible if a high quality resampler is used). Technically it is a lossy process that alters the signal. It makes sense only if the sound device doesn't support 44.1 kHz natively. In that case MC's sample rate converter may produce better results than upsampling that is done in the Windows kernel.
Just setting the bith depth setting to a higher value cannot increase the existing S/N ratio so it does not provide any benefit if the source material is 16-bit and an otherwise straight signal path is used (i.e. no DSP). The effect of the 24-bit output setting could be audible if the playback volume is set to a very low level using MC's 32-bit DSP and the amplifier is set to a very high volume level. Then MC would truncate the processed signal less and the resulting audible dynamic range could be higher.
I am sorry that I can't help with Wasapi. So far my only experienses of Vista have been when my friends have asked me to fix things like printer or network connections, but none of them have had a PC that is used as a serious media player.
-
... and you call that an upgrade. :) BTW, I am not aware of M-Audio 411. Do you mean M-Audio Delta 410?
In general, I don't understand why do you guys use Vista if it does not work. ASIO & XP works fine for me.
Yes, the Delta 410, sorry 'bout that.
You're right of course, it's pathetic. The Auzen Fusion in particular has been nothing but a great disappointment from the beginning. It was marketed with a promise of an HDMI add-on card to be released shortly after the main card was released. The add-on card would allow for bitstreaming of TrueHD/DTS HD Master and so forth BD/HD-DVD audio formats w/o downsampling using PAP. It was delayed and delayed and eventually canceled... In the mean time no working ASIO (at least for me) and quite lacking compared to the Delta 410 in other areas such as setting delays on the surround speakers. (M-audio on the other hand did not offer Vista drivers for the 410 at the time I was building this rig).
Vista was also marketed as finally solving all k-mixer and what not audio issues that had plagued XP/2k/98 and so forth for years, so at least on paper it looked good, plus Nvidia's Vista driver's supported video deinterlacing and hw acceleration whereas for XP they did not.
-
No upsampling used by me. My 24/96 tracks are either purchased from linn records, or ripped from DVD-A's.
I want the HDMI to work properly so I can send the 5.1 24/96 and 2.0 24/192 tracks to the preamp processor directly as the SPDIF is not an option for those.
-
After I changed the reg key to about 4.5 seconds I was able to get the full 96hz but not anything higher than 16 bits.
Where can I find this reg key?
-
I can't get 24 bit output either in MC. I either get an error that the format is unsupported, or if I lower the buffer, I just get noise. Using DSP studio to output everything as 16-bit and lowering the buffer (I have mine set to .50 sec) I can get 6 channel/96kHz to play (this is the highest fidelity file I have).
Foobar's WASAPI output plugin works fine for 24 bit output, though. I just needed to lower the buffer to the minimum (100ms) and I was able to playback my file at the full 6channels/24bit/96kHz resolution.
It would be nice if this functionality could eventually be matched in MC, but I can appreciate that this is probably a low priority. 16 bit is adequate for 99.9% of my music collection and exclusive mode at least fixes the fixed channel output problem I was having (PC sent stereo tracks to my receiver as 5.1 multichannel with 4 blank channels) so I can live with having to use Foobar for the few tracks that I have than are 24-bit.
-
I did some further testing.
The SPDIF below refer to the Auzentech Fusion card and HDMI refers to an ATI 4550 HDMI out with Realtek's 2.09 ATI HD sound driver. I used JRMC13 (build 82 I believe
I tested foobar with default buffer but with both 16 bit and 24 bit set in the config as the result was slightly different if I did.
Although foobar is able to play a few more formats over HDMI, it failed to play the dts5.1 track, thus I don't trust that the output from foobar over HDMI is at all bit perfect.
Also an issue with MC13 - if I got static out, it doesn't stop when I stop playing the file, or even after closing the app, i.e. I still hear static - pause - static - pause, where each static burst is perhaps a second and the pause about the same duration.
Hopefully this can be resolved, in the meantime I'm stuck with the Auzen card.
foobar2000 24bit output - HDMI
2.0/44.1 - yes
2.0/96 - yes
2.0/192k - no - "Unrecoverable playback error: Could not open device (8007000E)"
5.1dts - no
5.1/24 - no - "Unrecoverable playback error: Could not open device (8007001F)"
foobar2000 16bit output - HDMI
2.0/44.1 - yes
2.0/96 - yes
2.0/192k - yes
5.1dts - no
5.1/24 - no - "Unrecoverable playback error: Could not open device (8007001F)"
foobar2000 24bit output - SPDIF
2.0/44.1 - yes
2.0/96 - yes
2.0/192k - no (expected)- "Unrecoverable playback error: Could not open device:
unsupported data format: 192000 Hz / 24-bit / 2 channels"
5.1dts - yes
5.1/24 - no - (expected) "Unrecoverable playback error: Could not open device:
unsupported data format: 96000 Hz / 24-bit / 6 channels"
foobar2000 16bit output - SPDIF
2.0/44.1 - yes
2.0/96 - yes
2.0/192k - no - (expected) "Unrecoverable playback error: Could not open device:
unsupported data format: 192000 Hz / 16-bit / 2 channels"
5.1dts - yes
5.1/24 - no - (expected) "Unrecoverable playback error: Could not open device:
unsupported data format: 96000 Hz / 16-bit / 6 channels"
=============================================================================
MC13 - SPDIF
2.0/44.1 - yes
2.0/96 - yes
5.1/44.1 - yes, but only 2ch out
2.0/192k - no - "Yellow triangle w/ !-sign"
5.1dts - yes
5.1/24 - no - Yellow triangle w/ !-sign
MC13 - HDMI
2.0/44.1 - yes
2.0/96 - Yellow triangle w/ !-sign
5.1/44.1 - yes, but only 2ch out
2.0/192k - Yellow triangle w/ !-sign
5.1dts - no - static
5.1/24 - no - Yellow triangle w/ !-sign
-
@ suviking
Using a Radeon HD 4870 here myself and Foobar absolutely does playback DTS. In fact I am listening to my standard test disc as I type this. Receiver reports DTS Surround. You need to make sure that the volume control is set to max in Foobar to prevent any bit-fiddling, though. So maybe that's your problem?
...and a followup test confirms 6 channel/24bit/96kHz playback as well. In this case make sure under output you have the buffer length set to the minimum 100ms. The default setting causes the "Unrecoverable playback error: Could not open device XXXX" for me as well.
-
Thanks for the heads-up mrcorbo! Lowering the buffer to 100ms did the trick with foobar over the HDMI output. I also managed to get the dts wav to work by changing the speaker setup in Windows to stereo (I had it set to 5.1 before). Now 16 vs 24 bits in foobar makes no difference, i.e. both tracks play fine when foobar is configured to 24 bit output.
With MC I also had success in playing the dts wav files when I set the speaker config to stereo. No change in the behavior of the high bitrate files though, even with the buffer set to the lowest - 0.05s, the files won't play.
Anything the the MC team can do to improve the WASAPI implementation to work with high bitrate tracks? The issue with the static continuing to play after I stop - and exit JRMC13 continues to happen. I have to logoff/logon in order to get rid of it. Very annoying.
-
The issue with the static continuing to play after I stop - and exit JRMC13 continues to happen. I have to logoff/logon in order to get rid of it. Very annoying.
That may be a driver problem.
-
Could be. Through the Auzen it does not happen, but for foobar it does not happen with either device... It is intermittent as well, so probably a tough one to chase down.
/Anders
-
It looks like we need to convert 24-bit streams to 32-bit on some soundcards. We'll add this to a coming build.
We'll also automatically bump the buffer duration down so that a user-setting can't result in failure to get playback.
Thanks.
-
It looks like we need to convert 24-bit streams to 32-bit on some soundcards. We'll add this to a coming build.
We'll also automatically bump the buffer duration down so that a user-setting can't result in failure to get playback.
Thanks.
Sounds great! I'm looking forward to testing it.
-
In build 96 (and later), hopefully available next week:
Changed: WASAPI playback better handles 24-bit playback for cards that only support 24-bit playback padded to 32-bit.
Changed: WASAPI playback automatically reduces the user-set buffer size in hardware exclusive mode if the size is larger than the card supports.
-
Thanks for the heads-up mrcorbo! Lowering the buffer to 100ms did the trick with foobar over the HDMI output. I also managed to get the dts wav to work by changing the speaker setup in Windows to stereo (I had it set to 5.1 before). Now 16 vs 24 bits in foobar makes no difference, i.e. both tracks play fine when foobar is configured to 24 bit output.
With MC I also had success in playing the dts wav files when I set the speaker config to stereo. No change in the behavior of the high bitrate files though, even with the buffer set to the lowest - 0.05s, the files won't play.
Anything the the MC team can do to improve the WASAPI implementation to work with high bitrate tracks? The issue with the static continuing to play after I stop - and exit JRMC13 continues to happen. I have to logoff/logon in order to get rid of it. Very annoying.
Weird that you needed to change to stereo output to get that DTS wav to work as I don't have to do that. In fact, that was one of the reasons I wanted WASAPI+exclusive in the first place - so I wouldn't have to keep flipping between 5.1 and stereo every time I want to listen to music.
I get the looping audio sometimes also when stopping playback. I usually get rid of it by just playing-pausing until it doesn't loop anymore. The looping is also directly related to the size of the buffer. A longer buffer results in a longer snippet of looping audio.
@ Media Center Team - I'm looking forward to testing the fixes. Thanks for the attention.
-
Thanks for the attention.
Indeed!
When I bought this up I thought it was going to get logged under "Stupid User Problem" and ignored.
-
Build 100 (http://yabb.jriver.com/interact/index.php?topic=49871.msg341214#msg341214) has improved WASAPI support.
-
I've just done some testing of the new build and things are definitely on the right track.
I can now play 24/96 2.0, 24/96 5.1 and 24/192 2.0 over the HDMI. The bad news though is that there is loud static being played as well... The frequency of the static diminishes by upping the buffer time, i.e. at the lowest - 0.05 s the static is more or less constant, at higher buffer times the static is more bursty so to speak. Even at max though the static does not go away.
At buffer times greater than 0.44 s the 24/96 5.1 track stops playing.
The weird noise when hitting the stop or pause button is still there.
The dts wav plays over the HDMI when speaker config is set to stereo, but not when set to 5.1.
No changes with the Auzen SPDIF out, i.e. everything that should work over it still works.
-
Happy to also test on my system if you have some sample files you can post.
-
Hi jmone,
I found these samples googling: http://01688cb.netsolhost.com/samplerdownload/
They appear to be 2ch only, but have 96k sampling.
I played them on my desktop PC - it has the Asus P6T MB and I'm using the built in sound chip - Soundmax with a simple stereo analog out and got the same weird noise as with the HDMI out on my HTPC.
Please try one and see what result you get. What sound card/chipset do you use?
-
Hi - I played repighirossiana_01.flac and got a regular light dah dah dah dah noise over the top of the track. Pressing pause and all was quiet but when restarting I got a burst of static. Regular tracks play fine.
Thanks
Nathan
PS Audio Decoding on my system is via the Intel G33 HDMI Chipset.
-
It seems you hear the same noise I hear. So far we have ATI/Realtek HDMI, Intel G33 HDMI and SoundMax analog all have the noise issue. The Auzen Prelude SPDiF the odd man out w/o noise. Only the ATI HDMI has the stop stutter issue.
-
I'm experienceing the same issues as suviking minus the need to change to stereo to play back DTS wavs.
Also, here's a good place to get high res test samples in various formats:http://www.2l.no/hires/index.html
-
FYI - here are some results using the various B.Britten: Simple Symphony tracks at http://www.2l.no/hires/index.html - I've not played with any WASAPI settings at all.
Surround 5.1 DTS 24BIT/44.1kHz - outputs the bit steam to the AV Receiver and plays just fine
Surround 5.1 FLAC 24BIT/48kHz - plays but with the digital crackle (all quiet when paused)
Stereo FLAC 24BIT/48kHz - plays but with the digital crackle (all quiet when paused)
Surround 5.1 FLAC 24BIT/96kHz - would not play - MC13 error message "Playback could not be stated on the output "Windows Audio Session API (WASAPI) using the format 96000Hz, 24bits, 6ch"
Stereo FLAC 24BIT/96kHz - plays but with the digital crackle (all quiet when paused)
Stereo FLAC 24BIT/192kHz - plays but with the digital crackle (all quiet when paused)
Surround 5.1 WAV 24BIT/48kHz - will not play - messages in MC13 is "analyse files --> there is nothing to play"
Stereo WAV 24BIT/96kHz - will not play - messages in MC13 is "analyse files --> there is nothing to play"
-
@ Jmone
Lowering the buffer may allow you to play that Surround 5.1 FLAC 24BIT/96kHz file. I have to use a setting of .50s or lower to get all the formats to play.
-
Those 2L tracks sure are great sounding. I'll buy a couple of their albums as soon as we can get MC13 to stop playing "morse code" on top of track.
I managed to play them (with noise) when the buffer is 0.44s or less.
-
Build 101 and newer should automatically reduce the buffer size as necessary. If you still can cause playback errors by increasing the buffering, but see them go away when reducing the buffering, please post with more information about your soundcard and the version of Media Center you're using.
Thanks.
-
My desktop system playing the Britten flac 5.1ch 24/96 file:
With the buffer set to or greater than 0.47s, MC13 reports "Playback could not be started on the output 'Windows Audio Session API (WASAPI) using the format '96000 Hz, 24 Bits Per Sample, 6 Channels'. Lowering the buffer to 0.44s, the file plays.
Sysinfo:
Media Center 13.0.101 Registered -- C:\Program Files (x86)\J River\Media Center 13\
Microsoft Windows Vista 6.0 Service Pack 2, v.113 (Build 6002)
Intel Pentium III 2672 MHz MMX / Memory: Total - 3135 MB, Free - 1881 MB
Sound device:
On-board audio on Asus P6T deluxe motherboard - ADI AD2000B (SoundMax Integrated HD Audio).
-
Matt,
I upraded my HTPC from buildd 100 to 101 as well and got the same result, buffer greater than 0.44 s results in no playback. Here I have an ATI 4550 video card with HDMI out and the Realtek ATI HDMI Driver V2.09.
-
Sound device:
On-board audio on Asus P6T deluxe motherboard - ADI AD2000B (SoundMax Integrated HD Audio).
Please send your i7 to JRiver, Inc. c/o Matt. I'll get it back to you as soon as the i8's are available ;)
-
he he, it's a nice CPU for sure ;D
-
In build 102 and later (should be coming by next week):
Fixed: WASAPI playback could (still) fail on certain devices if the user-specified buffer size was too large.
Fixed: WASAPI playback of 24-bit material could produce static / ticking with certain hardware.
-
Excellent! I'm looking forward to test the new build.
-
I can confirm that V102 fixes the static ;D on my rig, however I still can not playback the following three files:
Surround 5.1 FLAC 24BIT/96kHz - would not play - MC13 error message "Playback could not be stated on the output "Windows Audio Session API (WASAPI) using the format 96000Hz, Surround 5.1 WAV 24BIT/48kHz - will not play - messages in MC13 is "analyse files --> there is nothing to play"
Stereo WAV 24BIT/96kHz - will not play - messages in MC13 is "analyse files --> there is nothing to play"
-
I have upgraded my Vid Card to an HD4550 and can also confirm the "Stop Stutter" issue has now appeared, as follows:
On the Intel G33: I'd see the receiver switch between 5.1CH MPCM (std output) to 2ch PCM when playing a CD Audio track using WASAPI and back again just fine.
On the HD4550: I'd see the receiver switch between 5.1CH MPCM (std output) to 2ch PCM when playing a CD Audio track using WASAPI but when the "stop stutter issue" happens it does not seem to switch back to 5.1CH MPCM or I see "Analogue" flash up first.
Anyway it seems that around 1/2 the time the issue occurs when stopping a CD Audio track which is not so good & I really liked WASAPI!
Let me know if you need any more info.
Thanks
Nathan
-
Nathan,
were you able to play the 3 files you had trouble with on the G33 through the 4550 using build 102?
/Anders
-
No - the files all played (or did not play) identically, but the good Folk at JR continue to make tweaks to the WASAPI code so you never know what will change over the next few builds.
-
For the ATI users, the "Stop Stutter" issue is also being addressed in upcoming builds!
-
Sweet!
-
For the ATI users, the "Stop Stutter" issue is also being addressed in upcoming builds!
All good stuff. Thanks for the heads-up!
-
Quick testing done on new build v104
Sound seems perfect during 24 bit playback.
Playing back 6 channel/24bit/96kHz track requires buffer setting of .40 or below or playback fails.
Occasional single burst of noise when stopping playback.
Consistent single burst of noise when starting playback from stopped state, behavior even persists after closing and re-opening application.
Noise on starting playback can be prevented by changing the buffer value in between stopping and re-starting playback. I noticed this while trying to determine the highest buffer value that would allow 6ch/24bit/96kHz playback.
Getting closer....
-
What sound card are you using?
I've been a little surprised that different cards seem to behave quite differently, return different errors when out of memory, etc.
-
On my HD4550
Occasional single burst of noise when stopping playback.
Yes - I hear that one.
Consistent single burst of noise when starting playback from stopped state, behavior even persists after closing and re-opening application.
I don't have this problem eg I can start stop Audio tracks just fine, can you explain more how this occurs & I can double check.
Thanks
Nathan
-
What sound card are you using?
I've been a little surprised that different cards seem to behave quite differently, return different errors when out of memory, etc.
Radeon HD 4870 using Realtek drivers. I just looked and there's a new 2.14 driver set and a 2.13 version of the ATI HDMI Audio Device. I'm going to try the 2.14 driver package and see if it changes anything.
For now, though, more results with current drivers -
These bursts of noise only seem to happen during 24bit playback.
Pausing a track frequently leads to looping audio, still. In both 16 bit and 24 bit. Resuming play usually stops the looping, but I once had playback hang up. Pressing stop after the hang and then pressing play worked.
Skipping between tracks seems to work fine.
@jmone
It happens every time I press play after pressing stop. Going into output settings and changing the buffer size (even by just .01) in any direction in between pressing stop and pressing play prevents it.
-
Build 104 certainly took care of the static and the high bit tracks now play beautifully. Sure, there’s a bit of a pop when stopping/playing and the noise when pausing is still there on some tracks, but I also have tracks where I could not reproduce that behavior.
I upgraded to V2.13 of the realtek driver (2.14 is not for the ATI card) and did not notice any difference.
The quality of those 2L recordings in 5.1/24/96 is amazing.
Thanks Matt for straightening out the WASAPI interface!
I’m off to download and listen to some more HD music!
/Anders
-
With ATI HDMI Driver 2.13 installed I don't get the noise on hitting the stop button any more. All other issues still present.
As suviking said, though, what works works great!
-
Radeon HD 4870 using Realtek drivers. I just looked and there's a new 2.14 driver set and a 2.13 version of the ATI HDMI Audio Device. I'm going to try the 2.14 driver package and see if it changes anything.
FYI - with my HD4550 I was told to first intall the Realtek Vista Drivers (V2.14) then the ATI HDMI Drivers (V2.13) which has been working well most things. I've not had the chance to play anymore however as the familly want to watch content!
-
Could someone please enlighten me about benefits of using WASAPI over ASIO or DirectSound? Is it of relevance only to those who use audio over HDMI? Or, it would also benefit who use high-end sound cards supporting 24-bit/96kHz?
Thanks,
Osho
-
Could someone please enlighten me about benefits of using WASAPI over ASIO or DirectSound? Is it of relevance only to those who use audio over HDMI? Or, it would also benefit who use high-end sound cards supporting 24-bit/96kHz?
Thanks,
Osho
This is my first experience with using a high quality Audio Renderer so while I can't enlighten you on the differences (if any) with ASIO, I do get two big benefits from using WASAPI over DirectSound:
1) Quality - to my (untrained) ears the quality output is far better using WASAPI than DirectSound. I've got all my music ripped in WMA Lossless and have it reproduced by a Yami V2700 with Axiom Epic60/500 5.1 speaker setup.
2) Empty Ch Problems - WASAPI (exclusive mode) will change the output from my HTPC to 2CH to match the playback of my CD Audio tracks from the Default 5.1 setting in the control panel which DirectShound will not do. This solves the problem where my Receiver was getting 5.1 CH from the HTPC but only 2 CH had any information in it (the other 3.1 were present but blank). This causes problems with Base Mgt, and (if you are into it) all the sound field mgt the Receiver can do as it thinks it is getting 5.1 not 2.0.
Thanks
Nathan
-
Could someone please enlighten me about benefits of using WASAPI over ASIO or DirectSound? Is it of relevance only to those who use audio over HDMI? Or, it would also benefit who use high-end sound cards supporting 24-bit/96kHz?
Thanks,
Osho
Versus ASIO, it's a little more supported. Being an integrated feature of Vista it should work on a wider variety of hardware than ASIO (though with ASIO4All, I was always able to get ASIO output with even the onboard audio codecs I have used). If you already have a working ASIO-capable setup, though, you may not gain any functionality.
Versus DirectSound, WASAPI in exclusive mode offers bit-perfect audio output. No mixing, no resampling. In my particular setup the audio data goes untouched from the point of decoding the audio file to when it gets to my receiver for playback which is exactly how I want it.
-
If you are intested in the possibility of including WASAPI support in the free ReClock Direct Show filter you may like to contribute to this thread at the Dev's Site http://forum.slysoft.com/showthread.php?t=24998
Thanks
Nathan
-
For my configuration (Windows XP Service Pack 3 with Lynx L22 sound card), ASIO works but WASAPI does not. What can I do to get WASAPI work for audio ? Would I see any benefit over ASIO?
Thanks,
Osho
-
For my configuration (Windows XP Service Pack 3 with Lynx L22 sound card), ASIO works but WASAPI does not. What can I do to get WASAPI work for audio ? Would I see any benefit over ASIO?
WASAPI is a Vista feature.
Generally speaking, you can use WASAPI instead of ASIO on Vista. Both output modes are capable of bit perfect playback.
I don't know if a device driver must specifically support WASAPI before it can work and I don't know how the Lynx driver works on Vista.
EDIT
I'd be happy to assist. Just send me one Lynx L22 (http://www.lynxstudio.com/product_detail.asp?i=11) card for testing. I'll post a report ASAP. :)
-
WASAPI is a Vista feature.
Generally speaking, you can use WASAPI instead of ASIO on Vista. Both output modes are capable of bit perfect playback.
I don't know if a device driver must specifically support WASAPI before it can work and I don't know how the Lynx driver works on Vista.
Thanks Alex. If I have ASIO on Windows XP SP3, should I bother moving to Vista for WASAPI? As I see it, both should send the same bit perfect audio to the sound card.
EDIT
I'd be happy to assist. Just send me one Lynx L22 (http://www.lynxstudio.com/product_detail.asp?i=11) card for testing. I'll post a report ASAP. :)
I wish I had an extra one lying around - if only the economy was better... :)
Osho
-
WASAPI on Vista cannot provide better audio quality than ASIO on XP. Bit perfect is bit perfect.
MS has claimed that Vista provides better audio quality than XP when the OS level, built-in audio engine is allowed to process the signal. Some of the usability related audio features have changed in Vista -- to better or worse depending on personal preferences.
I have used Vista only occasionally and briefly. I still prefer to install XP on my PCs.
P.S.
I have wanted to buy a LynxTWO-B card (with 6 output channels), but I always seem to be short of cash when I am purchasing new hardware and I end up buying other things that I need more urgently... :P
-
Since when did the Radeon become a soundcard?
-
Since when did the Radeon become a soundcard?
Since it started supporting HDMI output I think. HDMI sends both audio and video on the same cable so the graphics card has to become aware of sound. The same is true about the recent Nvidia cards.
Osho
-
Since it started supporting HDMI output I think. HDMI sends both audio and video on the same cable so the graphics card has to become aware of sound. The same is true about the recent Nvidia cards.
Osho
Slight clarification:
Nvidia video cards of recent vintage can passthrough audio received via S/PDIF from an external source. ATI Radeon HD cards (3xxx and 4xxx series) have an onboard Realtek codec to generate their own sound. The 3xxx series supports stereo PCM (up to 24 bit/192kHz IIRC) as well as Dolby Digital and DTS compressed audio. The 4xxx series adds multichannel PCM support of up to 7.1 channels @ 24 bit/192 kHz.
OTOH there are Nvidia motherboards with integrated video and audio (8xxx and 9xxx series) that have the same support for mutlichannel LPCM as the 4xxxx series Radeons.
-
WASAPI on Vista cannot provide better audio quality than ASIO on XP. Bit perfect is bit perfect.
Hmmmm, I beg to differ...."audio quality" is highly subjective and has to do with a huge amount of variables, only one of which is the bit perfect method of transmission. To my ears, with my computers, in my listening room, with my audio gear bit-perfect ASIO sounds different that bit-perfect WASAPI. I would venture to say that I am not the only person who hears or 'think they hear' a difference between bit-perfect ASIO and bit-perfect WASAPI. If their is a 'difference' then one can and always will be perceived as being of higher quality than the other. ;D
-
I am not sure if you are just joking (I guess ;D means that) , but...
The bit perfect ASIO and bit perfect WASAPI outputs are bit to bit identical. If other factors are causing measurable, audible or imagined differences then they are, but those differences are not caused by the ASIO or WASAPI stages in the signal chain if all related settings are correctly set to transmit unaltered signal. In theory you could redirect the output from ASIO and the output from WASAPI (before they reach any hardware component) to a SW comparator and it would verify that the outputs are identical. Naturally someone would first need to create the needed test software.
-
I am not sure if you are just joking (I guess ;D means that) , but...
The bit perfect ASIO and bit perfect WASAPI outputs are bit to bit identical. If other factors are causing measurable, audible or imagined differences then they are, but those differences are not caused by the ASIO or WASAPI stages in the signal chain if all related settings are correctly set to transmit unaltered signal. In theory you could redirect the output from ASIO and the output from WASAPI (before they reach any hardware component) to a SW comparator and it would verify that the outputs are identical. Naturally someone would first need to create the needed test software.
Nah, not joking....just implying that I am making a friendly exchange of dialog.
I am sure you know this type of discussion has gone on for ages...similar discussions used to go on about powercords, IC's, speaker cable and the like. Do we really want to dig up this old horse and beat it some more??
Let's just suffice to say there is such a thing as the Placebo affect, and there are people who claim to hear things that are not able to be measured. I guess I am one of them... ;D
-
Hi all,
I've got some ripped DVD-As at 88.2kHz, and they won't play with WASAPI exclusive mode. Same error that comes up when you play 96/24's with incorrect buffer size settings, except I can't get this to go away. Is this a limit of WASAPI, or the JRiver implementation? I've got everything else to work.
Cheers,
-Doug
-
Hi all,
I've got some ripped DVD-As at 88.2kHz, and they won't play with WASAPI exclusive mode. Same error that comes up when you play 96/24's with incorrect buffer size settings, except I can't get this to go away. Is this a limit of WASAPI, or the JRiver implementation? I've got everything else to work.
Cheers,
-Doug
It's possible your soundcard can't run its clock at 88.2. You could use DSP Studio to resample -- it's extremely high quality.
-
It's possible your soundcard can't run its clock at 88.2. You could use DSP Studio to resample -- it's extremely high quality.
Thanks Matt - will try!
-
FYI James at Slysoft has confired a couple of times now that they will be adding WASAPI Support to their DirectShow Reclock Audio Renderer!
http://forum.slysoft.com/showpost.php?p=177063&postcount=34
How good is that!
EDIT - CH Mapping is now supported in Reclock --> http://yabb.jriver.com/interact/index.php?topic=50688.0
-
Pausing a track frequently leads to looping audio
Mmm it is back for me....anyone else?
Thanks
Nathan
-
Did you try changing MC settings for WASAPI?
-
Nope - I've never changed a single WASAPI setting!
-
Mmm it is back for me....anyone else?
Thanks
Nathan
It never left for me. Still have all the issues outlined here (http://yabb.jriver.com/interact/index.php?topic=49536.msg342109#msg342109) and here (http://yabb.jriver.com/interact/index.php?topic=49536.msg342145#msg342145).
-
Did you try changing the settings for WASAPI in MC? You may need to update to find them.
-
For those interested, the latest version of Reclock as intoduced WASAPI support http://forum.slysoft.com/showthread.php?t=19931
-
Did you try changing the settings for WASAPI in MC? You may need to update to find them.
My last post was based on a re-test using the .126 build. The only settings I'm aware of are buffer size and the exclusive mode checkbox. Was there anything else added that I'm not aware of?
-
Please check the history for the recent builds. It's in each release thread on this board.
-
Please check the history for the recent builds. It's in each release thread on this board.
No WASAPI-related changes in the release notes that I can see since build .104.
-
Anyone having any stability issues with MC13 at present. I've had MC hang a few times leaving the WASAPI rap dance audio loop and an unresponse MC13 (needs to be killed). This seems to happen after a half hour or so of playing Audio (using Radio) - I'm now trying with Direct Show to see if it is WASAPI related.
I've attached the crash log (it is big however) if it is any help...
Thanks
nathan
-
Anyone having any stability issues with MC13 at present. I've had MC hang a few times leaving the WASAPI rap dance audio loop and an unresponse MC13 (needs to be killed). This seems to happen after a half hour or so of playing Audio (using Radio) - I'm now trying with Direct Show to see if it is WASAPI related.
I've attached the crash log (it is big however) if it is any help...
Thanks
nathan
Mmmm - I wonder.... http://support.microsoft.com/kb/957569 will give it a go...
Given the last three lines of my log file is:
2521226: 2160: Playback: CMJWaveFeeder::Thread: Finished feeder loop (bCancel: 0)
2521226: 2160: Playback: CPlayerZone::PlayNextFile: bContinue=1, bCanPlayNext=1, m_bPlaybackError=0
2521226: 2160: Playback: CMJWaveFeeder::Thread: Finish (261707 ms)
-
Mmmm - I wonder.... http://support.microsoft.com/kb/957569 will give it a go...
This fix works - no more hangs/stalls etc
-
Thanks for letting us know.
-
New version of reclock is out with much improved WASAPI support (http://forum.slysoft.com/showthread.php?t=19931) ;D including:
* New: Added option to select the desired output format for PCM audio (same as input, 16/24/32 bit PCM or 32 bit IEEE float)
-
Anyone still getting stutter when pressing pause?
-
Anyone still getting stutter when pressing pause?
Yes. All the issues I had as of .104 are still present in the current version.
-
Testing .140
Looping audio on pause, burst of noise on pressing stop and burst of noise on restarting playback after pressing stop (this last will happen even if you shut the application down and restart in between) are all still present.
Changing the buffer value in between pressing stop and restarting playback still prevents the burst of noise on restarting playback.
-
This appears to be a MC WASAPI implementation issue as while reclock had similar issues they have now been resolved.
-
Here are some updated notes on what plays / does not for me using MC V141 / Vista 32-Bit SP1 / Gigabyte HD4550 / Cat 9.2 / Realtek R218 Drivers / 5.1 Ch set in Audio Cntl Pnl --> using the various B.Britten: Simple Symphony tracks at http://www.2l.no/hires/index.html - I've not played with any WASAPI settings at all.
Surround 5.1 DTS 24BIT/44.1kHz
- Output = Fine, 5.1DTS Bitstream is sent to the receiver
- Pausing = Issues
a) Pressing "Play" causes the Receiver to flash on/off that it is getting a DTS Stream (eg the Stutter) but it is paused. Press "Play" again and it starts playing fine.
b) Pressing "Pause" seems to force the Audio out stream to 2CH PCM & from then on you don't hear anyting and can not resume playback. You have to press "Stop" and start again.
Surround 5.1 FLAC 24BIT/48kHz
- Output = Fine, 5.1 PCM is sent to the receiver
- Pausing = Issues, I'm getting the usual stutter, however as reported above it will also occasionally also freese when presssing "pause" (you hear nothing, the song does not advance) but you can stop and restart the track
Stereo FLAC 24BIT/48kHz & Stereo FLAC 24BIT/96kHz & Stereo WAV 24BIT/96kHz
- Output = Fine, 2.0 PCM is sent to the receiver
- Pausing = Issues, same probs as above.
Surround 5.1 FLAC 24BIT/96kHz - would not play - MC13 error message "Playback could not be stated on the output "Windows Audio Session API (WASAPI) using the format 96000Hz, 24bits, 6ch" - Note: I've not played with any buffer settings and others have reported this one plays.
Stereo FLAC 24BIT/192kHz
- Output = Wrong CH Configuration as 5.1 PCM is sent to the receiver
- Pausing = Issues, same probs as above.
Surround 5.1 WAV 24BIT/48kHz - will not play - messages in MC13 is "analyse files --> there is nothing to play"
MP3 / WA Lossless- Output = Fine, 2.0 PCM is sent to the receiver
- Pausing = Issues, same probs as above.
Summary: There is still the issue with "Pause" that causes the stutter or even stalls the playback of the track with all audio media types. The dynamic allocation of Channel Mapping is correct for all but one file type. MC's WASAPI Implemenation does not reset the Audio output to the default set in the control panel (eg mine is 5.1) but sets it at 2.0 CH.
Thanks
Nathan
-
Just tried the HDMI Drivers part of Cat9.3 and
1) there is no stutter problem,
2) auto channel config works
3) DTS in WAV file played fine
There is a problem with 32-Bit support in reclock (I'll post in their forum) but for now I've just turned off 32-Bit output in FFDSHOW and config reclock to set the output as the same as the input.
-
JRiver, do you plan to improve the WASAPI support in MC13 or is this the best we can hope for?
With latest 13.0.151 I still get stutter loop when paused (no matter if I check / uncheck "Flush device buffers") and also fading seems to be not working properly (on Stop or Next).
Vista Enterprise 64-bit SP1 (with latest updates)
ATI HD 4850 (Catalyst 9.4) connected via HDMI to receiver Denon AVR-2808
ATI HDMI Audio Device 2.18 (Realtek driver)
Thank you
-
JRiver, do you plan to improve the WASAPI support in MC13 or is this the best we can hope for?
With latest 13.0.151 I still get stutter loop when paused (no matter if I check / uncheck "Flush device buffers") and also fading seems to be not working properly (on Stop or Next).
Vista Enterprise 64-bit SP1 (with latest updates)
ATI HD 4850 (Catalyst 9.4) connected via HDMI to receiver Denon AVR-2808
ATI HDMI Audio Device 2.18 (Realtek driver)
That may be a driver problem.
-
What driver do you mean - Catalyst or Realtek?
Before I updated to latest I had been using Catalyst 9.2 and Realtek ATI HDMI Audio Device 2.13 and my HTPC behaved the same way (that's why I tried to update both to the latest).
-
I don't know which driver. Even the latest may not work correctly. Did you try a google search?
-
Johnny,
Try the HDMI Audio drivers that come as a part of the the ATI Catalyst pack. You will first need to uninstall the Reltek ATI Audio Driver (which still stutter with MC) then reinstall Catalyst. Your stuttering will be gone but you have other issues that you may or may not care about including:
1) Silent Stream: When sound is not being sent the Audio is acutally turned off (good way of removing stuttering) but you will not hear any "quick" sounds such as Windows Notification as by the time it has started the sound has finished. I don't mind this behaviour but others do....
2) No 32-Bit Debth Support (see my post above). It does not cause me any probs
Overall I'm happy(ier) with the HDMI Drivers in the ATI Catalyst install pack.
Thanks
Nathan
-
I tried Google pretty thoroughly however I did not manage to find anything relevant.
I tried official "Gigabyte HDMI AudioDriver" downloaded from Gigabyte website which is in-fact Realtek driver 1.97.
I also tried "ATI HDMI Audio Device" version 2.13 and 2.18 (downloaded from Realtek website).
In all 3 cases MC13 behaves the same way:
- Crossfade (on Next) works fine
- Fade out (on Stop) does not work = once I hit Stop button playback still goes on for a while (this "while" is determined by Fadeout settings Fast / Normal / Slow) and then playback stops instantly
- On Pause I get cca 1 second stuttering loop no matter if I check / uncheck the "Flush device buffers" checkbox
I also did want to try the integrated Catalyst HDMI audio drivers (9.4) however I am simply unable to try them at all. Once I uninstall Realtek drivers Vista automatically installs those crappy Microsoft drivers. I managed to prevent Vista from doing this by moving hdaudio INF files from Windows\Inf folder -> then I had "Unknown devices" in Device Manager. I reinstalled Catalyst 9.4 = still "unknown devices". I even uninstalled / install Catalyst = still the same. This is weird because I am unable to find any relevant ATI *.INF files anywhere in my system (I tried to update drivers manually by pointing Vista to specific location however there is no place to go). Nevertheless even if I would be able to make it work (Catalyst) at least that "Silent stream" bug is something that DOES bother me (I did "enjoy" it a lot with NVIDIA). I also read lots of comments on Internet that these Catalyst HDMI audio drivers suck and that the Realtek is much better...
-
No idea why the CAT HDMI Drivers will not install. All I did was uninstall the Realtek ones and upgraded to Cat 9.4 and they were installed correctly. The CAT HDMI Drivers IMHO don't suck "more", they just suck "differently" to the Realtek ones. I'd rather have the silent stream than the stutter....
-
I will try to contact AMD support - maybe they will have some explanation / hint.
Have you contacted them regarding the "silent stream" bug?
JRiver, is there anything I can do for you in order to solve this? Like sending some logs, doing some tests - whatever?
-
So I've been in contact with AMD for several days already. After some misunderstandings from their side we finally got to the core of the problem (=ATI HDMI audio driver in Catalyst) and it seems that the driver is included in their "Option 1" installation package ONLY (Display Driver & Catalyst Control Center together) whereas in the "Option 2" (separate DD and CCC) it is missing. And because I always go the "Option 2" way (being non-English native) that was the reason why I was unable to install it.
So I tried the Option 1 "all-in-1" package and this way I managed to install the ATI driver over Realtek (BTW it is not necessary to uninstall Realtek driver first). Nevertheless I am disappointed with it because the only improvement over Realtek 2.18 driver in MC13 is that Pause works as it should (=no stutter) however fade-out on Stop does not work and the "silent stream bug" is really unacceptable because it does affect playback of ANY file with sound in ANY application...
Regarding the "silent stream bug" in ATI audio driver I mentioned this to AMD and apparently they were not aware of this bug. So I sent them all reports they asked for and recently I got message from them that my request "has been escalated to one of our experts who can better address your questions". So hopefully they will try to do something about it.
I think it would be reasonable if anybody affected by this bug would contact AMD - the more they get from users the better they could possibly solve this issue.
-
So again JRiver guys: is there anything I can do for you in order to solve these? Like sending some logs, doing some tests - whatever?
I encountered another weird issue: while playing back music using WASAPI output the recognition of inserted discs is corrupted (e.g. MC says it cannot recognise it and advice to Open / Close the drive) however once the output is changed from WASAPI to something else the disk is recognised with no problem at all! Weird...
Should be easy to reproduce (when output is changed Closing / reOpening MC is necessary)
-
Someone else recently reported a problem with WASAPI that was solved by updating the driver. Search for "sigmatel" here.
-
I installed the latest Realtek driver 2.23 and also the latest MC13 build 167 nevertheless all the issues still persist:
> stuttering loop on Pause
> fade-out on Stop does not work
> inserted disc is not recognised
These all happen with Exclusive mode enabled. When Exclusive is disabled none from the list happen.
-
No reaction? :-\
FYI I am still in contact with AMD. I reported them the "silent stream bug" which does occur with the Catalyst HDMI audio driver. I told them that when the Realtek driver is used (2.13, 2.18) then no silent stream bug happens. To my surprise they told me that the driver included in Catalyst actually IS a Realtek driver!!! So I responded that it's strange that the Realtek driver available for download from Realtek website is OK and I asked AMD what version of the driver is actually used in Catalyst. I finally received an "answer" from some unknown support person who cannot even sign his / her name:
"I have spoken with people that communicate with the driver people and they did not want to disclose that info. The people I spoke with speculated that it may be one that Realtek may have made specially for us."
So again JRiver - could you please do something about the WASAPI or is this the best we can / will get??
-
Mmmmm that is interesting if the ATI supplied dirver is from Realtek as the bugs are quite unique between them:
1) ATI Supplier Driver (CAT): Silent Stream Issue - Some Instability (I think! - I'll occasional get a MC13 freeze on bigplaylists with the stutter going one - need to reboot) and No 32-Bit Debth Support (but workaround in FFDSHOW is fine for this....). Note: One reason we don't see to much stutter with these drivers may be due to the Silent Stream Issue where it turns off the driver in these instaces hence clearing the buffer?
2) Reltek Supplier Driver: MC13 buffer clearing issue eg you get the stuttering on pause and if there is an inelegant ending to an audio stream (eg I terminate the TMT process to return to MC13 after playing Blu-ray disks). I've only noticed that Pause/Stutter issue with MC13 so I think the devs could improve this a bit!
Thanks
Nathan
-
Also I see that there are newer Realtek ATI R2.23 out - will test later and report back.
-
Also I see that there are newer Realtek ATI R2.23 out - will test later and report back.
Same issues:
1) Stutter on Pause
2) If you repeat Pause --> Play then the sound output will stop alltogether untill a "Stop" is issued.
I have logs if Matt (others?) need / want them....
Thanks
Nathan
-
Could you also check the "inserted disc is not recognised" issue I reported here? This on is really weird...
-
FYI - Cat 9.5 is out with slightly later ATI HDMI Drivers but no change I can see (hear).
-
Are you sure that by installing Catalyst 9.5 you also updated the HDMI audio driver?? I doubt that...
I downloaded Cat 9.5 for Vista 64-bit (both Options) and the HDMI audio driver is NOT included in any of them!! And if you check the "release notes" you will discover that there is no single mention of that driver neither!! Therefore I assume you are actually still using the HDMI audio driver from Cat 9.4...
BTW I got another response from AMD support asking me whether the new Cat 9.5 "have any affect on the issue" (silent stream bug). So I told them that I tried however the audio driver is missing in Cat 9.5 completely this time (e.g. not only in the Option 2 as it was with Cat 9.4) - how absurd!! Now I'm waiting for their response again...
-
It's there and the driver is upgraded from Version xxxx.46 to xxxx.48, However I had to uninstall the Realtek driver first else it is not installed (just skipped).
-
I really doubt that...
In Cat 9.4 (Option 1) when "Custom" installation is selected then it's possible to check / uncheck what should be installed and what not. If you do the same with 9.5 there - contrary to Cat 9.4 - the HDMI audio driver is NOT in the list of checkboxes thus it cannot be checked / installed (this applies to both Option 1 and Option 2). And as I wrote before even the "release notes" document does not mention this driver at all neither...
Anyway I switched back to (at least for me) issue free Cat 9.2 because I suddenly could not change the refresh rates (neither with shortcuts nor CCC) and reinstalling of 9.5 / 9.4 did not help (it actually said something like "driver could not be installed because it does not match your hardware"?!?!) -> back to Cat 9.2 and Realtek 2.23 and again everything works as it should - well of course EXCEPT the WASAPI in MC13... :-\
-
You right, the option did not appear on my first install attempt....however the HDMI Audio Install Option in Cat 9.5 appeared once I uninstalled the Realtek driver. Check your driver rev, mine was xxxx.46 in Cat 9.4 and is now xxxx.48 after the Cat 9.5 install.
-
FYI - Reltek 2.25 HDMI Drivers are out....I can see/hear to difference..still tutters on a pause (also upgraded to Vista/SP2)
-
Hmm how about some "good" news?? :'(
(anyway thanks for the info)
JRiver apparently does not care... ::)
-
JRiver apparently does not care... ::)
It's not clear that this is a JRiver problem.
-
Hi Jim,
There are definatly issues with the drivers but also with JR's implemenation, here is an example using different drivers and different WASAPI implemenations using:
ATI's CAT HDMI Driver: Stutter on Pause happens with both JR's and Reclock's WASAPI Implementation
Relteck HDMI Driver: Stutter on Pause ONLY happens with JR's Implementation
Thanks
Nathan
-
New Cat 9.6 is out (nothing in the release notes about HDMI Audio changes) and 2.25 (and soon 2.26) of the Realtek ATI driver...will have to give them a go and see if there are any fixes....
-
As expected no change :( still stutters on botht the Realtek 2.25 and the Cat 9.6 (HDMI Driver Rev xxxx.49) HDMI Drivers.
-
Any WASAPI issues should now be reported in the following thread http://yabb.jriver.com/interact/index.php?topic=52554.0