diff options
author | Arun Raghavan <arun.raghavan@collabora.co.uk> | 2011-06-14 16:38:02 -0700 |
---|---|---|
committer | Arun Raghavan <arun.raghavan@collabora.co.uk> | 2011-06-14 16:39:47 -0700 |
commit | 7f48b797581e3559f97814433cf65338e4ea0f28 (patch) | |
tree | 03267b9c3ef4d87c797754cf58038ecbef316c06 /m4/tls.m4 | |
parent | 4e9328cb934ecbc1bec6acfd40994d8a048dac72 (diff) |
protocol-native: Use original requested latency on stream moves
We were calculating new latency based on the latency set on the old
sink/source, rather than the actual latency requested by the client.
Over a series of moves, this will lead the latency being ~halved each
time, resulting in an eventual rewind flood from a latency that cannot
be handled.
Diffstat (limited to 'm4/tls.m4')
0 files changed, 0 insertions, 0 deletions