[ecasound] JACK port naming [patch]

From: Oliver Oli <oliver.oli+0815@email-addr-hidden>
Date: Tue Sep 09 2008 - 11:54:30 EEST

On Tue, Sep 9, 2008 at 12:31 AM, Kai Vehmanen <kvehmanen@email-addr-hidden> wrote:
> Personally, I'm leaning towards to accepting the patch. Ecasound's JACK code
> was developed during very early days of JACK (in 2001-02), and at that time
> it was far from clear how people would end up using the system. Things like
> "jack_alsa" look a bit dated now, and I think "jack_generic" suffers partly
> from the same design rot. I agree that if someone needs to use
> "jack_generic" (versus e.g. "jack"), it is likely she would appreciate
> predictable port numbering as well.

Could we deprecate jack_alsa?

What I'm missing is some combination of jack_auto and jack_generic.
like jack_generic,local_portprefix,remote_client or

And why not give jack and jack_generic the same options, deprecate
jack_generic (but keep it available for some more years) and simplify
everything to:



This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
Ecasound-list mailing list
Received on Tue Sep 9 12:15:01 2008

This archive was generated by hypermail 2.1.8 : Tue Sep 09 2008 - 12:15:02 EEST