From: Eliot Blennerhassett <linux@audioscience.com>
To: Tobin Davis <tdavis@dsl-only.net>
Cc: ALSA Developers <alsa-devel@alsa-project.org>
Subject: Re: support for hardware encode/decode of compressed formats
Date: Sat, 05 Apr 2008 13:26:40 +1300 [thread overview]
Message-ID: <47F6C740.4020108@audioscience.com> (raw)
In-Reply-To: <1207330707.1496.199.camel@razman>
Tobin Davis wrote:
> Are there any alsa supported sound cards that do hardware audio decoding
> for MP3/WMA and otehr formats? I'd like to look at the mechanism used
> to connect the cards to the data stream.
This has come up a couple of times recently.
Todays answer is that ALSA has no support for getting the encoded data
through to the cards.
We are interested in this and would like to see it happen because our
cards do support MP2 and MP3 decode and encode in DSP on the cards.
Applications wanting to use this capability currently must use our HPI
driver directly (the primary example on Linux is Rivendell radio
automation software http://www.rivendellaudio.org)
One assumption that alsa makes is that a "period" equates to a fixed
amount of time, and a fixed amount of audio data. This is not the case
for Variable bitrate mpeg etc. And even with fixed bitrate, the bits
per sample is fractional E.g. 128kbps/44.1k = 2.90249... bits per sample
frame.
One of the two assumptions about the period would have to be relaxed to
allow alsa to maybe work with compressed data. Probably the time one.
I.e. a period means the decoder has consumed X bytes, but this doesn't
correspond to any particular amount of time.
regards
Eliot Blennerhassett *:-{)>
AudioScience, Inc. (New Zealand Office)
<http://www.audioscience.com>
next prev parent reply other threads:[~2008-04-05 0:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 17:38 Sound card question Tobin Davis
2008-04-05 0:26 ` Eliot Blennerhassett [this message]
2008-04-07 8:37 ` support for hardware encode/decode of compressed formats Pavel Hofman
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=47F6C740.4020108@audioscience.com \
--to=linux@audioscience.com \
--cc=alsa-devel@alsa-project.org \
--cc=tdavis@dsl-only.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 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.