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

PrevNext  Index
DateThu, 26 Jan 2012 01:23:40 +0200
From Nedko Arnaudov <[hidden] at arnaudov dot name>
ToPaul Davis <[hidden] at linuxaudiosystems dot com>
Cc[hidden] at lists dot jackaudio dot org
Follow-UpPaul Davis Re: [Jack-Devel] jackd1/jackd2: FFADO port name divergence
Paul Davis <[hidden]> writes:

> On Wed, Jan 25, 2012 at 6:11 PM, Nedko Arnaudov <[hidden]> wrote:
>
>>  * present human readable names for hardware ports that user will
>>   identify and connect, either from within an all-in-one app or
>>   external patchbay app. this applies to both parts of full port
>>   names. e.g. something like "emu10k1:rear_L"
>
> ports must have canonical names no matter what the user wants to call them.

IMO: For backward compatibility - yes. For future - see "tags" below.

>>  * present (autoconfigured or manually configured) "tags" that mark
>>   ports with well known semantics. the obvious example here is "default
>>   stereo playback ports (L&R)"
>
> as noted, the metadata API will allow this (and much more).

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.

-- 
Nedko Arnaudov <GnuPG KeyID: 5D1B58ED>
PrevNext  Index

1327533895.20673_0.ltw:2,a <87fwf3pds3.fsf at arnaudov dot name>