Re: [Jack-Devel] Jacktrip performance and reliability? (St?phane Letz)

Prev	Next Index
Date	Tue, 05 Nov 2013 15:10:59 +0100
From	Stéphane Letz <[hidden] at grame dot fr>
To	Robin Renwick <[hidden] at qub dot ac dot uk>, Chris Chafe <[hidden] at ccrma dot Stanford dot EDU>
Cc	"[hidden] at lists dot jackaudio dot org" <[hidden] at lists dot jackaudio dot org>
In-Reply-To	Robin Renwick [Jack-Devel] Jacktrip performance and reliability? (St?phane Letz)

Le 4 nov. 2013 à 23:00, Robin Renwick <[hidden]> a écrit :

>> Hi,
>> 
>> Anyone here to comment on Jacktrip performance and reliability on internet, especially running on OSX?
>> 
>> (https://ccrma.stanford.edu/groups/soundwire/software/jacktrip/  and http://code.google.com/p/jacktrip/)
>> 
>> Thanks.
>> 
>> St?phane
> 
> Hi,
> 
> We at www.sarc.qub.ac.uk, along with a host of other universities have been using JackTrip for a number of years now as our default udp audio transfer software tool with respect to Network Music Performance Research. 
> 
> I can safely vouch that it has been extremely reliable and robust. 
> 
> We have been involved in a many number of multi-site performances which have utilised the system on both OSX and Linux and have never ran into software issues concerned directly with JackTrip. 
> 
> There have been instances where we have run three sites or more - implementing a 15 plus discrete channel system at 44.1, 16bit. 
> 
> We have however run into issues of compatibility with respect to JackPilot/QJackCntrl and iterations of Mac OSX. These issues are slowly being ironed out, though they seem to be lagging behind the pace of OSX development. 
> 
> The most stable system i have personally used is OSX 10.6.8 coupled with the latest JackTrip build, along with the latest JackPilot Iteration (not the 10.7/10.8 Beta)
> 
> If you have any other questions regarding this, i can be reached at
> 
> [hidden]
> 
> cheers,
> 
> Robin
> _

Thanks for you help.

We tried here between 2 machines, both are behind a NAT (so have a 192.168.XXX.XXX kind of address). One of them was configured to redirect the 4464 port on the real 192.168.XXX.XXX  address and was started as the server. On client I did :

./jacktrip -c 82.67.55.75   got a connection but then jacktrip crashed with the following log:



We will try again this evening by redirecting the 4464 port on both sides.

Stephane     

* Attachment: 'jacktrip_2013-11-05-150119_magellan-pro.crash'
content-type: application/octet-stream

Prev	Next Index

1383660642.21660_0.ltw:2, <8E340436-2537-4AB6-8756-5A480A2B3AB0 at grame dot fr>