protocol-native: Use original requested latency on stream moves
authorArun Raghavan <arun.raghavan@collabora.co.uk>
Tue, 14 Jun 2011 23:38:02 +0000 (16:38 -0700)
committerArun Raghavan <arun.raghavan@collabora.co.uk>
Tue, 14 Jun 2011 23:39:47 +0000 (16:39 -0700)
commit7f48b797581e3559f97814433cf65338e4ea0f28
tree03267b9c3ef4d87c797754cf58038ecbef316c06
parent4e9328cb934ecbc1bec6acfd40994d8a048dac72
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.
src/pulsecore/protocol-native.c