tree 19a1b433644ba9447e41e0291b91fb2a88ad80d1
parent a42ab58588991b7f592d4732a9176f51c7708c4e
author Sebastian Dröge <sebastian@centricular.com> 1535704907 +0300
committer Sebastian Dröge <sebastian@centricular.com> 1535704907 +0300

pad: Accumulate live/non-live latency values separately

And only ever use the non-live values if all pads are non-live,
otherwise only use the results of all live pads.

It's unclear what one would use the values for in the non-live case, but
by this we at least pass them through correctly then.

This is a follow-up for 794944f779f954375fc74a3fffcc2067bba6a3e5, which
causes wrong latency calculations if the first pad is non-live but a
later pad is actually live. In that case the live values would be
accumulated together with the values of the non-live first pad,
generally causing wrong min/max latencies to be calculated.