From: Ricard Wanderlof <ricardw@axis.com>
To: "Rajwa, Marcin" <marcin.rajwa@linux.intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [alsa-devel] arecord: buffer-size dependency on period-size and other params
Date: Wed, 15 Jan 2020 15:52:34 +0100 [thread overview]
Message-ID: <alpine.DEB.2.20.2001151550140.9118@lnxricardw1.se.axis.com> (raw)
In-Reply-To: <7ae52bb6-1af4-897f-7de1-34196d0ed1f0@linux.intel.com>
On Wed, 15 Jan 2020, Rajwa, Marcin wrote:
> level). So to be specific I issue such command: arecod -Dplughw:0,8 -r
> 16000 -c 2 -f S24_LE --buffer_size 1280000 tmp.wav -vvv. The arecord
> response for this is buffer size of 31992 frames, 255936 bytes. Now let
> me also tell the buffer size of 1280000 bytes is the maximum buffer size
> our driver allows, likewise max period is 268800 bytes. Now if inside
Not an answer to your problem, but just a note: according to arecord -h,
the --buffer_size parameter is in frames (in your case, with S24_LE and 2
channels, the frame size is 4*2 = 8 bytes), not bytes.
/Ricard
--
Ricard Wolf Wanderlof ricardw(at)axis.com
Axis Communications AB, Lund, Sweden www.axis.com
Phone +46 46 272 2016 Fax +46 46 13 61 30
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2020-01-15 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 13:47 [alsa-devel] arecord: buffer-size dependency on period-size and other params Rajwa, Marcin
2020-01-15 14:14 ` Jaroslav Kysela
2020-01-15 14:52 ` Ricard Wanderlof [this message]
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=alpine.DEB.2.20.2001151550140.9118@lnxricardw1.se.axis.com \
--to=ricardw@axis.com \
--cc=alsa-devel@alsa-project.org \
--cc=marcin.rajwa@linux.intel.com \
/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).