Re: [PATCH 4/9] dsnoop: The delay presented to snd_pcm_status_delay() was incorrect

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

 



On Mon, 22 Jun 2020 15:15:10 +0200,
Mark Hills wrote:
> 
> This was the original bug that caused me to start looking at the
> ring buffer functions.
> 
> In the API this is documented as:
> 
>   "Delay is distance between current application frame position and
>    sound frame position. It's positive and less than buffer size in
>    normal situation, negative on playback underrun and greater than
>    buffer size on capture overrun. "
> 
> Because dsnoop was returning the buffer space available to the hardware
> the return value was always quite large, and moved in the wrong
> direction.
> 
> With this patch, dsnoop now gives results which are comparable to using
> the "hw" device directly. My test case was with snd-echo3g (Layla3G).
> 
> Signed-off-by: Mark Hills <mark@xxxxxxxx>

Thanks, applied.


Takashi



[Index of Archives]     [ALSA User]     [Linux Audio Users]     [Pulse Audio]     [Kernel Archive]     [Asterisk PBX]     [Photo Sharing]     [Linux Sound]     [Video 4 Linux]     [Gimp]     [Yosemite News]

  Powered by Linux