linuxaudio.org

--20cf3074b37e91061e04c13d8514

Content-Type: text/plain; charset=ISO-8859-1
On Wed, May 30, 2012 at 12:18 AM, Marcel Bonnet wrote:
> Hi,

quoted text
> Does anyone knows if there is a reason, except for the concern of a unique

> name per client, for jack clients to use the PID as suffix for the client

> name instead of simply allows the user to name it through the command line?

> As mentioned in [1], if we use, per example, qjackctl as front end for

> jackd and save the session, the next day you cannot load the same

> connections because the PIDs had changed. I think it would be better if we

> could name the clients ourselves.

>

JACK does not create such names. This is an issue with specific clients

that choose to use this naming convention, rather than with JACK itself.

Clients should rely on jack_client_open() to generate a unique name if the

name they request is already taken, and should not try to generate a unique

name for themselves (unless the user provides the unique name, which is

entirely different).
Note that if you do, in fact, run the same client multiple times, then

there will always be issues with defining the connections (not necessarily

that significant though).
--20cf3074b37e91061e04c13d8514

Content-Type: text/html; charset=ISO-8859-1

Content-Transfer-Encoding: quoted-printable
On Wed, May 30, 2012 at 12:18 AM, Marcel=

 Bonnet <marcelbonnet@gmail.com> wrote:

Hi, Does anyone knows if there is a reason, except for the concern of a=

 unique name per client, for jack clients to use the PID as suffix for the =

client name instead of simply allows the user to name it through the comman=

d line?
As mentioned in [1], if we use, per example, qjackctl as front end for jack=

d and save the session, the next day you cannot load the same connections b=

ecause the PIDs had changed. I think it would be better if we could name th=

e clients ourselves.

JACK does not create such names. This is an issue wit=

h specific clients that choose to use this naming convention, rather than w=

ith JACK itself. Clients should rely on jack_client_open() to generate a un=

ique name if the name they request is already taken, and should not try to =

generate a unique name for themselves (unless the user provides the unique =

name, which is entirely different).

Note that if you do, in fact, run the same client multiple times, then =

there will always be issues with defining the connections (not necessarily =

that significant though).
--20cf3074b37e91061e04c13d8514--