29 May
2016
29 May
'16
11:07 a.m.
Hello JACK community,
I’m planning my new audio editing setup (both hard- and software) and before investing in
hardware, I’d like to ask for advice.
Here’s what I want to do:
– Both computers run Linux.
– On Computer A, I can browse the web and see Youtube videos, I can listen to MP3 files
with Totem and I can do DAW stuff with Ardour.
– Computer B does nothing more than getting all the sound output from A and feed it to the
speaker through it’s soundcard.
Here’s my theoretical approach:
– Both computers run JACK.
– A runs PulseAudio in top of JACK.
– A runs with the net backend using netJACK2.
– B has the Net Manager loaded which gets the audio from A and pipes it to the soundcard.
– Every time I boot the two computers, they are ready to work. No daemons I have to launch
manually, etc. I want the configuration to be done one time for all.
I got my understanding of JACK through the network from here:
https://github.com/jackaudio/jackaudio.github.com/wiki/WalkThrough_User_Net… And this
site would also be my guide for setting up the thing.
But I’m not a JACK expert at all. It’s the first time I’m doing something like this. So I
want to make shure I got the basics right. And, maybe you now even a better step-by-step
tutorial which does exactly what I want.
So, I appreciate any comments on this.
Bye,
xan
4 Jun
4 Jun
3:25 a.m.
El 29/05/16 a les 18:07, xan ha escrit:
Hello JACK community,
I’m planning my new audio editing setup (both hard- and software) and before investing in
hardware, I’d like to ask for advice.
Here’s what I want to do:
– Both computers run Linux.
– On Computer A, I can browse the web and see Youtube videos, I can listen to MP3 files
with Totem and I can do DAW stuff with Ardour.
– Computer B does nothing more than getting all the sound output from A and feed it to
the speaker through it’s soundcard.
Here’s my theoretical approach:
– Both computers run JACK.
– A runs PulseAudio in top of JACK.
– A runs with the net backend using netJACK2.
– B has the Net Manager loaded which gets the audio from A and pipes it to the
soundcard.
– Every time I boot the two computers, they are ready to work. No daemons I have to
launch manually, etc. I want the configuration to be done one time for all.
I got my understanding of JACK through the network from here:
https://github.com/jackaudio/jackaudio.github.com/wiki/WalkThrough_User_Net… And this
site would also be my guide for setting up the thing.
But I’m not a JACK expert at all. It’s the first time I’m doing something like this. So I
want to make shure I got the basics right. And, maybe you now even a better step-by-step
tutorial which does exactly what I want.
So, I appreciate any comments on this.
Looks okay to me; this is the approach I'd take as well.
Some things to note:
- If computer A and computer B are connected by something other than
cable, you might want to use NetJack1 (netone) instead of NetJack2. The
latter is still pretty fragile to connections with packet loss or
jitter, AFAIK.
- NetJack1/2 don't propagate latency, so you'll theoretically
experience some A/V delay when watching videos, for example. In
practice, the difference is small enough that I've never knew it was there.
My five cents.
Xavi
Bye,
xan
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
10 Jul
10 Jul
9:09 a.m.
First of all, thanks, Xavier, for your comments.
I now got the hardware and I tried to set it up following this:
https://github.com/jackaudio/jackaudio.github.com/wiki/WalkThrough_User_Net…
Short story: It doesn’t work.
Long story: When I rung the 'jack_netsource' command, I start to get
resync-messages (see log at the end of the message). On both machines, nothing shows up in
the qjackctl-patchbay so I don’t know where to route my sound from machine A to B. I’ve no
sound so far on B.
I’d appreciate your help with this!
xan.
jackd -R -d net
jackd 0.124.2
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
no message buffer overruns
JACK compiled with System V SHM support.
loading driver ..
creating net driver ... net_pcm|48000|1024|3000|2|2|transport_sync:1
AutoConfig Override !!!
MTU is set to 1400 bytes
netjack: period : up: 1024 / dn: 1024
netjack: framerate: 48000
netjack: audio : cap: 2 / pbk: 2)
netjack: midi : cap: 1 / pbk: 1)
netjack: buffsize : rx: 12344)
netxruns amount: 21ms
netxruns amount: 21ms
resync after freerun... 89
netxruns amount: 2133ms
netxruns amount: 21ms
resync after freerun... 178
netxruns amount: 2133ms
netxruns amount: 21ms
resync after freerun... 267
netxruns amount: 2133ms
netxruns amount: 21ms
resync after freerun... 356
netxruns amount: 2133ms
netxruns amount: 21ms
resync after freerun... 446
netxruns amount: 2133ms
netxruns amount: 21ms
…
…
Am 04.06.2016 um 10:25 schrieb Xavier Mendez:
El 29/05/16 a les 18:07, xan ha escrit:
Hello JACK community,
I’m planning my new audio editing setup (both hard- and software) and before investing in
hardware, I’d like to ask for advice.
Here’s what I want to do:
– Both computers run Linux.
– On Computer A, I can browse the web and see Youtube videos, I can listen to MP3 files
with Totem and I can do DAW stuff with Ardour.
– Computer B does nothing more than getting all the sound output from A and feed it to
the speaker through it’s soundcard.
Here’s my theoretical approach:
– Both computers run JACK.
– A runs PulseAudio in top of JACK.
– A runs with the net backend using netJACK2.
– B has the Net Manager loaded which gets the audio from A and pipes it to the
soundcard.
– Every time I boot the two computers, they are ready to work. No daemons I have to
launch manually, etc. I want the configuration to be done one time for all.
I got my understanding of JACK through the network from here:
https://github.com/jackaudio/jackaudio.github.com/wiki/WalkThrough_User_Net… And this
site would also be my guide for setting up the thing.
But I’m not a JACK expert at all. It’s the first time I’m doing something like this. So I
want to make shure I got the basics right. And, maybe you now even a better step-by-step
tutorial which does exactly what I want.
So, I appreciate any comments on this.
Looks okay to me; this is the approach I'd take as well.
Some things to note:
- If computer A and computer B are connected by something other than cable, you might
want to use NetJack1 (netone) instead of NetJack2. The latter is still pretty fragile to
connections with packet loss or jitter, AFAIK.
- NetJack1/2 don't propagate latency, so you'll theoretically experience some
A/V delay when watching videos, for example. In practice, the difference is small enough
that I've never knew it was there.
My five cents.
Xavi
Bye,
xan
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org 
9:25 a.m.
This is a slightly odd approach in some way. Computer B basically has
nothing to do. All the hard work happens on A, and if the machine is
overloaded, the sound will still be affected. Normally, you'd use this sort
of design to spread the "load" around, but what you're proposing isn't
really spreading any load at all. Any time A is overloaded, it makes no
difference that B is running fine - the sound will still glitch.
On Sun, May 29, 2016 at 12:07 PM, xan <xan(a)0l3.de> wrote:
Hello JACK community,
I’m planning my new audio editing setup (both hard- and software) and
before investing in hardware, I’d like to ask for advice.
Here’s what I want to do:
– Both computers run Linux.
– On Computer A, I can browse the web and see Youtube videos, I can listen
to MP3 files with Totem and I can do DAW stuff with Ardour.
– Computer B does nothing more than getting all the sound output from A
and feed it to the speaker through it’s soundcard.
Here’s my theoretical approach:
– Both computers run JACK.
– A runs PulseAudio in top of JACK.
– A runs with the net backend using netJACK2.
– B has the Net Manager loaded which gets the audio from A and pipes it to
the soundcard.
– Every time I boot the two computers, they are ready to work. No daemons
I have to launch manually, etc. I want the configuration to be done one
time for all.
I got my understanding of JACK through the network from here:
https://github.com/jackaudio/jackaudio.github.com/wiki/WalkThrough_User_Net…
And this site would also be my guide for setting up the thing.
But I’m not a JACK expert at all. It’s the first time I’m doing something
like this. So I want to make shure I got the basics right. And, maybe you
now even a better step-by-step tutorial which does exactly what I want.
So, I appreciate any comments on this.
Bye,
xan
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
9:39 a.m.
The reason I’m doing this is that I don’t want my loud working machine A in my studio. It
sits somewhere else and in my studio I only have the fanless thinclient B. Is there a
better way to do this?
Am 10.07.2016 um 16:25 schrieb Paul Davis:
This is a slightly odd approach in some way. Computer
B basically has nothing to do. All the hard work happens on A, and if the machine is
overloaded, the sound will still be affected. Normally, you'd use this sort of design
to spread the "load" around, but what you're proposing isn't really
spreading any load at all. Any time A is overloaded, it makes no difference that B is
running fine - the sound will still glitch.
On Sun, May 29, 2016 at 12:07 PM, xan <xan(a)0l3.de <mailto:xan@0l3.de>>
wrote:
Hello JACK community,
I’m planning my new audio editing setup (both hard- and software) and before
investing in hardware, I’d like to ask for advice.
Here’s what I want to do:
– Both computers run Linux.
– On Computer A, I can browse the web and see Youtube videos, I can listen to MP3
files with Totem and I can do DAW stuff with Ardour.
– Computer B does nothing more than getting all the sound output from A and feed it
to the speaker through it’s soundcard.
Here’s my theoretical approach:
– Both computers run JACK.
– A runs PulseAudio in top of JACK.
– A runs with the net backend using netJACK2.
– B has the Net Manager loaded which gets the audio from A and pipes it to the
soundcard.
– Every time I boot the two computers, they are ready to work. No daemons I have to
launch manually, etc. I want the configuration to be done one time for all.
I got my understanding of JACK through the network from here:
https://github.com/jackaudio/jackaudio.github.com/wiki/WalkThrough_User_Net… And this
site would also be my guide for setting up the thing.
But I’m not a JACK expert at all. It’s the first time I’m doing something like this.
So I want to make shure I got the basics right. And, maybe you now even a better
step-by-step tutorial which does exactly what I want.
So, I appreciate any comments on this.
Bye,
xan
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org <mailto:Jack-Devel@lists.jackaudio.org>
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
9:44 a.m.
why not just run cables? what is computer B doing? basically nothing ...
On Sun, Jul 10, 2016 at 10:39 AM, xan <xan(a)0l3.de> wrote:
The reason I’m doing this is that I don’t want my loud
working machine A
in my studio. It sits somewhere else and in my studio I only have the
fanless thinclient B. Is there a better way to do this?
Am 10.07.2016 um 16:25 schrieb Paul Davis:
This is a slightly odd approach in some way. Computer B basically has
nothing to do. All the hard work happens on A, and if the machine is
overloaded, the sound will still be affected. Normally, you'd use this sort
of design to spread the "load" around, but what you're proposing isn't
really spreading any load at all. Any time A is overloaded, it makes no
difference that B is running fine - the sound will still glitch.
On Sun, May 29, 2016 at 12:07 PM, xan <xan(a)0l3.de> wrote:
Hello JACK community,
I’m planning my new audio editing setup (both hard- and software) and
before investing in hardware, I’d like to ask for advice.
Here’s what I want to do:
– Both computers run Linux.
– On Computer A, I can browse the web and see Youtube videos, I can
listen to MP3 files with Totem and I can do DAW stuff with Ardour.
– Computer B does nothing more than getting all the sound output from A
and feed it to the speaker through it’s soundcard.
Here’s my theoretical approach:
– Both computers run JACK.
– A runs PulseAudio in top of JACK.
– A runs with the net backend using netJACK2.
– B has the Net Manager loaded which gets the audio from A and pipes it
to the soundcard.
– Every time I boot the two computers, they are ready to work. No daemons
I have to launch manually, etc. I want the configuration to be done one
time for all.
I got my understanding of JACK through the network from here:
https://github.com/jackaudio/jackaudio.github.com/wiki/WalkThrough_User_Net…
And this site would also be my guide for setting up the thing.
But I’m not a JACK expert at all. It’s the first time I’m doing something
like this. So I want to make shure I got the basics right. And, maybe you
now even a better step-by-step tutorial which does exactly what I want.
So, I appreciate any comments on this.
Bye,
xan
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
10:36 a.m.
A cable would be just fine if both computers where not so far away. Believe me, it would
be a lot easier for me, too.
On 10.07.2016 16:44, Paul Davis wrote:
why not just run cables? what is computer B doing?
basically nothing ...
On Sun, Jul 10, 2016 at 10:39 AM, xan <xan(a)0l3.de <mailto:xan@0l3.de>>
wrote:
The reason I’m doing this is that I don’t want my loud working machine A in my
studio. It sits somewhere else and in my studio I only have the fanless thinclient B. Is
there a better way to do this?
Am 10.07.2016 um 16:25 schrieb Paul Davis:
This is a slightly odd approach in some way.
Computer B basically has nothing to do. All the hard work happens on A, and if the machine
is overloaded, the sound will still be affected. Normally, you'd use this sort of
design to spread the "load" around, but what you're proposing isn't
really spreading any load at all. Any time A is overloaded, it makes no difference that B
is running fine - the sound will still glitch.
On Sun, May 29, 2016 at 12:07 PM, xan <xan(a)0l3.de <mailto:xan@0l3.de>>
wrote:
Hello JACK community,
I’m planning my new audio editing setup (both hard- and software) and before
investing in hardware, I’d like to ask for advice.
Here’s what I want to do:
– Both computers run Linux.
– On Computer A, I can browse the web and see Youtube videos, I can listen to MP3
files with Totem and I can do DAW stuff with Ardour.
– Computer B does nothing more than getting all the sound output from A and feed
it to the speaker through it’s soundcard.
Here’s my theoretical approach:
– Both computers run JACK.
– A runs PulseAudio in top of JACK.
– A runs with the net backend using netJACK2.
– B has the Net Manager loaded which gets the audio from A and pipes it to the
soundcard.
– Every time I boot the two computers, they are ready to work. No daemons I have
to launch manually, etc. I want the configuration to be done one time for all.
I got my understanding of JACK through the network from here:
https://github.com/jackaudio/jackaudio.github.com/wiki/WalkThrough_User_Net… And this
site would also be my guide for setting up the thing.
But I’m not a JACK expert at all. It’s the first time I’m doing something like
this. So I want to make shure I got the basics right. And, maybe you now even a better
step-by-step tutorial which does exactly what I want.
So, I appreciate any comments on this.
Bye,
xan
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org <mailto:Jack-Devel@lists.jackaudio.org>
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org <mailto:Jack-Devel@lists.jackaudio.org>
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
11:54 a.m.
On Sun, Jul 10, 2016 at 05:36:23PM +0200, xan wrote:
A cable would be just fine if both computers where not
so
far away. Believe me, it would be a lot easier for me, too.
What is 'far' ?
Anyway, you could just run zita-j2n on A and zita-n2j on B
(or use the versions that come with jack1). Having things
set up when you log in is just a matter of writing two
scripts.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
11 Jul
11 Jul
8:17 a.m.
Thanks for pointing me to zita, Fons. I’d like to give it a go but I’m
not shure how. Just run the command and the rest happens automatically?
Where is zita documented? I couldn’t find a lot.
Am 10.07.2016 um 18:54 schrieb Fons Adriaensen:
What is 'far' ?
There’s walls inbetween I can’t fiddle with. That’s far enough.
xan.
14 Jul
14 Jul
8:32 a.m.
Hi Xan,
my two cents here too.
in a similar setup zita* stuff has not worked great for me - I got alot of
noise , so I switched to using the more primitive alsa_in and alsa_out.
just keep in mind you may find more suitable as well.
you may also find useful the "jcmess" - a cli tool to automate
loading/saving jack connections (as these appear on qjackctl). you can find
it on github
https://github.com/synthnassizer/jcmess
Hope this helps!
On Mon, Jul 11, 2016 at 4:17 PM, xan <xan(a)0l3.de> wrote:
Thanks for pointing me to zita, Fons. I’d like to give
it a go but I’m
not shure how. Just run the command and the rest happens automatically?
Where is zita documented? I couldn’t find a lot.
Am 10.07.2016 um 18:54 schrieb Fons Adriaensen:
What is 'far' ?
There’s walls inbetween I can’t fiddle with. That’s far enough.
xan.
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
12:51 p.m.
On Mon, Jul 11, 2016 at 03:17:05PM +0200, xan wrote:
Thanks for pointing me to zita, Fons. I’d like to give
it a go but I’m
not shure how. Just run the command and the rest happens automatically?
Where is zita documented? I couldn’t find a lot.
Both programs have man pages, and also will display the
command syntax if run without arguments or with --help.
If you have any problems with zita-*2* just let me know.
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
12:53 p.m.
On Thu, Jul 14, 2016 at 04:32:29PM +0300, Athanasios Silis wrote:
in a similar setup zita* stuff has not worked great
for me - I got alot of
noise , so I switched to using the more primitive alsa_in and alsa_out.
There a many ways a link using zita-*2* can go wrong, depending on
network performance and if your Jack systems by themselves are OK
or not. But 'noise' is not one of the possible results.
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
19 Jul
19 Jul
12:13 a.m.
Hi Fons,
i'm not implying there was something wrong with zita-*2*, i'm sure in fact
it is some network issue that caused the jitter from the speakers, it was
nonetheless a jitter.
Now where zita-*2* offered jitter ,alsa_* did not , provided the same
arguments where used (ie for low latency).
I am sure had I spend more time on it I would have found a solution - i do
not question zita-* is "future" while alsa_* is "obsolete", but for
the
given transition to zita-* , I had to revert to alsa_*
On Thu, Jul 14, 2016 at 8:53 PM, Fons Adriaensen <fons(a)linuxaudio.org>
wrote:
On Thu, Jul 14, 2016 at 04:32:29PM +0300, Athanasios
Silis wrote:
in a similar setup zita* stuff has not worked
great for me - I got alot
of
noise , so I switched to using the more primitive
alsa_in and alsa_out.
There a many ways a link using zita-*2* can go wrong, depending on
network performance and if your Jack systems by themselves are OK
or not. But 'noise' is not one of the possible results.
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
15 Aug
15 Aug
1:11 p.m.
Hi,
after some weeks of silence, I got back to this issue. I installed zita-njbridge on both
my machines, started the JACK server and tried to run the commands.
'zita-j2n b`s-ip port' is running on A and 'zita-n2j a`s-ip port' is
running on B.
However, I don`t know the port I`m supposed to use and I couldn` find out.
The command seems to run on A but fails on B: "Failed to connect to socket. Cannot
assign request address."
I`d appreciate some debugging here.
Thanks in advance,
xan.
Am 19.07.2016 um 07:13 schrieb Athanasios Silis:
Hi Fons,
i'm not implying there was something wrong with zita-*2*, i'm sure in fact it is
some network issue that caused the jitter from the speakers, it was nonetheless a jitter.
Now where zita-*2* offered jitter ,alsa_* did not , provided the same arguments where
used (ie for low latency).
I am sure had I spend more time on it I would have found a solution - i do not question
zita-* is "future" while alsa_* is "obsolete", but for the given
transition to zita-* , I had to revert to alsa_*
On Thu, Jul 14, 2016 at 8:53 PM, Fons Adriaensen <fons(a)linuxaudio.org
<mailto:fons@linuxaudio.org>> wrote:
On Thu, Jul 14, 2016 at 04:32:29PM +0300, Athanasios Silis wrote:
in a similar setup zita* stuff has not worked
great for me - I got alot of
noise , so I switched to using the more primitive alsa_in and alsa_out.
There a many ways a link using zita-*2* can go wrong, depending on
network performance and if your Jack systems by themselves are OK
or not. But 'noise' is not one of the possible results.
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org <mailto:Jack-Devel@lists.jackaudio.org>
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org 
3:12 p.m.
On 08/15/16 14:11, xan wrote:
Hi,
after some weeks of silence, I got back to this issue. I installed zita-njbridge on both
my machines, started the JACK server and tried to run the commands.
'zita-j2n b`s-ip port' is running on A and 'zita-n2j a`s-ip port' is
running on B.
However, I don`t know the port I`m supposed to use and I couldn` find out.
The command seems to run on A but fails on B: "Failed to connect to socket. Cannot
assign request address."
I`d appreciate some debugging here.
Thanks in advance,
xan.
Am 19.07.2016 um 07:13 schrieb Athanasios Silis:
b should also have b's ip. i use ports in the 46xx range - not sure
why. it works.
--
www.the-temp-agency.com/lollipop-factory
Hi Fons,
i'm not implying there was something wrong with zita-*2*, i'm sure in fact it is
some network issue that caused the jitter from the speakers, it was nonetheless a jitter.
Now where zita-*2* offered jitter ,alsa_* did not , provided the same arguments where
used (ie for low latency).
I am sure had I spend more time on it I would have found a solution - i do not question
zita-* is "future" while alsa_* is "obsolete", but for the given
transition to zita-* , I had to revert to alsa_*
On Thu, Jul 14, 2016 at 8:53 PM, Fons Adriaensen <fons(a)linuxaudio.org
<mailto:fons@linuxaudio.org>> wrote:
On Thu, Jul 14, 2016 at 04:32:29PM +0300, Athanasios Silis wrote:
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org in a similar setup zita* stuff has not worked
great for me - I got alot of
noise , so I switched to using the more primitive alsa_in and alsa_out.
There a many ways a link using zita-*2* can go wrong, depending on
network performance and if your Jack systems by themselves are OK
or not. But 'noise' is not one of the possible results.
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org <mailto:Jack-Devel@lists.jackaudio.org>
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
3:50 p.m.
On Mon, Aug 15, 2016 at 08:11:06PM +0200, xan wrote:
after some weeks of silence, I got back to this issue.
I installed zita-njbridge on both my machines, started the JACK server and tried to run
the commands.
'zita-j2n b`s-ip port' is running on A and 'zita-n2j a`s-ip port' is
running on B.
However, I don`t know the port I`m supposed to use and I couldn` find out.
The command seems to run on A but fails on B: "Failed to connect to socket. Cannot
assign request address."
I`d appreciate some debugging here.
Read the man page. The IP address for both j2n and n2j is that of
the destination. For the port you can use any value > 1000 that is
not in use, try e.g. 7000.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
16 Aug
16 Aug
8:14 a.m.
Am 15.08.2016 um 22:50 schrieb Fons Adriaensen:
Read the man page. The IP address for both j2n and n2j
is that of
the destination. For the port you can use any value > 1000 that is
not in use, try e.g. 7000.
I couldn`t find anything specific about ports in the man page, but I`m now using port
7000. Thanks for pointing me to it.
The command runs without any output on the sender and the recevier sees the incoming
packages and says: "Syncing... Recieving". However, the sound I`m playing on the
sender end is not played back on the recievers end. Do I have to do some routing in
something like qjackctl? I tried this and that but couldn`t get it running. Is there a
detailed step-by-step tutorial somewhere or can you help me please?
Thanks,
xan.
1:35 p.m.
On Tue, Aug 16, 2016 at 03:14:13PM +0200, xan wrote:
Am 15.08.2016 um 22:50 schrieb Fons Adriaensen:
What do you mean by 'playing on the sender' ? I assume you are using
something that outputs via Jack. Then you have to connect it to j2n.
Read the man page. The IP address for both j2n
and n2j is that of
the destination. For the port you can use any value > 1000 that is
not in use, try e.g. 7000.
I couldn`t find anything specific about ports in the man page,
but I`m now using port 7000. Thanks for pointing me to it.
The command runs without any output on the sender and the recevier
sees the incoming packages and says: "Syncing... Recieving". However,
the sound I`m playing on the sender end is not played back on the
recievers end. Do I have to do some routing in something like
qjackctl?
And on the receiving end you need to connect n2j, e.g. to the
soundcard.
I tried this and that but couldn`t get it running. Is
there
a detailed step-by-step tutorial somewhere or can you help
me please?
Do you mean you can't run qjackctl ? If not what happens if
you try running it ? How do you start Jack ? You really need
to provide more info if you want anyone to help... Without
that it's not possible.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
19 Aug
19 Aug
5:58 a.m.
Am 16.08.2016 um 20:35 schrieb Fons Adriaensen:
What do you mean by 'playing on the sender' ?
I assume you are using
something that outputs via Jack. Then you have to connect it to j2n.
And on the receiving end you need to connect n2j, e.g.
to the
soundcard.
I know, this seems so clear to you, but to me it wasn`t so clear. And I couldn`t find this
documented somewhere. But thanks to your comment, I think I`ve done it right.
So for the record, here`s what I did:
– start Jack on both machines using qjackctl
– run 'zita-j2n ip-of-the-reciever 7000' in a terminal on the sender
– run 'zita-n2j ip-of-the-reciever 7000' in a terminal on the reciever
– bring up qjackctl`s connections window on both machines
I want to send Ardour`s output over the network so:
– on the sender, left side of the connections window, flip ardour open and on the right
side, flip zita-j2n open; drag and drop ardour`s Master/audio_out 1 onto zita-j2n`s in_1;
do the same for Master/audio_out 2 and in_2; now, a line is connecting these two channels
– on the reciever, left side of the connection window flip zita-n2j open and on the right
side, flip system open; connect zita-n2j`s out_1 to system`s playback_1; do the same for
out_2 and playback_2
So far, so good. It worked. I get sound through the reciever`s headphones, but it`s very
very bad quality, something like an ultra low bitrate. What I suspect is happening is, a
lot of packets get lost and are replaced with silence (zita-nj does this, right?). I
originally tried it with using wifi connection although I know it`s not supported. Because
of that, I tried it using an ethernet cable. I can`t hear any difference. How can I debug
this and possibly make the connection better?
Do you mean you can't run qjackctl ?
I`m
sorry, that was a misunderstanding. I can run qjackctl.
I appreciate all your help and I`m sorry if my writing is confusing to you.
xan.
20 Aug
20 Aug
5:47 a.m.
On Fri, Aug 19, 2016 at 12:57:53PM +0200, xan wrote:
I know, this seems so clear to you, but to me it
wasn`t so
clear. And I couldn`t find this documented somewhere. But
thanks to your comment, I think I`ve done it right.
Since you're using Jack I assume you know the basics...
which include that you have to connect things (which
can be automated of course).
So for the record, here`s what I did:
– start Jack on both machines using qjackctl
– run 'zita-j2n ip-of-the-reciever 7000' in a terminal on the sender
– run 'zita-n2j ip-of-the-reciever 7000' in a terminal on the reciever
– bring up qjackctl`s connections window on both machines
I want to send Ardour`s output over the network so:
– on the sender, left side of the connections window,
flip ardour open and on the right side, flip zita-j2n open;
drag and drop ardour`s Master/audio_out 1 onto zita-j2n`s in_1;
do the same for Master/audio_out 2 and in_2; now, a line is
connecting these two channels
OK, you could also make the connection in Ardour.
– on the reciever, left side of the connection window
flip
zita-n2j open and on the right side, flip system open; connect
zita-n2j`s out_1 to system`s playback_1; do the same for out_2
and playback_2
OK.
So far, so good. It worked. I get sound through the
reciever`s headphones,
but it`s very very bad quality, something like an ultra low bitrate. What
I suspect is happening is, a lot of packets get lost and are replaced with
silence (zita-nj does this, right?).
Yes. You could try --buff 100 on the receiver. This will provide 100 ms
of extra buffering.
I originally tried it with using wifi connection
although I know it`s not
supported. Because of that, I tried it using an ethernet cable. I can`t
hear any difference. How can I debug this and possibly make the connection better?
Hmm, did you just connect the ethernet cable and then use the same IP
addresses ? In that case you're still using the Wifi...
Are you using Jack in real-time mode (this is absolutely essential) ?
Check the top line of qjackctl's display, it should show 'RT' in
the top line (just left of the % CPU indication).
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
2813
days inactive
2896
days old
jackaudio@lists.linuxaudio.org
19 comments
6 participants
participants (6)
-
Athanasios Silis -
Fons Adriaensen -
Paul Davis -
Tweed -
xan -
Xavier Mendez