Re: [Jack-Devel] colons in port names

On Tue, Jul 26, 2011 at 08:43:56AM -0400, Paul Davis wrote:

>     1) do nothing
>     2) note that its unwise to use colons in the documentation, but nothing more
>     3) enforce a no-colon rule


(3), without reservation.


And while we are at it, I'd like to add the following recommendations:

1. Hierarchical port names should be composed the way Ardour does it,
   using '/' to separate components of the name.

2. Ports which are part of a multichannel group should have names of
   the form

   clientname:groupname.channel

so that one day (dreaming) tools like qjackctl could recognise such
groups, present them as one port (unless the user expands them), and
do the 'right thing' when connecting them which is to connect ports
with the same channel name. This format is already being used by my
Ambisonic tools for example (where a group could easily be 16 or 25
channels - a pain to connect manually). It makes sense even for
stereo: "master/out.L", "master/out.R".

Ciao,

-- 
FA

1311689241.860_0.ltw:2,a <20110726140707.GA17314 at linuxaudio dot org>