[pulseaudio-discuss] [PATCH] alsa: reset watermark to initial values on resume

Colin Guthrie gmane at colin.guthr.ie
Sun Oct 9 10:01:10 PDT 2011


'Twas brillig, and Tanu Kaskinen at 09/10/11 10:34 did gyre and gimble:
> Or am I
> wrong in thinking that some applications prefer drop-outs to
> higher-than-requested latency?

I think as a general rule, applications have to make the best with what
they are given.

I mean what if you start off on a h/w alsa sink but then move to a BT or
a network sink. Latency requirements that may work fine on the h/w sink
might be completely unrealistic on the BT or network sink. Should we let
apps that have perhaps been tailored to working on h/w sinks get such
very obvious dropouts under these circumstances? I'd say no, we should
be encouraging good handling of various different latencies (especially
for media players etc.), but, of course, we do still need to honour
requested latency whenever possible.

I am of course prepared to be wrong here :D

Col

-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/



More information about the pulseaudio-discuss mailing list