31 Jan
2016
31 Jan
'16
8:06 a.m.
On Sun, Jan 31, 2016 at 9:42 AM, Joakim Hernberg <jhernberg(a)alchemy.lu>
wrote:
On Sun, 31 Jan 2016 14:37:13 +0100
Christian Schoenebeck <schoenebeck(a)crudebyte.com> wrote:
coreaudio has per-client latency, not just system-wide latency.
Another internal deficit was the policy how to
deal with laggy
clients. Which is quite important for consumer use cases. Instead of
simply kicking out a laggy client from the signal graph it would be
better to handle it like CoreAudio does: that is automatically
increasing the latency instead.
I'm absolutely not a fan of zombifying clients (at least up to a
certain point), but I'd also not be a fan of automagically changing
latencies... IMO it far better to just the client cause xruns and to
let the user deal with the problem himself.