On Sat, 26 Jun 2010, David Dillow wrote: > When using a timing voice to clock out periods during capture, the > driver would slowly loose synchronization and never catch up, eventually > reaching a point where it no longer generated interrupts. To avoid > this situation, the virtual period clocking was changed to shorten the > next timing period when our timing voice falls too far behind the > capture voice. In addition, the first virtual period for the timing > voice was slightly too short, causing the timing voice to initially be > ahead of the capture voice. > > While tracking down this problem, I noticed that the expected sample > offset was being incorrectly initialized, causing an overrun to be > incorrectly reported when the timing voice happened to be perfectly > synchronized. > > Reported-by: Hans Schou <linux@xxxxxxxx> > Signed-off-by: Dave Dillow <dave@xxxxxxxxxxxxxx> Thanks for the patch. I applied it to my GIT tree. Jaroslav ----- Jaroslav Kysela <perex@xxxxxxxx> Linux Kernel Sound Maintainer ALSA Project, Red Hat, Inc. _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
