On Thu, Apr 25, 2024 at 12:52:07AM +0200, Robin Gareus wrote:
> Correct, yet the effective signal delay (which can be measured)
> needs to be reported to the host to align the signal.
And that should be the average value, not the minimum which can be
achieved only during a small fraction of the
On 2024-04-25 00:10, Fons Adriaensen wrote:
The way 'fast mode' works in the x42 plugin could give you
a momentary latency of 2 ms, but the average value will be
quite a bit higher and depend on signal content.
Correct, yet the effective signal delay (which can be measured) needs to
be
On Wed, Apr 24, 2024 at 10:02:01PM +0200, Robin Gareus wrote:
> > > Except the latency in zita-at1 0.8.1 is still around ~20ms,
> >
> > It will be 10 ms when selecting low latency mode.
>
> At 48kHz sample-rate, Retuner::set_lowlat(true) sets Retuner::_latency to
> 1024.
1024 samples at 96 kHz
On 2024-04-24 21:39, Fons Adriaensen wrote:
On Tue, Apr 23, 2024 at 09:24:20PM +0200, Robin Gareus wrote:
On 2024-04-20 16:41, Fons Adriaensen wrote:
With the new logic deciding on forward / backward jumps, the
low latency mode just came for free
Except the latency in zita-at1 0.8.1 is
On Tue, Apr 23, 2024 at 09:24:20PM +0200, Robin Gareus wrote:
> On 2024-04-20 16:41, Fons Adriaensen wrote:
>
> > With the new logic deciding on forward / backward jumps, the
> > low latency mode just came for free
>
> Except the latency in zita-at1 0.8.1 is still around ~20ms,
It will be 10 ms