[LAD] Proposals for JACK

[Paul Davis]

On Wed, May 23, 2012 at 3:30 PM, Nikita Zlobin <cook60020tmp at mail.ru> wrote:

> What things, you think, may need to create such all-purpose API?


What is the use case for "Per client time wheel management." ?
What is the use case for "Waiting wheel. ?"

Unless these represent common uses of JACK, the required features have no
role in the API. Currently, these look like corner cases to me.

It it true that I skipped over the proposal for dynamic/on-the-fly backend
switching. This has already been discussed and yes, it would be great to
add it. Torben did this for his "tschak" implementation. Its another
example of something that needs to be done, not discussed.


> As for
> rooms - it is just a side effect of what i propose. JACK api doesn't
> need to be changed; way to select jack instance by client may be same
> as today. I'm not sure even, that you read message up to end -
> including proposed structure.
>

I did read it to the end, which is why I remarked on the port metadata idea
which would make the "rooms" idea much easier to implement and manage
efficiently.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxaudio.org/pipermail/linux-audio-dev/attachments/20120523/105cc340/attachment.html>