On Mon, 20 Sep 2010 19:58:16 +0200 (CEST)
Julien Claassen <julien(a)c-lab.de> wrote:
Hello David!
That is helpful. Yet how to start the jack_netsource or how to try
the connection. The netmanager says:
Listening on '225.3.19.154:19000'
It is my understanding that jack_netsource isn't used in a jack2 setup.
Regarding addressing, according to the docs [1]
If you need, for particulary[sic] reasons to set another Multicast
address or UDP Port, you can use :
jack_load netmanager -i "-a xxx.xxx.xxx.xxx -p port"
... and on the client, use the same address and port with the
-a and -p parameters
jackd -dnet -h
[snip]
-a, --multicast_ip Multicast Address (default: 225.3.19.154)
-p, --udp_net_port UDP port (default: 19000)
[/snip]
But my server has a completely different adress and
I want to work
it over the WAN.
I'd be extremely interested in WAN performance. Like I said, if my
setup has any concurrent traffic, I get serious xruns. I'm not sure
netjack will work very efficiently over a WAN.
David
[1]
http://trac.jackaudio.org/wiki/WalkThrough/User/NetJack2