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

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.

1327534581.21455_0.ltw:2,a <CAFa_cK=9x1OYme3PgQGLsy1WguTjiRU2j0e3mFo6PDkJ3ELhHg at mail dot gmail dot com>