On Sat, Apr 25, 2020 at 6:50 PM Gregor Pintar <grpintar@xxxxxxxxx> wrote: > > On Fri, Apr 24, 2020 at 6:44 PM Alexander Tsoy <alexander@xxxxxxx> wrote: > > > > В Пт, 24/04/2020 в 17:02 +0200, Gregor Pintar пишет: > > > On Fri, Apr 24, 2020 at 4:24 AM Alexander Tsoy <alexander@xxxxxxx> > > > wrote: > > > > This patch fixes this issue by implementing a different algorithm > > > > for > > > > frame size computation. It is based on accumulating of the > > > > remainders > > > > from division fs/fps and it doesn't accumulate errors over time. > > > > This > > > > new method is enabled for synchronous and adaptive playback > > > > endpoints. > > > > > > > > > > Hm, I still sometimes get click usually in about first 2 seconds, > > > but it is hard to reproduce. > > > > I wonder if it's because the driver doesn't honor wLockDelay. Anyway, > > the second patch can be reverted if there are still issues with 2nd gen > > Scarletts. > > > > I just got click with async. I better stop testing before I get click > with 48kHz. > Could this wLockDelay affect async too? > > Does anybody else still get clicks? I would totally think I'm mad, if > I would not > record them. Maybe it is something else. > > I guess I will just switch back to 48kHz and try not too think about it. Guess what 48kHz sync and async clicks too. It could be related to running capture at the same time. It seems fine with 44.1kHz so far with input muted. Sorry for all this spam.
