jack_netsource(1) [debian man page]

JACK_NETSOURCE(1)					      General Commands Manual						 JACK_NETSOURCE(1)

NAME

       jack_netsource - Netjack Master client for one slave

SYNOPSIS

       jack_netsource [ -H hostname ] [ options ]

DESCRIPTION

       jack_netsource The Master side of a netjack connection. Represents the slave jackd -dnet in the master jack graph.  Most connection parame-
       ters are configured via the netsource, and the slave will set itself up according to the commandline option given to jack_netsource.
       Netjack allows low latency audio connections over general IP networks. When using celt for compression, it is even  possible  to  establish
       transatlantic links, with latencies not much over the actual ping time.
       But the main usecase is of course a LAN, where it can achieve one jack period of latency.

OPTIONS

       -h this help text

       -H slave host
	      Host name of the slave JACK

       -o num channels
	      Number of audio playback channels

       -i num channels
	      Number of audio capture channels

       -O num channels
	      Number of midi playback channels

       -I num channels
	      Number of midi capture channels

       -n periods
	      Network latency in JACK periods

       -p port
	      UDP port that the slave is listening on

       -r reply port
	      UDP port that we are listening on

       -B bind port
	      reply port, for use in NAT environments

       -b bitdepth
	      Set transport to use 16bit or 8bit

       -c bytes
	      Use CELT encoding with <bytes> per period and channel

       -m mtu
	      Assume this mtu for the link

       -R N
	      Redundancy: send out packets N times.

       -e
	      skip host-to-network endianness conversion

       -N jack name
	      Reports a different client name to jack

       -s, --server servername
	      Connect to the jack server named servername

       -h, --help
	      Display help/usage message

       -v, --version
	      Output version information and exit

EXAMPLES

       run a 4 audio channel bidirectional link with one period of latency and no midi channels. Audio data is flowing uncompressed over the wire:
       On hostA:

	      jackd -d alsa
	      jack_netsource -H hostB -n1 -i4 -o4 -I0 -O0

       On hostB:

	      jackd -d net

0-122-0 							  September 2012						 JACK_NETSOURCE(1)

JACK_IODELAY(1) 					      General Commands Manual						   JACK_IODELAY(1)

NAME

       jack_iodelay - JACK toolkit client to measure roundtrip latency

SYNOPSIS

       jack_iodelay

DESCRIPTION

       jack_iodelay  will  create  one input and one output port, and then measures the latency (signal delay) between them. For this to work, the
       output port must be connected to its input port. The measurement is accurate to a resolution of greater than 1 sample.

       The expected use is to connect jack_iodelay's output port to a hardware playback port, then use a physical loopback cable from  the  corre-
       sponding  hardware  output connector to an input connector, and to connect that corresponding hardware capture port to jack_iodelay's input
       port. This creates a roundtrip that goes through any analog-to-digital or digital-converters that are present in the audio hardware.

       Although the hardware loopback latency is the expected use, it is also possible to use jack_iodelay to measure the latency along any  fully
       connected signal path, such as those involving other JACK clients.

       Once  jack_iodelay  completes  its measurement it will print the total latency it has detected. This will include the JACK period length in
       addition to any other latency in the signal path. It will continue to print the value every 0.5 seconds or so so that if you wish  you  can
       vary aspects of the signal path to see their effect on the measured latency.

       If no incoming signal is detected from the input port, jack_iodelay will print

	Signal below threshold... .

       every second until this changes (e.g. until you establish the correct connections).

       To  use	the value measured by jack_iodelay with the -I and -O arguments of a JACK backend (also called Input Latency and Output Latency in
       the setup dialog of qjackctl), you must subtract the JACK period size from the result. Then, if you believe that  the  latency  is  equally
       distributed  between  the input and output parts of your audio hardware (extremely likely), divide the result by two and use that for input
       and/or output latency value. Doing this measurement will enable JACK clients that use the JACK latency  API  to	accurately  position/delay
       audio to keep signals synchronized even when there are inherent delays in the end-to-end signal pathways.

AUTHOR

       Originally written in C++ by Fons Adriensen, ported to C by Torben Hohn.

0-122-0 							  September 2012						   JACK_IODELAY(1)