From: korgman <korgie@gmail.com>
To: alsa-devel@alsa-project.org
Subject: arecord - bug with big file?
Date: Sun, 04 May 2014 23:30:23 +0300 [thread overview]
Message-ID: <5366A35F.4040308@gmail.com> (raw)
Bugtracker is down ->
https://bugtrack.alsa-project.org/alsa-bug
from main page ->
http://alsa-project.org
So, excuse my reporting here.
I can't record with arecord for long periods.
time arecord -f dat -D hw:0,0 | aplay
Recording WAVE 'stdin' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo
Playing WAVE 'stdin' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo
real 186m25.375s
user 1m26.204s
sys 0m20.772s
It seems that this bug was also reported there.
https://bugzilla.redhat.com/show_bug.cgi?id=213783
cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version k3.12.9x40-122l. (custom kernel)
arecord --version
arecord: version 1.0.27.1 by Jaroslav Kysela <perex@perex.cz>
I now trying with sox (rec test.wav) to check if sox is ok.
Thank you for reading this!
next reply other threads:[~2014-05-04 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 20:30 korgman [this message]
2014-05-04 23:04 ` arecord - bug with big file? Daniel Mack
2014-05-05 9:46 ` Clemens Ladisch
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=5366A35F.4040308@gmail.com \
--to=korgie@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox