aggregator: Fix min>max latency error check
authorSebastian Dröge <sebastian@centricular.com>
Fri, 6 Feb 2015 09:33:59 +0000 (10:33 +0100)
committerTim-Philipp Müller <tim@centricular.com>
Sat, 2 Dec 2017 15:10:26 +0000 (15:10 +0000)
We have to include the upstream latency, our own latency and the subclass
latency in the calculations.

FIXME: This is still not entirely correct


No differences found