2012-07-04, 12:09
Maybe DDDamien can shed some light on this when he returns? The CPU utilisation in audio and the problem with 5.0 FLAC files (earlier in the thread) are also worth looking at.
(2012-07-03, 23:28)fat-tony Wrote: When you set AC3 enabled on xbmc, it is sent via the passthrough setting to which you have allocated the S/PDIF connection - so it plays on the Panasonic receiver. How is the TV connected? I am assuming that you are using an HDMI cable direct from your HTPC to the TV. Because the AC3 sound is routed via passthrough it is not being sent via HDMI. If you try to set passthrough to HDMI what happens? Some TVs can handle AC3 but others may not.
When you disable AC3 on xbmc it decodes the AC3 data internally and sends it over the HDMI connection as PCM data rather than using passthrough, which is why you can hear the sound on the TV but not on the AVR.
I just route everything through my receiver, but yours may not handle HDMI, so you may need to try an alternative strategy if you want to use the TV on its own. Have a look at this thread which discusses a patched version of xbmc which handles dual audio output. Beware, though it's a huge thread
http://forum.xbmc.org/showthread.php?tid=86038
Note that this patched version is not supported officially by xbmc and diverges from AE. There may be a way by using profiles within xbmc that you could set alternative sound configurations if you didn't want to keep switching the Directsound settings each time. I'm not sufficiently knowledgeable on profile settings to be sure whether this would work.
(2012-07-03, 20:30)Voyager-xbmc Wrote: Eureka, I found it! It was a Catalyst setting indeed, "Pulldown detection" was checked. I unchecked it and now audio playback through WASAPI doesn't cause choppy playback anymore.
Thanks fat-tony, for the help you provided by running these tests.
Quote:How the XBMC team is putting out builds when part of it is not being updated, I just do not know.