From: Lee Revell <rlrevell@joe-job.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: ALSA devel <alsa-devel@lists.sourceforge.net>
Subject: Re: ac3 in/out
Date: Tue, 21 Mar 2006 13:17:04 -0500 [thread overview]
Message-ID: <1142965025.4532.132.camel@mindpipe> (raw)
In-Reply-To: <1142936836.4759.3.camel@localhost>
On Tue, 2006-03-21 at 11:27 +0100, Johannes Berg wrote:
> Hi,
>
> From what I've seen about ac3 in and also out, the support in alsa for
> that is more of a hack, and the data that is passed down the pcm
> interface actually contains the channel status bits for some drivers...
> Working on the new Apple stuff this isn't possible -- only some channel
> status bits can be set by the software, some are fixed. And they aren't
> interleaved in the stream, but set externally.
>
> So the question is -- are there any plans to abstract some digital out
> API within alsa? Otherwise the userspace will need to handle all kinds
> of different devices differently since the data on the stream is
> essentially the same as the data the chipset needs.
I don't understand - ALSA fully supports AC3 passthrough and digital
audio.
What is the exact problem you are trying to solve?
Lee
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next prev parent reply other threads:[~2006-03-21 18:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 10:27 ac3 in/out Johannes Berg
2006-03-21 18:17 ` Lee Revell [this message]
2006-03-21 18:37 ` Takashi Iwai
2006-03-22 9:41 ` Johannes Berg
2006-03-22 10:43 ` Takashi Iwai
2006-03-22 10:54 ` Johannes Berg
2006-03-22 11:09 ` Takashi Iwai
2006-03-22 11:12 ` Johannes Berg
2006-03-22 21:39 ` Benjamin Herrenschmidt
2006-03-23 17:06 ` Johannes Berg
2006-03-22 0:20 ` James Courtier-Dutton
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=1142965025.4532.132.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=johannes@sipsolutions.net \
/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