From: Mike Looijmans <mike.looijmans@topic.nl>
To: alsa-devel@alsa-project.org
Subject: Sample rates above 192000
Date: Wed, 17 Apr 2013 10:21:20 +0200 [thread overview]
Message-ID: <516E5B80.804@topic.nl> (raw)
In-Reply-To: <5166B247.807@metafoo.de>
I'm trying to use "my" hardware at a 204800 sample rate. I've changed
the DAI and codec limits to match. If I limit them to anything below
192kHz, everything behaves as expected and I can record at up to that
rate, also if that rate is not a multiple of 48k or 44k1 (using
"SNDRV_PCM_RATE_KNOT" constant).
When I specifiy anything over 192000, I bump onto some ceiling, and I
cannot figure out what's causing it. I patched alsa-utils to allow
>192000 already (there is a silly check on that in aplay.c which bails
out early without asking the driver).
# arecord -D hw:ADC8 --duration=5 -f S32_LE -c 2 -r 204800
/tmp/recording.wav
Recording WAVE '/tmp/recording.wav' : Signed 32 bit Little Endian, Rate
204800 Hz, Stereo
Warning: rate is not accurate (requested = 204800Hz, got = 192000Hz)
please, try the plug plugin
#
# arecord -D hw:ADC8 --duration=5 -f S32_LE -c 2 -r 192000
/tmp/recording.wav
Recording WAVE '/tmp/recording.wav' : Signed 32 bit Little Endian, Rate
192000 Hz, Stereo
#
I also tried a "grep" on the kernel (i'm still on 2.3.7 though) source
files on "192000" but found nothing that would limit the sample rate to
that. I'm running out of ideas. How can I break this limit? Or where in
the kernel can I find the part that calculates the max rate?
Mike.
next prev parent reply other threads:[~2013-04-17 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <516688D4.9040700@zonque.org>
2013-04-11 10:51 ` Enhance support for SigmaDSP chips Lars-Peter Clausen
2013-04-11 12:02 ` Daniel Mack
2013-04-11 12:53 ` Lars-Peter Clausen
2013-04-17 8:21 ` Mike Looijmans [this message]
2013-04-17 11:44 ` Sample rates above 192000 Mike Looijmans
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=516E5B80.804@topic.nl \
--to=mike.looijmans@topic.nl \
--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.