(2012-07-05, 15:04)lndiana Wrote: @knight2000 : yes, with a M-Audio Revolution 5.1 sound card, set up with 192 000kHz output.
It work great, in Wasapi and DirectSound. Why?

(2012-07-06, 08:50)knight2000 Wrote:

(2012-07-05, 15:04)lndiana Wrote: @knight2000 : yes, with a M-Audio Revolution 5.1 sound card, set up with 192 000kHz output.
It work great, in Wasapi and DirectSound. Why?

I ask because i tried one of the recent builds and sound did work but the speaker mapping was not right. Like on a 7.1 configuration xbmc was playing 7.1 test files as a 5.1 setup meaning side tracks and rear tracks were being played thru the side speakers. Windows is setup as 7.1 so its xbmc, so makes me wonder :/

PS: The Test track is from http://www.demo-world.eu/trailers/high-definition-trailers.php and its named hd_dts_hd_master_audio_sound_check_7_1_lossless

(2012-07-06, 09:44)Nimo Wrote:

(2012-07-06, 08:50)knight2000 Wrote:

(2012-07-05, 15:04)lndiana Wrote: @knight2000 : yes, with a M-Audio Revolution 5.1 sound card, set up with 192 000kHz output.
It work great, in Wasapi and DirectSound. Why?

I ask because i tried one of the recent builds and sound did work but the speaker mapping was not right. Like on a 7.1 configuration xbmc was playing 7.1 test files as a 5.1 setup meaning side tracks and rear tracks were being played thru the side speakers. Windows is setup as 7.1 so its xbmc, so makes me wonder :/

PS: The Test track is from http://www.demo-world.eu/trailers/high-definition-trailers.php and its named hd_dts_hd_master_audio_sound_check_7_1_lossless

please poste log file

(2012-07-06, 18:30)flanger216 Wrote: Been following this development for a while, and first wanted to thank all involved developers for such a great job.

There is one issue with the current AE development pertaining to ATI HDMI chips. And if this has been resolved at some point, then apologies for reiterating it. Basically, the AE implementation currently works great with ATI's in-house HDMI drivers, but it doesn't seem to initialize or work at all when using Realtek's HDMI drivers. I believe this is because AE only uses the WASAPI 'Event Mode' interface. ATI's drivers support 'event mode,' but Realtek's drivers do not. I have also verified this with Foobar's WASAPI implementation --- normal exclusive mode works perfectly on Realtek's drivers, but the 'Event Mode' option returns an "Invalid Argument" error code.

Now, the obvious solution would be simply to install ATI's drivers, but in many other respects Realtek's drivers are superior. Realtek's drivers tend to cause fewer handshake issues with some receivers, they support 32bit audio paths (ATI's are limited to 24bit), they handle atypical channel outputs more consistently (3.0 in particular), and most importantly, they support Windows audio enhancements such as 'speaker fill.' Like some users, I particularly need speaker fill (for various boring reasons pertaining to computer games and Netflix), so I'm stuck with the Realtek drivers. And FWIW, Realtek's drivers tend to get updated more frequently and, of course, they themselves actually make the HDMI chips, so the ATI drivers are really just delayed, modified versions of the Realtek ones anyway.

All other media software I've used has always defaulted to normal WASAPI exclusive mode and then provided 'Event Mode' as an option, usually with a warning that 'your hardware might not support this.' So that might be the best way to go with XBMC, as well. Of course, I'm just an audio engineer and not a programmer, so I might be gabbing out my backside, so to speak