Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: korgman <korgie@gmail.com>, alsa-devel@alsa-project.org
Subject: Re: arecord - bug with big file?
Date: Mon, 05 May 2014 11:46:54 +0200	[thread overview]
Message-ID: <53675E0E.2060303@ladisch.de> (raw)
In-Reply-To: <5366A35F.4040308@gmail.com>

korgman wrote:
> 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

This is the time needed for 2^31 bytes.  Stopping recording after that
is a feature because .wav files (as supported by arecord) have a 2 GB
limit.  When recording to a file, it would be possible to create
multiple files, but this is not possible with stdout.

Use "-t raw" to avoid the .wav restrictions.  (This requires you to
tell aplay about the format.)


Regards,
Clemens

      parent reply	other threads:[~2014-05-05  9:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-04 20:30 arecord - bug with big file? korgman
2014-05-04 23:04 ` Daniel Mack
2014-05-05  9:46 ` 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=53675E0E.2060303@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=korgie@gmail.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