From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Rajeev kumar <rajeev-dlh.kumar@st.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: overrun in case of record
Date: Tue, 6 Sep 2011 11:01:38 -0700 [thread overview]
Message-ID: <20110906180138.GC2924@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4E65E934.2070706@st.com>
On Tue, Sep 06, 2011 at 03:04:44PM +0530, Rajeev kumar wrote:
> I am using arecord for capturing data.
> #arecord -f dat > t
> overrun!!! (at least 32.949 ms long)
>
> Overrun issue: The issue is only reproducible if we try to record
> for more than 40 sec.The strange part is that Instead of overrun
> condition generated,
> it will record complete data for 10sec.(This is verified with the
> number of bytes recorded).
> So could you please let me know whether this is an error condition
> or just a warning.
An overrun means that your driver is producing data faster than the
application is reading it and ran out of buffer space. This may mean
that you're running at the wrong sample rate, or it may mean that your
system is just too slow to do recordings.
> pcm_read error: For this I have seen a bug is locked in the
> bugzila(*Bug 472469* <show_bug.cgi?id=472469> -arecord: input/output
> error ). and the status is closed saying insufficient data.
> Could you please let me know what is the meaning of this bug? Is it
> like, data is not available in the buffer and pcm_read from the user
> space fails? But why this situation will
> arise?
You'll need to investigate the bug.
next prev parent reply other threads:[~2011-09-06 18:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 9:34 overrun in case of record Rajeev kumar
2011-09-06 18:01 ` Mark Brown [this message]
2011-09-07 4:14 ` Rajeev kumar
2011-09-07 8:35 ` Clemens Ladisch
2011-11-17 13:35 ` Exporting playback and capture capability to user space Rajeev kumar
2011-11-17 15:19 ` Mark Brown
2011-11-21 5:49 ` Rajeev kumar
2011-11-21 6:23 ` Vinod Koul
2011-11-22 4:27 ` Rajeev kumar
2011-11-22 13:08 ` Mark Brown
2011-11-23 4:36 ` Rajeev kumar
2011-12-02 10:50 ` Rajeev kumar
2011-12-02 11:50 ` Vinod Koul
2012-01-09 6:31 ` Rajeev kumar
2012-01-12 8:45 ` Rajeev kumar
2011-11-21 10:55 ` Mark Brown
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=20110906180138.GC2924@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=rajeev-dlh.kumar@st.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).