From: "Alexander E. Patrakov" <patrakov@gmail.com>
To: bencoxdev@gmail.com,
David Henningsson <david.henningsson@canonical.com>,
ALSA Mailing list <alsa-devel@alsa-project.org>
Subject: Re: Nodes, Widgets, ELD and Digital Surround 5.1 (HDMI) Output?
Date: Thu, 04 Dec 2014 17:34:25 +0500 [thread overview]
Message-ID: <548054D1.1000302@gmail.com> (raw)
In-Reply-To: <46543BFB759444F4B56F5153F4727DEE@Lyra>
04.12.2014 15:55, bencoxdev@gmail.com wrote:
> Hi Guys,
> Thank you for your input it's much appreciated.
> I have now produced the pulse audio log as suggested and it
> appears that
> when an attempt to open the Digital Surround 5.1 device, it fails with a
> "No such file or directory" error. Here is a snippet of the log
> showing the
> error.
> ( 0.456| 0.000) D: [pulseaudio] alsa-mixer.c: Looking at profile
> output:iec958-ac3-surround-51
> ( 0.456| 0.000) D: [pulseaudio] alsa-mixer.c: Checking for
> playback on Digital Surround 5.1 (IEC958/AC3) (iec958-ac3-surround-51)
> ( 0.456| 0.000) D: [pulseaudio] alsa-util.c: Trying a52:1 with
> SND_PCM_NO_AUTO_FORMAT ...
> ( 0.456| 0.000) I: [pulseaudio] (alsa-lib)pcm.c: Unknown PCM a52:1
> ( 0.456| 0.000) I: [pulseaudio] alsa-util.c: Error opening PCM
> device a52:1: No such file or directory
> So I guess the next question is what is responsible for producing the
> required device?
This is not the correct device. This is a software encoder that is not
installed on your computer. It will degrade audio quality by
compression, eat CPU time, kill PulseAudio for exhausting the real-time
budget, and is generally not needed on HDMI, because HDMI can transport
PCM 5.1 streams just fine.
Please see my earlier reply how to force PulseAudio into opening the
correct HDMI device.
--
Alexander E. Patrakov
next prev parent reply other threads:[~2014-12-04 12:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 15:28 Nodes, Widgets, ELD and Digital Surround 5.1 (HDMI) Output? bencoxdev
2014-12-03 7:34 ` David Henningsson
2014-12-03 7:58 ` Alexander E. Patrakov
2014-12-04 10:55 ` bencoxdev
2014-12-04 12:08 ` Raymond Yau
2014-12-04 12:34 ` Alexander E. Patrakov [this message]
2014-12-05 2:33 ` Raymond Yau
2014-12-05 9:41 ` bencoxdev
2014-12-05 10:49 ` Alexander E. Patrakov
2014-12-08 14:40 ` bencoxdev
2014-12-08 16:38 ` Alexander E. Patrakov
2014-12-08 17:42 ` bencoxdev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=548054D1.1000302@gmail.com \
--to=patrakov@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=bencoxdev@gmail.com \
--cc=david.henningsson@canonical.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox