Re: [Jack-Devel] jackd1/jackd2: FFADO port name divergence

PrevNext  Index
DateWed, 25 Jan 2012 23:43:14 +0000
From Fons Adriaensen <[hidden] at linuxaudio dot org>
To[hidden] at lists dot jackaudio dot org
In-Reply-ToPaul Davis Re: [Jack-Devel] jackd1/jackd2: FFADO port name divergence
Follow-UpPaul Davis Re: [Jack-Devel] jackd1/jackd2: FFADO port name divergence
On Wed, Jan 25, 2012 at 06:36:06PM -0500, Paul Davis wrote:
> On Wed, Jan 25, 2012 at 6:23 PM, Nedko Arnaudov <[hidden]> wrote:
> 
> > Time will tell if the metadata api is the proper way. ATM in ladish I'm
> > using well known guids that I encode in room port names, but this is
> > only one of the other possible ways.
> 
> useful/pretty/semantic names need to be accessible to any JACK client
> that wants to find stuff or display stuff. thus they need to have
> well-defined URIs that are not the domain of a single application.
> 
> when a user makes a port into "monitors/L", they presumably want all
> apps to be able to show that as "monitors/L" even if the canonical
> name continues to exist.

The really simple way to achieve that is to name the port 'monitors/L'
and forget about all other names, aliases or whatever.

And yes that would make e.g. an Ardour session fail when it expects
'monitor/[LR]' and those ports don't exist. It fails becaus it should
fail, it does so in a safe way, and it's easy to fix.

Ciao,

-- 
FA

Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl.
PrevNext  Index

1327535002.21740_0.ltw:2,a <20120125234313.GB30274 at linuxaudio dot org>