<br><br><div class="gmail_quote">On Wed, May 30, 2012 at 12:18 AM, Marcel Bonnet <span dir="ltr"><<a href="mailto:marcelbonnet@gmail.com" target="_blank">marcelbonnet@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Hi, <br>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?<br>
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.<br>
</blockquote><div><br>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).<br>
<br>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).<br><br><br></div></div>