All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: Lee Revell <rlrevell@joe-job.com>,
	ALSA devel <alsa-devel@lists.sourceforge.net>
Subject: Re: ac3 in/out
Date: Wed, 22 Mar 2006 10:41:22 +0100	[thread overview]
Message-ID: <1143020483.11724.46.camel@localhost> (raw)
In-Reply-To: <s5hbqvzzlss.wl%tiwai@suse.de>

[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]

On Tue, 2006-03-21 at 19:37 +0100, Takashi Iwai wrote:

> The SPDIF status bits are generic and rather depending on the data
> than the device you output.  That is, more or less, the SPDIF I/O is
> abstracted.

Are you talking about alsa or spdif itself?

> Regarding AC3, I'm not against to create a new easy-to-use API
> function.  One reason is that AC3 over SPDIF needs conversions of
> packets and also requires the sync work, in addition to the SPDIF
> status bits mentioned in the above.  Such a job can be certainly
> hidden in the system instead of application itself.

Yes, but apparently some hardware is capable of doing the conversion
(the chip apple uses for example: pcm3052, download data sheet for
pcm3052a if you're interested, it's the same chip)

On the other hand, some other chips seem to rely on software to
multiplex the channel status bits into the bitstream which is currently
done by userspace as far as I can tell.

> If we create a new one, we should better think of other compressed
> formats, too...

They're essentially the same to the spdif output though -- just a
non-pcm bitstream.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]

  reply	other threads:[~2006-03-22  9:41 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
2006-03-21 18:37   ` Takashi Iwai
2006-03-22  9:41     ` Johannes Berg [this message]
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=1143020483.11724.46.camel@localhost \
    --to=johannes@sipsolutions.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=rlrevell@joe-job.com \
    --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.