21 Sep
2010
21 Sep
'10
6:56 p.m.
Hi Paul,
On Mon, 20 Sep 2010 15:11:09 -0400
Paul Davis <paul(a)linuxaudiosystems.com> wrote:
On Mon, Sep 20, 2010 at 2:15 PM, Julien Claassen
<julien(a)c-lab.de>
wrote:
jacktrip is interesting. I just tried a simple:
-> start jackd on server
-> start jackd on client with same rates etc
-> start jacktrip -s on server
-> start jacktrip -c <server-ip>
on both machines, jacktrip shows up as jack client but 'sending' is
never 'received' in either direction.
Server logs: "Waiting for Connection From Client..." and that's it.
At any rate, netjack2 works for me but what is the purpose of jacktrip
if netjack works?
Hello David!
I think that's where the CELT codec comes in. As to the other
side: It will be jack1. I didn't read anything saying, that jack2
and jack1 netjack aren't compatible.
they are completely incompatible.
for WAN usage, netjack2 is not an option. either use netjack1 (aka
"netone") with CELT or jack.trip