Bug 56168 - Pulseaudio, a52 (or other) and S/PDIF 5.1 in Pulseaudio 2.1 don't work anymore
Summary: Pulseaudio, a52 (or other) and S/PDIF 5.1 in Pulseaudio 2.1 don't work anymore
Status: RESOLVED NOTOURBUG
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: alsa (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-19 07:08 UTC by Dario Ernst
Modified: 2012-10-24 16:24 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
ASound.conf that should(?) allow S/PDIF 5.1 via A52? (534 bytes, text/plain)
2012-10-19 07:08 UTC, Dario Ernst
Details
Ouput when starting pulseaudio with the supplied asound.conf (573.87 KB, text/plain)
2012-10-19 07:09 UTC, Dario Ernst
Details

Description Dario Ernst 2012-10-19 07:08:08 UTC
Created attachment 68785 [details]
ASound.conf that should(?) allow S/PDIF 5.1 via A52?

Hello,

since quite a time (since 0.9) i use a /etc/asound.conf like the attached file. This allowed me to choose between various outputs/configurations in pauvcontrol in the past - amongst others "Digital Surround 5.1" via my coaxial S/PDIF output. However, in the recent version*s* in Debian GNU/Linux (2.1-2 from experimental or 2.0-6 from testing+unstable) this functionality has ceased to exist. Instead i am rewarded with a very long log file where pulse would complain over parameters beeing riduclously large. I'll attach that logfile to the next comment since i don't know how to attach two files to one report(?).

I'd be grateful for any hints, tips or fixes - even dirty hacks to workaround this problem!

Best Regards
- Dario Ernst
Comment 1 Dario Ernst 2012-10-19 07:09:00 UTC
Created attachment 68786 [details]
Ouput when starting pulseaudio with the supplied asound.conf
Comment 2 Dario Ernst 2012-10-19 07:22:03 UTC
By the way, a few versions and infos of the Software and Hardware on this box:
alsa-base: 1.0.25+2+nmu2
alsa-tools: 1.0.25-2
alsa-utils: 1.0.25-3
alsa-firmware-loaders: 1.0.25-2
Kernel: 3.5.5-1~experimental.1
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)

If any more info is needed, please ask! :)
Comment 3 Tanu Kaskinen 2012-10-24 10:28:53 UTC
The "out of range" flooding seems to be coming from the a52 plugin. How did you install it? You're using Debian - does Debian provide the a52 plugin, or did you have to install it in some unconventional way? I'm thinking that if the a52 plugin and the rest of alsa came from different sources, they may not be compatible (the weird out of range values would hint to that direction).

For some more information, you could take the log again, this time with even more verbosity. I guess you used the -v parameter when starting pulseaudio. Use -vv (or even more vees) to get the full debug log. You know you have enough vees when you start to get lines in the log that have "D:" prefix (now the lowest log level seems to be "I:").
Comment 4 Dario Ernst 2012-10-24 16:24:40 UTC
Hey,

thanks for offering your expertise and pointing out that this isn't coming from pulseaudio itself but from the a52 stuff. After trying to uninstall/reinstall libav*, libasound2-plugins and pulseaudio (so that i'm sure everything is from the packages, but i was quite sure before!) it still didn't work. I then tried to build alsa-plugins from hand and put the a52 .so where it belongs - to no effect.

Then after understanding that the a52 encoding is actually handeled by libav*, i dug into that and discovered that i actually have libav* from debian-multimedia.org ... which was the cause! I installed the "correct" libavcodec53 version from debian itself, and not DMO - an *bang* it worked!

You've helped me so much on this! Thank you!


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.