From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: alsa-devel@alsa-project.org
Subject: Sample format coversion bug?
Date: Fri, 26 Oct 2007 19:18:42 +0600 [thread overview]
Message-ID: <4721E932.5090603@ums.usu.ru> (raw)
Hello,
I am writing an application that uses ALSA, and I don't want to write
code to support all possible sample formats. On IRC, I asked whether it
is OK to support only S24 format internally and rely on the "plug" to do
the required conversion. I got a positive answer, but, when testing my
application against my SAA7134-based tuner as a capture device, found
that it doesn't work.
The problem is also reproducible with "arecord". Given that plughw:1
refers to a SAA7134-based tuner (which obviously doesn't support S24_LE
natively), running the following command
arecord -vvv -f S24_LE -c 2 -r 32000 -D plughw:1 /dev/null
produces the following output:
ALSA lib pcm_mmap.c:369:(snd_pcm_mmap) mmap failed: Invalid argument
arecord: set_params:961: Unable to install hw params:
ACCESS: RW_INTERLEAVED
FORMAT: S24_LE
SUBFORMAT: STD
SAMPLE_BITS: 32
FRAME_BITS: 64
CHANNELS: 2
RATE: 32000
PERIOD_TIME: 125000
PERIOD_SIZE: 4000
PERIOD_BYTES: 32000
PERIODS: 4
BUFFER_TIME: 500000
BUFFER_SIZE: 16000
BUFFER_BYTES: 128000
TICK_TIME: 4000
This is on Debian, the kernel is 2.6.22-2-amd64, libasound2 is
1.0.14a-2. Same for S32_LE.
--
Alexander E. Patrakov
next reply other threads:[~2007-10-26 13:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 13:18 Alexander E. Patrakov [this message]
2007-10-29 8:08 ` Sample format coversion bug? Takashi Iwai
2007-10-29 11:01 ` Alexander E. Patrakov
2007-10-29 9:05 ` Takashi Iwai
2007-10-29 11:21 ` Alexander E. Patrakov
2007-10-29 15:04 ` Alexander E. Patrakov
2007-10-29 18:47 ` Trent Piepho
2007-10-30 16:24 ` mmap support in saa7134-alsa (was: Sample format coversion bug?) Alexander E. Patrakov
2007-10-31 8:34 ` Takashi Iwai
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=4721E932.5090603@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--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 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.