Lars Luthman wrote:
> On Mon, 2007-04-23 at 16:22 +0200, Pieter Palmers
wrote:
>> Paul Davis wrote:
>>> I'm about ready to wrap up the v1.0 API by
adding port aliases which i
>>> believe will serve two purposes:
>>>
>>> 1) they are generally useful
>>> 2) they will allow us to migrate away from
the current
>>> backend-specific names in favor of something
more generic, without
>>> breaking any client behaviour
>>>
>>> my only dilemma is the best way to implement
them. i don't want to do a
>>> client/server roundtrip to lookup aliases,
which means they need to live
>>> in shared memory. this suggests (to me) 2
possibilities:
>>>
>>> a) a new shared memory "chunk"
that contains a list of aliases
>>> b) add a fixed number of alias slots to the
existing port structure
>>>
>>> (b) is a bit of a kludge, and limits the
aliases per port BUT at the
>>> same time it avoids more substantive changes to
the overall design in
>>> favor of a bit more memory allocation. and in
reality, the number
>>> of aliases per port is likely to be zero, one
or two at the outside.
>> What are the use cases for #aliases > 2 ?
>>
>> (b) is limited, but simple
>> simple = good.
>>
>> If we fix the max nb of aliases at 8, with a port
name length max = 256
>> (guess) this is 2k/port, giving a 2 meg overhead
for the ports in a 1000
>> port jackd setup. Is that acceptable (my guess is
yes)?
>
> 2 MB for port aliases that hardly ever will be used is
a bit steep.
The danger of course lies in the "hardly ever
used".
>
>> Or lets fix it at 4.
>
> Fix it at 1 or 2. What are the reasons for using them,
other than
> backwards compatibility with backend client ports?
If by 'them' you mean aliases:
I would readily rename all the ports on my system to a more
sensible
name (SynthLeft, SynthRight, Vocal1, ...) in a case where I
have a fixed
setup.
Matching the port names to the channels on the studio mixer,
even if
they are as general as CH1, CH2, CH3, ... makes sense.
They allow LASHed sessions to be loaded on a system with
another
soundcard. If you have an ALSA soundcard, and then switch
over to a
FireWire based one, all your e.g. Ardour sessions have to be
rewired.
I would propose 2 aliases, one fixed to the current name and
one for the
user alias. Which can also be understood as only one alias
of course. If
you change your studio setup, you can equally well change
your port aliases.
Greets,
Pieter
------------------------------------------------------------
-------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and
take
control of your XML. No limits. Just data. Click to get it
now.
http://sourcefor
ge.net/powerbar/db2/
_______________________________________________
Jackit-devel mailing list
Jackit-devel lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jackit-dev
el
|