On Mon, Aug 19, 2013 at 6:05 AM, Tanu Kaskinen <tanu.kaskinen at linux.intel.com> wrote: > On Tue, 2013-08-13 at 01:54 -0300, jprvita at gmail.com wrote: >> From: Jo?o Paulo Rechi Vita <jprvita at openbossa.org> >> >> --- >> src/modules/bluetooth/module-bluez5-device.c | 81 ++++++++++++++++++++++++++++ >> 1 file changed, 81 insertions(+) > > Apparently you did no changes, despite my feedback: > http://lists.freedesktop.org/archives/pulseaudio-discuss/2013-July/018049.html > I don't have a deep knowledge of how the sink latency should be calculated and reported. My understanding of this is that FIXED_LATENCY_PLAYBACK_A2DP is synthesizing the over-the-air A2DP latency (which can be calculated with the current specification of AVDTP), and then we set a fixed latency for the sink in a2dp_set_bitpool adding up this FIXED_LATENCY_PLAYBACK_A2DP and the time the whole data buffer takes. If my assumptions are right, then I think we should keep using thread_info.fixed_latency in PA_SINK_MESSAGE_GET_LATENCY. What are your thoughts about it? -- Jo?o Paulo Rechi Vita http://about.me/jprvita
