Jörn wrote: > > there is also netjack, which is part of the jack package. it does the > same job, but sample-synchronized. > the downside of netjack is that two mutually incompatible > implementations exist, which makes for a somewhat intimidating first > contact... but it works very well.
> with netjack, you would run the second machine (the one with the 8ch > card) as master, running the jack_netsource program. > the other machine is then slaved to it, using jackd -d net. > the jack graph on the slave machine will be timed by the master. that > means you don't have two diverging sample clocks, as is the case with > jacktrip (and which necessitates some messy compensation, such as > dropping or duplicating frames, which is usually not be tolerable in a > studio context). > Must admit I was (possibly still am) a naïve debutant ... and went to <http://www.jackaudio.org/netjack> and whilst I _suspected_ anything working with Jack would be better, having had my fingers burnt with other applications that think mono is standard and two channels state of the art, the text "jack.trip was originally created for streaming relatively large numbers of channels ..." attracted me ;-)> Thought bandwidth would be no problem on a 1 metre cable (but forgot to buy gold-plated platinum cabling* ;-(> Michael *Suspect it is one of the ethernet cards, or its driver ... _______________________________________________ Sursound mailing list [email protected] https://mail.music.vt.edu/mailman/listinfo/sursound
