09.12.2015 01:47, Tanu Kaskinen пишет:
On Wed, 2015-02-25 at 19:43 +0100, Georg Chini wrote:
---
src/modules/module-loopback.c | 18 +-
1 file changed, 17 insertions(+), 1 deletion(-)
The commit message should say something about why the jitter is tracked.
diff --git a/src
This part is system specific, if we request it - we will get them,
otherwise tolerate that it's either unsupported or just disabled.
Caught on NetBSD.
---
src/daemon/caps.c | 4
1 file changed, 4 deletions(-)
diff --git a/src/daemon/caps.c b/src/daemon/caps.c
index fd135c0..81c4b25 100644
-
On Wed, 2015-02-25 at 19:43 +0100, Georg Chini wrote:
> With USB or Bluetooth sources, the controller exhibited random
> deviations of new_rate around the correct value, due to latency jitter.
> Use the already-known latency error due to jitter, and assume that there
> is no latency difference if t
On Wed, 2015-02-25 at 19:43 +0100, Georg Chini wrote:
> ---
> src/modules/module-loopback.c | 18 +-
> 1 file changed, 17 insertions(+), 1 deletion(-)
The commit message should say something about why the jitter is tracked.
> diff --git a/src/modules/module-loopback.c b/src/modul
On Mon, 2015-12-07 at 18:19 +0200, Tanu Kaskinen wrote:
> On Fri, 2015-08-21 at 23:29 +0300, Joonas Govenius wrote:
> > This allows calling a user-specified external program whenever a
> > source or sink is suspended or resumed (by specifying
> > external_suspend_handler="" as an option to
> > modu
