3 Oct
2002
3 Oct
'02
9:58 p.m.
From: Steve Harris [mailto:S.W.Harris@ecs.soton.ac.uk]
Not that this is a good thing, it should be fixed. I
didn´t
check to see
if there was a client name query function. If so I will use
that, if not I
will probably just move to always using bridge-<pid>. ¿comments?
The only thing I don't like about the <jack-client-name>-<pid> idea is
when
you've got applications (ardour) that try to re-establish previous jack
connections it can't.
I'm not sure that you'd want to do this with the meterbridge but it's
something that needs to be handled if we want to be able to save and restart
a "jack session".
Regards,
Jake.
This e-mail and any attachment is for authorised use by the intended recipient(s) only.
It may contain proprietary material, confidential information and/or be subject to legal
privilege. It should not be copied, disclosed to, retained or used by, any other party.
If you are not an intended recipient then please promptly delete this e-mail and any
attachment and all copies and inform the sender. Thank you.
4 Oct
4 Oct
7:23 a.m.
New subject: [linux-audio-dev] meterbridge 0.0.4
On Fri, Oct 04, 2002 at 09:55:25 +1000, Stoll, Jake wrote:
Well, there should be a standardised switch to jack clients that makes
them use a given jack name, we´ve mentioned this before. I suggest
--jack-name. votes¿
I dont like using pids because it looks messy, maybe jack could provice an
eqivalent to tmpname (or whatever its called), so you could call
jack_unique_name("bridge") and get back "bridge-1" the first time and
"bridge-2" the second for example.
- Steve
that, if not
I
will probably just move to always using bridge-<pid>. ¿comments?
The only thing I don't like about the <jack-client-name>-<pid> idea is
when
you've got applications (ardour) that try to re-establish previous jack
connections it can't.
I'm not sure that you'd want to do this with the meterbridge but it's
something that needs to be handled if we want to be able to save and restart
a "jack session". 
8:27 a.m.
New subject: [linux-audio-dev] meterbridge 0.0.4
On Fri, 4 Oct 2002, Steve Harris wrote:
This might be a good addition. In any case using pids is not optimal.
This is basicly the same problem as with port names. Either we maintain
two sets of names (one for programs, one for the user-interfaces) or
make a compromise and have something that is usable for both. Requiring
users to map the application instances to pids does not fill this
requirement.
Having a basename with a standard way of labelling/iterating instances
is the way to go IMHO. Ecasound does the following now:
--cut--
for(n = 0; n < AUDIO_IO_JACK_MANAGER::instance_limit; n++) {
client_repp = jack_client_new (client_name.c_str());
if (client_repp != 0) break;
client_name = jackname_rep + "_" + kvu_numtostr(n + 2);
}
--cut--
Ie. it tries "ecasound", "ecasound_2", and so on. The exact syntax
doesn't
really matter, just as long as all client apps use the same one.
--
http://www.eca.cx
Audio software for Linux!
I'm not
sure that you'd want to do this with the meterbridge but it's
something that needs to be handled if we want to be able to save and restart
a "jack session".
I dont like using pids because it looks messy, maybe
jack could provice an
eqivalent to tmpname (or whatever its called), so you could call
jack_unique_name("bridge") and get back "bridge-1" the first time
and
"bridge-2" the second for example.
7:47 p.m.
New subject: [linux-audio-dev] meterbridge 0.0.4
On Fri, Oct 04, 2002 at 01:22:47 +0300, Kai Vehmanen wrote:
This might be a good addition. In any case using pids
is not optimal.
This is basicly the same problem as with port names. Either we maintain
two sets of names (one for programs, one for the user-interfaces) or
make a compromise and have something that is usable for both. Requiring
users to map the application instances to pids does not fill this
requirement.
I hadn't thought about having two names. That wouldn;t totaly solve the
borblem though, as youd still want unique, easy to read names for the long
name.
- Steve
11:19 a.m.
New subject: [linux-audio-dev] meterbridge 0.0.4
On 04 Oct 2002 10:21:13 +0100, Steve Harris wrote:
On Fri, Oct 04, 2002 at 09:55:25 +1000, Stoll, Jake
wrote:
Well, there should be a standardised switch to jack clients that makes
them use a given jack name, we´ve mentioned this before. I suggest
--jack-name. votes¿
--jack-name is good.
libjack should be able to add its own commandline options through a
mechanism like gtk_init( argc, &argv );
that, if
not I
will probably just move to always using bridge-<pid>. ¿comments?
The only thing I don't like about the <jack-client-name>-<pid> idea is
when
you've got applications (ardour) that try to re-establish previous jack
connections it can't.
I'm not sure that you'd want to do this with the meterbridge but it's
something that needs to be handled if we want to be able to save and restart
a "jack session".
I dont like using pids because it looks messy, maybe jack could provice an
eqivalent to tmpname (or whatever its called), so you could call
jack_unique_name("bridge") and get back "bridge-1" the first time
and
"bridge-2" the second for example.
- Steve
8021
days inactive
8022
days old
linux-audio-dev@lists.linuxaudio.org
5 comments
4 participants
participants (4)
-
Kai Vehmanen -
Steve Harris -
Stoll, Jake -
torben hohn