Re: overrun with 'arecord' - why ?

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

 



On Fri, 8 Apr 2011 21:14:55 -0700 (PDT)
Bill Unruh <unruh@xxxxxxxxxxxxxx> wrote:

[snip]
> > 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.
> 
> You said underrun, and now say overrun. Which is it?
> 
[snip]

I said _both_ overrun and underrun. When it's 'arecord', it's overrun, when
it's playback, it's underrun.

My words above mention overrun in the context of 'arecord' - the way it should
be.

The bogus duration is reported (if/when they happen) for both overruns and
underruns. I.e. it looks like the part of ALSA calculating overrun/underrun
duration is buggy.

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