From: SourceForge.net <noreply@sourceforge.net>
To: SourceForge.net <noreply@sourceforge.net>
Subject: [ sox-Bugs-3606963 ] sox prints "rec WARN alsa: over-run" during sound recording
Date: Tue, 05 Mar 2013 11:30:45 -0800 [thread overview]
Message-ID: <E1UCxZW-0002hf-RW@sfs-ml-3.v29.ch3.sourceforge.com> (raw)
Bugs item #3606963, was opened at 2013-03-05 11:30
Message generated for change (Tracker Item Submitted) made by yurivict
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=110706&aid=3606963&group_id=10706
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Yuri (yurivict)
Assigned to: Nobody/Anonymous (nobody)
Summary: sox prints "rec WARN alsa: over-run" during sound recording
Initial Comment:
I am using this command for sound recording:
rec -c 1 -t wav $WAV
In most cases it works fine. However, in ~10% cases it gets into the cycle and endlessly prints the following messages:
...
rec WARN alsa: over-run
rec WARN alsa: over-run
rec WARN alsa: over-run
rec WARN alsa: over-run
...
I think the error condition is somewhat provoked by the higher system load.
sox-14.3.2
FreeBSD 9.1-STABLE amd64
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=110706&aid=3606963&group_id=10706
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
reply other threads:[~2013-03-05 19:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.sourceforge.net/lists/listinfo/sox-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1UCxZW-0002hf-RW@sfs-ml-3.v29.ch3.sourceforge.com \
--to=sox-devel@lists.sourceforge.net \
--cc=noreply@sourceforge.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/sox.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).