[LAD] Proposals for JACK

[J. Liles]

On Tue, May 22, 2012 at 12:08 PM, Paul Davis <paul at linuxaudiosystems.com> wrote:
> I'm sorry but I don't agree with any of these ideas.
>
> One of the guiding design philosophies behind JACK's design has been to
> avoid trying to create an API that covers every possible use case, including
> all the obscure ones. We have seen several examples of this (the most
> notable being SGI's graphics API) which provide the general lesson that
> adding complexity in order to be able to satisfy the least common 10% of use
> cases invariably causes unnecessary complexity for the common 80%.
>
> If you want a "room" like concept then please work on providing per-port
> metadata (I can post a header that describes a proposed API), because I
> believe that this will provide everything necessary to do this without
> JACK's involvement. This is an important addition to the API, and will
> facilitate many things that are useful and moderately common.

I didn't actually understand any of the OP's proposal. But I would
like to chime in and express my support for the idea of per-port
meta-data--it would indeed be very useful.