On Fri, 2017-04-14 at 17:02 +0200, Georg Chini wrote:
> The reported latency of source or sink is based on measured initial
> conditions.
> If the conditions contain an error, the estimated latency values may become
> negative.
> This does not indicate that the latency is indeed negative but can
On Sun, 2017-04-16 at 22:33 +0200, Enrico Weigelt, metux IT consult
wrote:
> On 15.04.2017 20:39, Tanu Kaskinen wrote:
>
> > The feature set of libpulse will necessarily track the features of the
> > pulseaudio daemon. Is the idea to take a subset of the libpulse API and
> > make that work on non-
On 17.04.2017 18:52, Tanu Kaskinen wrote:
On Fri, 2017-04-14 at 17:02 +0200, Georg Chini wrote:
The reported latency of source or sink is based on measured initial conditions.
If the conditions contain an error, the estimated latency values may become
negative.
This does not indicate that the l
Setting the allow_negative flag of pa_{source,sink}_get_latency_within_thread()
to true
leads to improved end to end latency estimation and to correct handling of
negative port
latency offsets.
---
src/modules/module-loopback.c | 49 +++
1 file changed, 31
The configured adjust time does not match exactly the real adjust time. Also
the adjust time varies. To improve latency estimation use an average of the
measured adjust times instead of the configured value in all calculations.
---
src/modules/module-loopback.c | 36 +++
