From: Clemens Ladisch <clemens@ladisch.de>
To: "Harsha, Priya" <priya.harsha@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: issue at 44.1 Khz capturing
Date: Mon, 10 Aug 2009 15:34:09 +0200 [thread overview]
Message-ID: <4A8021D1.10602@ladisch.de> (raw)
In-Reply-To: <98769532B4BB14429434178695419EAE5F937AC6@bgsmsx501.gar.corp.intel.com>
(please don't top-post)
Harsha, Priya wrote:
> I see that the buffer allocated is 22050 bytes (and not 22052 bytes).
> Yes the hardware supports buffers which are not multiple of period size.
But there may be a (driver) bug that affects the last byte.
Try calling
snd_pcm_hw_constraint_integer(runtime, SNDRV_PCM_HW_PARAM_PERIODS);
in the open callback.
> Can I forcefully set my buffer size to 22052 bytes
Try the --buffer-size and --period-size parameters of arecord.
HTH
Clemens
prev parent reply other threads:[~2009-08-10 13:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 10:06 issue at 44.1 Khz capturing Harsha, Priya
2009-08-10 10:14 ` James Courtier-Dutton
2009-08-10 11:51 ` Clemens Ladisch
2009-08-10 13:12 ` Harsha, Priya
2009-08-10 13:34 ` Clemens Ladisch [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=4A8021D1.10602@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=priya.harsha@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