All of lore.kernel.org
 help / color / mirror / Atom feed
From: pl bossart <bossart.nospam@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Anssi Hannula <anssi.hannula@iki.fi>, alsa-devel@alsa-project.org
Subject: Re: How to handle HBR pass-through? (new PCM_FORMAT?)
Date: Mon, 2 Aug 2010 14:33:38 -0500	[thread overview]
Message-ID: <AANLkTi=gj0vwsX0x3Ct9nA=GM2BrH0GVqjxLPr5VG1gy@mail.gmail.com> (raw)
In-Reply-To: <s5hocdlm1f0.wl%tiwai@suse.de>

>> Looked at gstreamer, it seems to only have ac3-in-iec61937 support currently.
>> However, I'd guess gstreamer would additionally need some ways to 1) detect if
>> HBR is supported, and 2) detect if the connected receiver supports the
>> specific codec..
>
> Reusing the existing IEC958 status bits is OK for practical POV,
> indeed.  This makes also compatible with the existing user-space stuff.
>
> But I feel a bit uncertain when looking forward for future
> development.  More discussions needed.

The automatic detection is not possible for now no matter if you rely
on gstreamer or ffmpeg or something else.
The one thing that is missing for HDMI is to make use of EDID
information to report to userspace the capabilities of the receiver so
that apps or the audio policy make educated decisions on whether to
decode locally or use pass-through modes using iec61937. The HDMI spec
only mandates stereo/48kHz, and if you have an older receiver (2 years
old...) you may not have TruHD supported there. To the best of my
knowledge, there aren't any standard controls to report what the
receiver supports. I had some discussions with Takashi on this in the
past, looks like it's time to make this happen?

  parent reply	other threads:[~2010-08-02 19:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-01 11:23 How to handle HBR pass-through? (new PCM_FORMAT?) Anssi Hannula
2010-08-02  3:18 ` pl bossart
2010-08-02  7:40   ` Anssi Hannula
2010-08-02 16:20     ` Takashi Iwai
2010-08-02 17:37       ` Anssi Hannula
2010-08-02 19:33       ` pl bossart [this message]
2010-08-03  5:51         ` Takashi Iwai

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='AANLkTi=gj0vwsX0x3Ct9nA=GM2BrH0GVqjxLPr5VG1gy@mail.gmail.com' \
    --to=bossart.nospam@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=anssi.hannula@iki.fi \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.