[LAU] Bitwig: what we can learn from it

[Fons Adriaensen]

On Sat, Mar 29, 2014 at 09:11:23AM -0700, Len Ovens wrote:
> 
> On Sat, 29 Mar 2014, Alexandre Prokoudine wrote:
> 
> >3) After >10 years I'm still uncertain if I can permanently rename I/O
> >for a device in JACK, but I'm sure as hell there is no simple UI for
> >that. Bitwig fixes that at the "first run configuration" step: I can
> >create virtual inputs/outputs from physical ones and give them
> >sensible names.
> 
> This should I think be a part of jack. I have a delta 66 which means
> capture 1 to 4 are analog in, capture 9 and 10 are spdif in (analog
> 5 and 6 for me) and capture 11 and 12 are monitor mixer in. Capture
> 5 to 8 are not usable and it would be nice to not show them at all,
> but it would be nice to at least label them "NA" or "not in use" or
> something. Playback has similar issues though I can at least use all
> the playbacks as inputs to the monitor mixer... if I actually made
> use of it :)  But labeling (which affects ordering in displays BTW)
> would be really nice. I could make a fake device with 6 inputs and 6
> outputs which would be next best...

With latest Jack1 you can add any metadata to a port. Of course 
then the connection GUIs such as qjackctl should support it...

Apart from that it would indeed be handy if the port names for a
device could be defined somewhere, e.g. in a .jackrc file. Can't
be that difficult...

Ciao,

-- 
FA

A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)