https://bugs.freedesktop.org/show_bug.cgi?id=81075
--- Comment #8 from Tanu Kaskinen <[email protected]> --- I attached before/after output from the test program (both were about one minute runs), as well as graphs generated from those outputs. What does the test program do, and how to interpret the output files? The program calls pa_simple_read() in an infinite loop, reading 10000 bytes at a time. After each read, the program prints "x,y" to stdout, where x is usecs since the first read (wall clock time) and y is the difference between x and the cumulative amount of audio that has been read plus the current latency as reported by pa_simple_get_latency(). I believe that if the latency reporting is perfect, y should be constant (or change slowly and steadily if there's drift between the wall clock and the sound card clock). The patch seems to improve things, but the graph after patching is still far from a straight line. I don't have time to dig in deeper at this time, so I think it's best if I apply the patch to master and leave this bug open. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.
_______________________________________________ pulseaudio-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/pulseaudio-bugs
