Re: [Jack-Devel] mismatch between Mageia 2 (1.9.8) and TinyCore (1.9.7)

Yes, when I said "client", I meant the thin client machine that
has a soundcard--the JACK master if I understand JACK terminology
correctly.  When I said "server", I meant the compute server that
runs Firefox, MuseScore, MPlayer, etc.--the JACK slave if I
understand correctly.  Audio is passed between the two via
NetJACK2, if I understand that terminology correctly.

Running the exact same build of JACK on both sides would be the
ideal.  However, sometimes reality dictates that the two sides
are different distributions, and the exact same build is not
always available between distributions.  In this case, Mageia 2
on the JACK slave comes with 1.9.8 and TinyCore on the JACK
master comes with 1.9.7.

Based on the tone of the replies, I would guess there is no
compatibility mode or option or bridge between the 1.9.7 and
1.9.8 protocols.  Or is there?

The combination of 1.9.6 on the JACK slave (applications that
generate sound data) and 1.9.7 on the JACK master (soundcard)
worked when the slave was Mageia 1.  However, now with the 1.9.6
packages from Mageia 1 installed on Mageia 2, jack_lsp on the
JACK slave says "Cannot open lsp client" and "jack_client_open()
failed, status = 0x21".  The jackd process is running, and its
output doesn't have any apparent indication it isn't healthy and
happy.  Any suggestions to get slave jack_lsp and jack_connect
back on speaking terms with slave jackd?

Also, is the issue of "500 Internal Server Error" on the Wiki and
bugs pages being worked on?

Thanks again,

Robert Riches


> Message: 5
> Date: Tue, 18 Dec 2012 15:08:26 -0600
> From: "Chris Caudle" <[hidden]>
> To: "JACK" <[hidden]>
> Subject: Re: [Jack-Devel] mismatch between Mageia 2 (1.9.8) and
> 	TinyCore (1.9.7)
> Message-ID:
> 	<[hidden]>
> Content-Type: text/plain;charset=iso-8859-1
>
> > On Tue, Dec 18, 2012 at 2:50 PM, Robert M. Riches Jr. <
> > [hidden]> wrote:
> >> With server running 1.9.8 and clients running 1.9.7,
>
> On Tue, December 18, 2012 2:13 pm, Paul Davis wrote:
> > You can NEVER run JACK this way.
>
> The original email was talking about thin clients, so I think in Jack
> terminology it would be a machine running JACK 1.9.8 as slave and a second
> machine running JACK 1.9.7 as master with a NetJACK-2 connection between
> them.
>
> Assumptions:
> "client" refers to thin client, or what would be the X server, so would be
> the JACK master since it is physically closest to the user.
>
> "Server" refers to compute server, remote from the user, so would be
> running JACK slave to connect applications on the remote machine to the
> display and sound card on the client machine.
>
> I think your objection was assuming that JACK server and JACK client meant
> jackd and an application linked to jack running on the same machine, which
> I think is not what the original author meant.
>
> -- 
> Chris Caudle

1355874375.24050_0.ltw:2,a <20121218234606.A0EFD1835EA at one dot localnet>