From: Eliot Blennerhassett <linux@audioscience.com>
To: alsa-devel@alsa-project.org
Subject: Re: basic questions
Date: Sat, 15 Mar 2008 11:57:38 +1300 [thread overview]
Message-ID: <200803151157.38835.linux@audioscience.com> (raw)
In-Reply-To: <75b66ecd0803141535g66aae270v5c53fb67e973566f@mail.gmail.com>
On Saturday 15 March 2008 11:35:20 Lee Revell wrote:
> On Fri, Mar 14, 2008 at 12:35 AM, Harsha priya gupta
>
> <harshapriya@gmail.com> wrote:
> > Hi,
> >
> > I am ramping up on ALSA architecture and framework. I have a couple of
> > basic questions. I apologize if these questions are very basic to be
> > raised in this mailing list. If anyone can help me find answers, it would
> > be great. Thanks in advance.
> >
> > 1. My assumption is that ALSA handles only PCM streams today. Does it
> > handle encoded streams from application to sound card (Which can do
> > hardware decoding)?
>
> Someone else could probably give a better answer, but I believe that
> currently ALSA has no API for cards that do HW decoding.
Not AFAIK, and certainly the architecture assumes a constant data rate. I.e X
bytes consumed implies elapsed time of (X * constant) = the _period_
Alsa headers do define some format constants for compressed audio.
We would like to support compressed audio for our cards, which can do hardware
decoding. I did try to implement it early on, but got lost in the quagmire of
driver midlevel code and alsa-lib.
A first step would be to allow CBR compressed formats to pass through to the
driver unaltered. For these there is a defined bits per sample, though it can
be non-integer which might be a problem.
regards
--
Eliot Blennerhassett
www.audioscience.com
next prev parent reply other threads:[~2008-03-14 22:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 4:35 basic questions Harsha priya gupta
2008-03-14 22:35 ` Lee Revell
2008-03-14 22:57 ` Eliot Blennerhassett [this message]
2008-03-18 2:01 ` Lee Revell
2008-03-18 12:50 ` Harsha priya gupta
-- strict thread matches above, loose matches on Subject: below --
2017-07-30 10:00 Basic questions tsepp2001
2017-07-30 14:24 ` Clemens Ladisch
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=200803151157.38835.linux@audioscience.com \
--to=linux@audioscience.com \
--cc=alsa-devel@alsa-project.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