On Thu, 2017-02-16 at 13:10 +0100, Georg Chini wrote:
> On 16.02.2017 12:59, Tanu Kaskinen wrote:
> > On Fri, 2017-02-10 at 14:38 +0100, Georg Chini wrote:
> > > Hi,
> > >
> > > during my work on module-loopback I came upon an issue regarding the
> > > handling
> > > of the port latency offsets.
On 16.02.2017 13:10, Georg Chini wrote:
On 16.02.2017 12:59, Tanu Kaskinen wrote:
On Fri, 2017-02-10 at 14:38 +0100, Georg Chini wrote:
Hi,
during my work on module-loopback I came upon an issue regarding the
handling
of the port latency offsets.
The functions
On 16.02.2017 12:59, Tanu Kaskinen wrote:
On Fri, 2017-02-10 at 14:38 +0100, Georg Chini wrote:
Hi,
during my work on module-loopback I came upon an issue regarding the
handling
of the port latency offsets.
The functions pa_{source,sink}_get_latency_within_thread() return the
latencies
On Fri, 2017-02-10 at 14:38 +0100, Georg Chini wrote:
> Hi,
>
> during my work on module-loopback I came upon an issue regarding the
> handling
> of the port latency offsets.
> The functions pa_{source,sink}_get_latency_within_thread() return the
> latencies
> including the offset. Those
Hi,
during my work on module-loopback I came upon an issue regarding the
handling
of the port latency offsets.
The functions pa_{source,sink}_get_latency_within_thread() return the
latencies
including the offset. Those functions are used to determine the amount
that has
to be rewound during
