JACK over network
(Nedko Arnaudov`s blog)

Today I’ve tried to create a working netjack setup over Internet. I was curious whether the netjack technology has reached a usable by general public state.

I’ve tried two tools that aim to simplify such setups: The Mike Cookson`s jack-netmanager-gtk- and and Torben Hohn`s netjackconnect-0.8.

The jack-netmanager-gtk suggested to install it and I did it in “~/opt/”, but it will be useful if it can be started without installing it. It presents a GUI dialog with options. Without much knowledge of netjack technology I was not sure what to do. I’ve got some information from the wiki page about netjack1 at jackaudio.org, but it was not enough. That wiki page does not give overview on how to setup the firewall, does not give overview of the communication channels and does not tells much about the (UDP) ports being used. I’ve been pointed by Torben to try his netjackconnect (aka njc). The use of njc requires registration on the http://hochstrom.endofinternet.org/ site and it does not even start if ran manually. Maybe this approach is intentional and is supposed to track and control netjack interactions over Internet, something I definitively don’t like. Global tracker is definitively a good thing, but only if it is optional and not forced.

A JACK Internet connectivity manager should present a dialog a choice of whether to connect to user supplied IP address or to use a tracker. List of such trackers should be configurable with the default one being hosted under jackaudio.org. All connectivity options should be negotiated directly between peers and not through a man-in-the-middle tracker site. Sending connectivity parameters to the tracker should be suggested but optional and should default to *privacy*.

The netjack1 documentation should contain an overview of the the interaction between involved software components. The network communication channel(s) should be explicitly described and the UDP firewall “puncturing” should be mentioned as well.

I’ve set up the netone (jack2) driver with alsa_out. The audio sent to to soundcard ports was chopped and it remained chopped even with high buffer sizes (big latencies). With big buffer size, I’ve tracked chops to “delay” lines in alsa_out output, but it was not obvious whether these lines are errors or part of normal output.

Created: Sun Aug 08 00:52:33 +0300 2010

Valid XHTML 1.0 Strict Valid CSS!