[pulseaudio-discuss] alsa sink latency - how to account for startup delay

[Raymond Yau]

>> The capture device may already started by other application (e.g. mic
peak of pavucontrol), there is some audio already captured by driver but
not read by server
>>
>> At low latency, usb pointer incremented by number of frames in urb
packet but hda intel increment by frames in dma brust
>>
>> Do the result different when you use hda-intel as source and usb audio
for playback?
>>
>
> It depends on what delay you mean. The delay I am talking about
> above stays the same, but as already said the individual sinks and
> sources have additional small delays of their own. So moving the
> source from HDA to USB increases the overall latency by about 1ms.
>

If the granularity of two sound cards are differenct? Hda  32 frames but
usb use 44.1 frames ?? Do you have enough frames to start usb audio when
using hda as source after receive 32 frames

>
>> It is unlikey module loopback can achieve lowest latency when you cannot
control start,  capture and playback of alsa sink and source
>>
>> It should have latency higher than snd-aloop,  alsaloop or latency.c
>>
>
> The low limit of module-loopback seems to be around 5ms end-to-end latency
> for HDA -> HDA. At this point tons of "memblock.c: Pool full" messages
appear
> in the log and going below 5ms will always lead to underruns.

#define TSCHED_MIN_SLEEP_USEC (10*PA_USEC_PER_MSEC) /* 10ms */ #define
TSCHED_MIN_WAKEUP_USEC (4*PA_USEC_PER_MSEC) /* 4ms */

It is because hda use timer base scheduling which has min sleep and
watermark

Are there any difference when enable/ disable timer base scheduling for usb
audio?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20160407/d6452376/attachment.html>