The native protocol reports too low latencies for streams connected to monitor sources
@tanuk
Submitted by Tanu Kaskinen Assigned to pul..@..op.org
Description
When the native protocol gathers the timing information for capture streams in the SOURCE_OUTPUT_MESSAGE_UPDATE_LATENCY handler, it doesn't call pa_source_output_get_latency_within_thread(). This means that data in pa_source_output.delay_memblockq isn't taken into account in the latency calculation, resulting in the latency reports being too low. The delay memblockq only contains data for streams that are connected to monitor sources, though, so the impact of this bug is limited to those streams.
This bug report is only based on reading the code, I haven't done experiments that would prove that there really is a bug.