Re: [ecasound] JACK port naming

On Sunday 07 September 2008 10:40:16 Julien Claassen wrote:
> Not to my knowledge. But is it so important? If you create the
> chain-setup, you'll always know which port is which. If youneed this for
> evil scripting, you could still determine the port-numbers in your
> script. A bit more evil still, yet possible.

What's so evil about scripting? ;)

Actually, in this case I'm using Qjackctl's patchbay to auto-connect the
ports. Qjackctl allows the use of wildcards for port names, but as far as I
can tell there's no way to match *two* adjacent ports with a common prefix.

Is there any particular reason not to start counting at 1 for each prefix?
I could make a patch if there's consensus that this should be changed.

Dominic

-------------------------------------------------------------------------
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
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Ecasound-list mailing list
Ecasound-list@email-addr-hidden
https://lists.sourceforge.net/lists/listinfo/ecasound-list
Received on Sun Sep 7 16:15:02 2008