Bug 69132 - The native protocol reports too low latencies for streams connected to monitor sources
Summary: The native protocol reports too low latencies for streams connected to monito...
Status: RESOLVED MOVED
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: modules (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-09 08:27 UTC by Tanu Kaskinen
Modified: 2018-07-30 09:59 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Tanu Kaskinen 2013-09-09 08:27:55 UTC 
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.
Comment 1 GitLab Migration User 2018-07-30 09:59:27 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/152.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.