Re: overrun with 'arecord' - why ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 8 Apr 2011 22:34:40 -0500
James Shatto <wwwshadow7@xxxxxxxxx> wrote:

> > Please reread my message in this thread on 'sox' - it contains the complete
> > command line I've used.
> 
> So apples to oranges?  since your sox only does 4 seconds (trim 1 5)
> and your arecord does 6 seconds -d 6.  Statistically that's 50% more
> opportunity for failure in arecord.
> 
> -----
> 
> Did omitting -D help?  did adding -t wav help, so it doesn't have to
> assume stuff (or not) based only on file extension?
> 
> milliseconds are what?  1/1000 of a second.  So 855507586.521 is about
> 85,550 seconds.  Or roughly 1,426 minutes or roughly 23 hours and 46
> minutes.  Kind of odd for a 6 second capture don't you think?  Or is
> the result and the example unrelated?
> 
> - James
> 
>

No, it is the same kind of fruit. When I run 'arecord', I run it sometimes with
VU meter, so I see when relative to the stream overruns happen. They can happen
anywhere - in the beginning, in the middle, closer to the end.

And I tried 'sox' with different lengths, including 6 seconds - no overruns.

Regards,
  Sergei.

------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user


[Index of Archives]     [ALSA Devel]     [Linux Audio Users]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]

  Powered by Linux