alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Patrick Lai <plai@codeaurora.org>
Cc: alsa-devel <alsa-devel@alsa-project.org>, linux-arm-msm@vger.kernel.org
Subject: Re: [alsa-devel] Compressed Audio Playback/Capture through ALSA framework
Date: Wed, 16 Mar 2011 10:38:14 +0000	[thread overview]
Message-ID: <20110316103814.GA8369@sirena.org.uk> (raw)
In-Reply-To: <4D7FB076.30300@codeaurora.org>

On Tue, Mar 15, 2011 at 11:31:18AM -0700, Patrick Lai wrote:

> Is there a precedent for playback/capture compressed audio stream 
> through ALSA playback/capture interface if underlying hardware supports 
> decoder + sink & encoder + source capabilities?

I'm not sure if ALSA is the best API to use for this - the ALSA APIs are
strongly oriented around data where the size is consistent in time while
most compressed audio formats don't do that.  There's also existing APIs
in userspace like gstreamer and the various OpenMAXish things to slot in
with, everything below those is usually black boxed per implementation.

Within ASoC the current tunneled audio stuff I've seen does something
like representing the decompressor output as a DAPM input and showing
that as active when there's a stream being decoded.  Portions of the
implementation for Moorestown are in mainline in sound/soc/mid-x86,
though I'm not sure if it's all fully hooked up yet or not.

Nobody's really tried to do more yet but this may end up being the best
choice overall as there's substantial variation in how the DSPs are
structured both physically and OS wise which make the abstractions below
the userspace API level less clear.

  parent reply	other threads:[~2011-03-16 10:38 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 18:31 Compressed Audio Playback/Capture through ALSA framework Patrick Lai
2011-03-15 20:40 ` Eliot Blennerhassett
2011-03-15 20:52   ` [alsa-devel] " pl bossart
2011-03-15 23:28   ` Patrick Lai
2011-03-16  7:21     ` [alsa-devel] " Clemens Ladisch
2011-03-16  7:23     ` Jaroslav Kysela
2011-03-16 22:08     ` Patrick Lai
2011-03-17  7:39       ` [alsa-devel] " Clemens Ladisch
2011-03-16 10:38 ` Mark Brown [this message]
2011-03-16 10:59   ` Koul, Vinod
2011-03-16 11:56     ` Mark Brown
2011-03-16 12:17       ` Koul, Vinod
2011-03-16 17:52       ` pl bossart
2011-03-16 17:53         ` Mark Brown
2011-03-16 18:00           ` pl bossart
2011-03-16 18:08             ` Mark Brown
2011-03-17  2:21               ` Koul, Vinod
2011-03-17  5:00                 ` Patrick Lai
2011-03-17 11:54                   ` Mark Brown
2011-03-17 14:27                     ` pl bossart
2011-03-17 18:25                       ` Mark Brown
2011-03-17 19:16                         ` [alsa-devel] " pl bossart
2011-03-17 20:16                           ` Mark Brown
2011-03-17 21:19                             ` Patrick Lai
2011-03-17 21:25                               ` Mark Brown
2011-03-18 16:03                             ` pl bossart
2011-03-22 13:01                               ` Mark Brown
2011-03-17  5:32           ` Asus E35M1-M Pro and Realtek AL887-VD - no love from ALSA for Sourround Wojciech Myrda
2011-03-17 21:55             ` Paul Menzel
2011-03-20 10:13               ` Wojciech Myrda
2011-03-18  2:22     ` Compressed Audio Playback/Capture through ALSA framework Raymond Yau

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=20110316103814.GA8369@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=plai@codeaurora.org \
    /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;
as well as URLs for NNTP newsgroup(s).