On 15.02.2017 11:17, Tanu Kaskinen wrote: > On Tue, 2017-02-14 at 14:33 +0100, Georg Chini wrote: >> The PA_SINK_GET_LATENCY message handler falsely always added the A2DP latency as fixed >> latency instead of the profile specific constant. >> >> --- >> src/modules/bluetooth/module-bluez5-device.c | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/src/modules/bluetooth/module-bluez5-device.c b/src/modules/bluetooth/module-bluez5-device.c >> index 47842f7..976818b 100644 >> --- a/src/modules/bluetooth/module-bluez5-device.c >> +++ b/src/modules/bluetooth/module-bluez5-device.c >> @@ -1051,7 +1051,7 @@ static int sink_process_msg(pa_msgobject *o, int code, void *data, int64_t offse >> wi = pa_bytes_to_usec(u->write_index, &u->sample_spec); >> } >> >> - *((pa_usec_t*) data) = FIXED_LATENCY_PLAYBACK_A2DP + wi > ri ? FIXED_LATENCY_PLAYBACK_A2DP + wi - ri : 0; >> + *((pa_usec_t*) data) = u->sink->thread_info.fixed_latency + wi > ri ? u->sink->thread_info.fixed_latency + wi - ri : 0; >> >> return 0; >> } > The same problem exists in for the source latency handler. > sent a corrected patch
