[packages/jack-audio-connection-kit/JACK_0] - up to 0.125.0 - updated link patch - added man patch (missing man pages sources taken from github)

qboosh qboosh at pld-linux.org
Thu Oct 6 20:48:24 CEST 2016 

commit c4c52f595f1c5757f2c3c6f929ae77db7a49d0a2
Author: Jakub Bogusz <qboosh at pld-linux.org>
Date:   Thu Oct 6 20:50:22 2016 +0200

    - up to 0.125.0
    - updated link patch
    - added man patch (missing man pages sources taken from github)

 jack-audio-connection-kit-man.patch | 733 ++++++++++++++++++++++++++++++++++++
 jack-audio-connection-kit.spec      |  21 +-
 link.patch                          |  16 +-
 3 files changed, 748 insertions(+), 22 deletions(-)
---
diff --git a/jack-audio-connection-kit.spec b/jack-audio-connection-kit.spec
index e56f45c..288f7f1 100644
--- a/jack-audio-connection-kit.spec
+++ b/jack-audio-connection-kit.spec
@@ -10,24 +10,18 @@
 Summary:	The JACK Audio Connection Kit
 Summary(pl.UTF-8):	JACK - zestaw do połączeń audio
 Name:		jack-audio-connection-kit
-Version:	0.124.1
+Version:	0.125.0
 Release:	1
 License:	LGPL v2.1+ (libjack), GPL v2+ (the rest)
 Group:		Daemons
 # http://jackaudio.org/download - outdated?
-#Source0:	http://jackaudio.org/downloads/%{name}-%{version}.tar.gz
-Source0:	https://github.com/jackaudio/jack1/archive/%{version}/%{name}-%{version}.tar.gz
-# Source0-md5:	5805ff4d4305f05a04a6cd9fa345733c
-Source1:	https://github.com/jackaudio/headers/archive/%{version}/jack-headers-%{version}.tar.gz
-# Source1-md5:	c9c209fd9915c9d0b0ab4c60e31a867d
-Source2:	https://github.com/jackaudio/tools/archive/%{version}/jack-tools-%{version}.tar.gz
-# Source2-md5:	25772ce858298fbb66146345c4394df5
-Source3:	https://github.com/jackaudio/example-clients/archive/7fa089095c81e81dacd2554ae3184acc7f2d58ed/jack-example-clients-%{version}.tar.gz
-# Source3-md5:	dd415d1923a7d118d4c2454a1b58ae47
+Source0:	http://jackaudio.org/downloads/%{name}-%{version}.tar.gz
+# Source0-md5:	d9b7e230aeae2d5b45c7a822b2d2dd15
 Patch0:		%{name}-gcc4.patch
 Patch1:		%{name}-readline.patch
 Patch2:		link.patch
 Patch3:		%{name}-update.patch
+Patch4:		%{name}-man.patch
 URL:		http://jackaudio.org/
 BuildRequires:	alsa-lib-devel >= 1.0.18
 BuildRequires:	autoconf >= 2.50
@@ -188,14 +182,12 @@ Przykładowy klient zestawu JACK: jackrec. Jest wydzielony, ponieważ
 wymaga biblioteki libsndfile.
 
 %prep
-%setup -q -n jack1-%{version} -a1 -a2 -a3
-%{__mv} headers-%{version}/* jack
-%{__mv} tools-%{version}/* tools
-%{__mv} example-clients-*/* example-clients
+%setup -q
 %patch0 -p1
 %patch1 -p1
 %patch2 -p1
 %patch3 -p1
+%patch4 -p1
 
 %build
 %{__libtoolize}
@@ -219,6 +211,7 @@ wymaga biblioteki libsndfile.
 	--enable-ensure-mlock \
 	--enable-preemption-check \
 	--enable-resize \
+	--disable-silent-rules \
 	--enable-timestamps \
 	--with-default-tmpdir=/tmp \
 	--with-html-dir=%{_gtkdocdir}/%{name}
diff --git a/jack-audio-connection-kit-man.patch b/jack-audio-connection-kit-man.patch
new file mode 100644
index 0000000..64ec3da
--- /dev/null
+++ b/jack-audio-connection-kit-man.patch
@@ -0,0 +1,733 @@
+diff -Nur jack1-0.125.0/man.orig/alsa_in.0 jack1-0.125.0/man/alsa_in.0
+--- jack1-0.125.0/man.orig/alsa_in.0	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/alsa_in.0	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1,98 @@
++.TH ALSA_IO "1" "!DATE!" "!VERSION!"
++.SH NAME
++\fBalsa_in\fR, \fBalsa_out\fR \- Jack clients that perform I/O with an alternate audio interface
++.SH SYNOPSIS
++\fBalsa_in\fR [\fIoptions\fR]
++.br
++\fBalsa_out\fR [\fIoptions\fR]
++
++.SH DESCRIPTION
++A JACK client that opens a specified audio interface (different to the
++one used by the JACK server, if any) and moves audio data between its
++JACK ports and the interface. alsa_in will provide data from the
++interface (potentially for capture); alsa_out will deliver data to it
++(for playback).
++
++The audio interface used by alsa_in/alsa_out does not need to be
++synchronized with JACK backend (or the hardware it might be using).
++alsa_in/alsa_out tries to resample the output stream in an attempt to
++compensate for drift between the two clocks.
++
++As of jack-0.116.3 this works almost perfectly. It takes some time, to reach
++absolute resample-rate stability. So give it some minutes (its intended to be
++running permanently anyways)
++
++.SH OPTIONS
++.TP
++\fB\-j \fI jack_client_name\fR
++.br
++Set Client Name.
++.TP
++\fB\-d \fI alsa_device\fR  
++.br
++Use this Soundcard.
++.TP
++\fB\-v\fR  
++.br
++Verbose, prints out resample coefficient and other parameters useful for debugging, every 500ms.
++also reports soft xruns. 
++.TP
++\fB\-i\fR  
++.br
++Instrumentation. This logs the 4 important parameters of the samplerate control algorithm every 1ms.
++You can pipe this into a file, and plot it. Should only be necessary, if it does not work as
++expected, and we need to adjust some of the obscure parameters, to make it work. 
++Find me on irc.freenode.org #jack in order to set this up correctly.
++.TP
++\fB\-c \fI channels\fR  
++.br
++Set Number of channels.
++.TP
++\fB\-r \fI sample_rate\fR  
++.br
++Set sample_rate. The program resamples as necessary.
++So you can connect a 44k1 jackd to a soundcard only supporting
++48k. (default is jack sample_rate)
++.TP
++\fB\-p \fI period_size\fR  
++.br
++Set the period size. It is not related to the jackd period_size.
++Sometimes it affects the quality of the delay measurements.
++Setting this lower than the jackd period_size will only work, if you
++use a higher number of periods. 
++.TP
++\fB\-n \fI num_period\fR  
++.br
++Set number of periods. See note for period_size.
++.TP
++\fB\-q \fI quality\fR  
++.br
++Set the quality of the resampler from 0 to 4. This can significanly reduce
++CPU usage. Higher values give better quality and more CPU usage.
++.TP
++\fB\-m \fI max_diff\fR  
++.br
++The value when a soft xrun occurs. Basically the window, in which
++the dma pointer may jitter. I don't think its necessary to play with this anymore. 
++.TP
++\fB\-t \fI target_delay\fR  
++.br
++The delay alsa_io should try to approach. Same as for max_diff. It will be setup based on \-p and \-n
++which is generally sufficient.
++.TP
++\fB\-s \fI smooth_array_size\fR  
++.br
++This parameter controls the size of the array used for smoothing the delay measurement. Its default is 256.
++If you use a pretty low period size, you can lower the CPU usage a bit by decreasing this parameter.
++However most CPU time is spent in the resampling so this will not be much.
++.TP
++\fB\-C \fI P Control Clamp\fR  
++.br
++If you have a PCI card, then the default value (15) of this parameter is too high for \-p64 \-n2... Setting it to 5 should fix that.
++Be aware that setting this parameter too low, lets the hf noise on the delay measurement come through onto the resamplerate, so this
++might degrade the quality of the output. (but its a threshold value, and it has been chosen, to mask the noise of a USB card,
++which has an amplitude which is 50 times higher than that of a PCI card, so 5 wont loose you any quality on a PCI card)
++
++.SH AUTHOR
++Torben Hohn
++
+diff -Nur jack1-0.125.0/man.orig/alsa_out.0 jack1-0.125.0/man/alsa_out.0
+--- jack1-0.125.0/man.orig/alsa_out.0	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/alsa_out.0	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1 @@
++.so man1/alsa_in.1
+diff -Nur jack1-0.125.0/man.orig/.gitignore jack1-0.125.0/man/.gitignore
+--- jack1-0.125.0/man.orig/.gitignore	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/.gitignore	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1 @@
++*.1
+diff -Nur jack1-0.125.0/man.orig/jack_bufsize.0 jack1-0.125.0/man/jack_bufsize.0
+--- jack1-0.125.0/man.orig/jack_bufsize.0	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/jack_bufsize.0	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1,14 @@
++.TH JACK_BUFSIZE "1" "!DATE!" "!VERSION!"
++.SH NAME
++jack_bufsize \- JACK toolkit client to change the JACK buffer size
++.SH SYNOPSIS
++.B jack_bufsize bufsize
++.SH DESCRIPTION
++.B jack_bufsize
++jack_bufsize sets the size of the buffer (frames per period) used in JACK. 
++This change happens on-line (the JACK server and its clients do not need to be 
++restarted).
++.br
++When invoked without arguments, it prints the current bufsize, and exits.
++
++
+diff -Nur jack1-0.125.0/man.orig/jack_connect.0 jack1-0.125.0/man/jack_connect.0
+--- jack1-0.125.0/man.orig/jack_connect.0	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/jack_connect.0	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1,11 @@
++.TH JACK_CONNECT "1" "!DATE!" "!VERSION!"
++.SH NAME
++\fBjack_connect\fR, \fBjack_disconnect\fR \- JACK toolkit clients for connecting & disconnecting ports
++.SH SYNOPSIS
++\fB jack_connect\fR [ \fI-s\fR | \fI--server servername\fR ] [\fI-h\fR | \fI--help\fR ] port1 port2
++\fB jack_disconnect\fR [ \fI-s\fR | \fI--server servername\fR ] [\fI-h\fR | \fI--help\fR ] port1 port2
++.SH DESCRIPTION
++\fBjack_connect\fR connects the two named ports. \fBjack_disconnect\fR disconnects the two named ports.
++.SH RETURNS
++The exit status is zero if successful, 1 otherwise
++
+diff -Nur jack1-0.125.0/man.orig/jack_disconnect.0 jack1-0.125.0/man/jack_disconnect.0
+--- jack1-0.125.0/man.orig/jack_disconnect.0	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/jack_disconnect.0	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1 @@
++.so man1/jack_connect.1
+diff -Nur jack1-0.125.0/man.orig/jack_freewheel.0 jack1-0.125.0/man/jack_freewheel.0
+--- jack1-0.125.0/man.orig/jack_freewheel.0	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/jack_freewheel.0	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1,16 @@
++.TH JACK_FREEWHEEL "1" "!DATE!" "!VERSION!"
++.SH NAME
++jack_freewheel \- JACK toolkit client to control freewheeling mode
++.SH SYNOPSIS
++.B jack_freewheel [y|n]
++.SH DESCRIPTION
++.B jack_freewheel
++Turns freewheeling mode on (y) or off (n). While in freewheeling mode,
++the JACK server does not wait in between process() calls, and does not
++read or write data from/to any audio interface. That results in the JACK graph
++processing data as fast as possible. Freewheeling makes fast exports to 
++files possible.
++.PP
++There is no useful reason to use this tool other than testing. JACK
++clients that use freewheeling will turn it on and off themselves.
++
+diff -Nur jack1-0.125.0/man.orig/jack_impulse_grabber.0 jack1-0.125.0/man/jack_impulse_grabber.0
+--- jack1-0.125.0/man.orig/jack_impulse_grabber.0	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/jack_impulse_grabber.0	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1,11 @@
++.TH JACK_IMPULSE_GRABBER "1" "!DATE!" "!VERSION!"
++.SH NAME
++jack_impulse_grabber \- JACK toolkit client to grab an impulse (response)
++.SH SYNOPSIS
++\fBjack_impulse_grabber\fR \fB-d\fR \fIduration\fR [\fI-f\fR (C|gnuplot)]
++.SH DESCRIPTION
++\fBjack_impulse_grabber\fR is a JACK example client for collecting
++impulses recordings from JACK ports.
++
++
++
+diff -Nur jack1-0.125.0/man.orig/jack_iodelay.0 jack1-0.125.0/man/jack_iodelay.0
+--- jack1-0.125.0/man.orig/jack_iodelay.0	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/jack_iodelay.0	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1,53 @@
++.TH JACK_IODELAY "1" "!DATE!" "!VERSION!"
++.SH NAME
++jack_iodelay \- JACK toolkit client to measure roundtrip latency
++.SH SYNOPSIS
++.B jack_iodelay
++.SH DESCRIPTION
++.B 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.
++.PP
++The expected use is to connect jack_iodelay's output port to a
++hardware playback port, then use a physical loopback cable from the
++corresponding 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. 
++.PP
++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.
++.PP
++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.
++.PP
++If no incoming signal is detected from the input port, jack_iodelay
++will print 
++.PP
++\fT Signal below threshold... .\fR
++.PP
++every second until this changes (e.g. until you establish the correct connections).
++.PP
++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.
++.SH AUTHOR
++Originally written in C++ by Fons Adriensen, ported to C by Torben Hohn.
++
++
++
+diff -Nur jack1-0.125.0/man.orig/jack_load.0 jack1-0.125.0/man/jack_load.0
+--- jack1-0.125.0/man.orig/jack_load.0	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/jack_load.0	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1,28 @@
++.TH JACK_LOAD "1" "!DATE!" "!VERSION!"
++.SH NAME
++jack_load \- JACK toolkit client for loading in-process clients
++.SH SYNOPSIS
++\fBjack_load\fR [ \fI-i\fR initstring ] [ \fI-s\fR servername ] [\fI-w\fR ] client-name so-name [ initstring ]
++.SH DESCRIPTION
++\fBjack_load\fR is a JACK toolkit client. It loads the specified plugin and creates an in-process client.
++.SH ARGUMENTS
++.PP
++The client-name must be a currently unused client name.
++.PP
++The so-name is the name of file that client code is stored in (typically, \fIclientname.so\fR)
++.SH OPTIONS
++.TP
++\fB-i\fR, \fB--init\fR init-string
++.br
++initialization string passed to the in-process client. Note that this can also be specified as the last argument on the command line.
++.TP
++\fB-s\fR, \fB--server\fR servername
++.br
++Name of JACK server to connect to
++.TP
++\fB-w\fR, \fB--wait\fR
++Wait for a signal (eg. from Ctrl-c) and then unload the client.
++.SH AUTHOR
++Jeremy Hall
++
++
+diff -Nur jack1-0.125.0/man.orig/jack_load_test.0 jack1-0.125.0/man/jack_load_test.0
+--- jack1-0.125.0/man.orig/jack_load_test.0	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/jack_load_test.0	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1,11 @@
++.TH JACK_LOAD_TEST "1" "!DATE!" "!VERSION!"
++.SH NAME
++jack_load_test \- JACK toolkit client which occupies the cpu for some time in process.
++.SH SYNOPSIS
++.B jack_load_test -t \fItime\fR
++.SH DESCRIPTION
++.B jack_load_test
++jack_load_test is a client without ports, which just occupies the cpu for \fItime\fR
++miliseconds. It is quite useful to test jackd behaviour under load.
++
++
+diff -Nur jack1-0.125.0/man.orig/jack_lsp.0 jack1-0.125.0/man/jack_lsp.0
+--- jack1-0.125.0/man.orig/jack_lsp.0	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/jack_lsp.0	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1,51 @@
++.TH JACK_LSP "1" "!DATE!" "!VERSION!"
++.SH NAME
++jack_lsp \- JACK toolkit client to list informtion on ports
++.SH SYNOPSIS
++\fBjack_lsp\fR [ \fI-s\fR | \fI--server\fR servername ] [ \fI-AclLptvhuU\fR ]
++.SH DESCRIPTION
++\fBjack_lsp\fR lists all known ports associated with a JACK
++server. It can also optionally list various kinds of information about each port.
++.SH OPTIONS
++.TP
++\fB-s\fR, \fB--server\fR \fIservername\fR
++.br
++Connect to the jack server named \fIservername\fR
++.TP
++\fB-A\fR, \fB--aliases\fR
++.br
++List aliases for each port
++.TP
++\fB-c\fR, \fB--connections\fR
++.br
++List connections to/from each port
++.TP
++\fB-l\fR, \fB--latency\fR
++.br
++Display per-port latency in frames at each port
++.TP
++\fB-p\fR, \fB--properties\fR
++.br
++Display port properties. Output may include input|output, can-monitor, physical, terminal
++.TP
++\fB-t\fR, \fB--type\fR
++.br
++Display port type
++.TP
++\fB-u\fR, \fB--uuid\fR
++.br
++Display client UUIDs instead of names
++.TP
++\fB-U\fR
++.br
++Show port UUIDs as well as names
++.TP
++\fB-h\fR, \fB--help\fR
++.br
++Display help/usage message
++.TP
++\fB-v\fR, \fB--version\fR
++.br
++Output version information and exit
++
++
+diff -Nur jack1-0.125.0/man.orig/jack_metro.0 jack1-0.125.0/man/jack_metro.0
+--- jack1-0.125.0/man.orig/jack_metro.0	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/jack_metro.0	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1,40 @@
++.TH JACK_METRO "1" "!DATE!" "!VERSION!"
++.SH NAME
++jack_metro \- JACK toolkit metronome
++.SH SYNOPSIS
++\fBjack_metro\fR [ \fI-n\fR name ] [ \fI-f\fR hz ] [ \fI-D\fR msecs ] [\fI-a\fR % ] [ \fI-d\fR % ] \fI-b\fR bpm 
++.SH DESCRIPTION
++\fBjack_metro\fR is a simple metronome for JACK. It generates a
++synthetic "tick" sound for every beat. Note that is does \fBnot\fR
++connect its output port by default - to hear the sound it makes you must
++connect them using some other tool.
++.SH OPTIONS
++.TP
++\fB-n\fR, \fB--name\fR
++.br
++Specify a name for this instance of the metronome.
++.TP
++\fB-f\fR, \fB--frequency\fR Hz
++.br
++Define the frequency of the "tick" in Hz.
++.TP
++\fB-D\fR, \fB--duration\fR msecs
++.br
++Define the duration of the "tick" in milliseconds.
++.TP
++\fB-a\fR, \fB--attack\fR %-age
++.br
++Define the duration of the attack phase of the "tick" as a percentage
++of the duration.
++.TP
++\fB-d\fR, \fB--decay\fR %-age
++.br
++Define the duration of the decay phase of the "tick" as a percentage
++of the duration.
++.TP
++\fB--b\fR, \fB--bpm\fR bpm
++.br
++Define the number of beats per minute.
++.SH AUTHOR
++Anthony Van Groningen
++
+diff -Nur jack1-0.125.0/man.orig/jack_monitor_client.0 jack1-0.125.0/man/jack_monitor_client.0
+--- jack1-0.125.0/man.orig/jack_monitor_client.0	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/jack_monitor_client.0	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1,18 @@
++.TH JACK_CONNECT "1" "!DATE!" "!VERSION!"
++.SH NAME
++jack_monitor_client \- The JACK Audio Connection Kit example client
++.SH SYNOPSIS
++.B jack_monitor_client
++client-name
++.PP
++The client-name must be the name of a existing client that monitoring is 
++to be enabled for.
++.SH DESCRIPTION
++.B jack_monitor_client
++is an example client for the JACK Audio Connection Kit. It enables
++monitoring for the specified client.
++.SH AUTHOR
++Jeremy Hall
++.PP
++This manpage was written by Robert Jordens <jordens at debian.org> for Debian.
++
+diff -Nur jack1-0.125.0/man.orig/jack_netsource.0 jack1-0.125.0/man/jack_netsource.0
+--- jack1-0.125.0/man.orig/jack_netsource.0	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/jack_netsource.0	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1,109 @@
++.TH JACK_NETSOURCE "1" "!DATE!" "!VERSION!"
++.SH NAME
++jack_netsource \- Netjack Master client for one slave
++.SH SYNOPSIS
++\fBjack_netsource\fR [ \fI-H\fR hostname ] [ \fIoptions\fR ]
++
++.SH DESCRIPTION
++\fBjack_netsource\fR The Master side of a netjack connection. Represents the slave jackd -dnet in the master jack graph.
++Most connection parameters are configured via the netsource, and the slave will set itself up according to the commandline
++option given to jack_netsource.
++.br
++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. 
++.br
++But the main usecase is of course a LAN, where it can achieve one jack period of latency.
++
++.SH OPTIONS
++.TP
++\fB-h\fR this help text
++.TP
++\fB-H\fR \fIslave host\fR
++.br
++Host name of the slave JACK
++.TP
++\fB-o\fR \fInum channels\fR
++.br
++Number of audio playback channels
++.TP
++\fB-i\fR \fInum channels\fR
++.br
++Number of audio capture channels
++.TP
++\fB-O\fR \fInum channels\fR
++.br
++Number of midi playback channels
++.TP
++\fB-I\fR \fInum channels\fR
++.br
++Number of midi capture channels
++.TP
++\fB-n\fR \fIperiods\fR
++.br
++Network latency in JACK periods
++.TP
++\fB-p\fR \fIport\fR
++.br
++UDP port that the slave is listening on
++.TP
++\fB-r\fR \fIreply port\fR
++.br
++UDP port that we are listening on
++.TP
++\fB-B\fR \fIbind port\fR
++.br
++reply port, for use in NAT environments
++.TP
++\fB-b\fR \fIbitdepth\fR
++.br
++Set transport to use 16bit or 8bit
++.TP
++\fB-c\fR \fIbytes\fR
++.br
++Use CELT encoding with <bytes> per period and channel
++.TP
++\fB-m\fR \fImtu\fR
++.br
++Assume this mtu for the link
++.TP
++\fB-R\fR \fIN\fR
++.br
++Redundancy: send out packets N times.
++.TP
++\fB-e\fR
++.br
++skip host-to-network endianness conversion
++.TP
++\fB-N\fR \fIjack name\fR
++.br
++Reports a different client name to jack
++.TP
++.TP
++\fB-s\fR, \fB--server\fR \fIservername\fR
++.br
++Connect to the jack server named \fIservername\fR
++.TP
++\fB-h\fR, \fB--help\fR
++.br
++Display help/usage message
++.TP
++\fB-v\fR, \fB--version\fR
++.br
++Output version information and exit
++
++
++.SH EXAMPLES
++
++.PP
++run a 4 audio channel bidirectional link with one period of latency and no midi channels. Audio data is flowing uncompressed over the wire:
++.br
++On \fIhostA\fR:
++.IP
++\fBjackd \-d alsa \fR
++.br
++\fBjack_netsource \-H hostB -n1 -i4 -o4 -I0 -O0 \fR
++.PP
++On \fIhostB\fR:
++.IP
++\fBjackd \-d net \fR
++
+diff -Nur jack1-0.125.0/man.orig/jack_property.0 jack1-0.125.0/man/jack_property.0
+--- jack1-0.125.0/man.orig/jack_property.0	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/jack_property.0	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1,64 @@
++.TH JACK_PROPERTY "1" "!DATE!" "!VERSION!"
++.SH NAME
++jack_property \- JACK client to list, set and delete metadata information
++.SH SYNOPSIS
++\fBjack_property\fR -l
++.br
++\fBjack_property\fR [ -c | -p ] -l \fIidentifier\fR 
++.br
++\fBjack_property\fR [ -c | -p ] -l \fIidentifier\fR \fIkey\fR
++.br
++\fBjack_property\fR [ -c | -p ] -s \fIidentifier\fR \fIkey\fR \fIvalue\fR [ \fItype\fR ]
++.br
++\fBjack_property\fR [ -c | -p ] -d \fIidentifier\fR 
++.br
++\fBjack_property\fR [ -c | -p ] -d \fIidentifier\fR \fIkey\fR
++.br
++\fBjack_property\fR -D 
++.SH DESCRIPTION
++\fBjack_property\fR can be used to list, set and delete any and all metadata associated with the ports
++and clients of a JACK server.
++.P
++There are three main ways to use the command. The \fB-l\fR option is used to list existing metadata. The \fB-s\fR option is used
++to set metadata. The \fB-d/-D\fR options are used to delete metadata.
++.P
++The \fIidentifier\fR is normally a UUID (UUIDs for ports and clients can be shown with jack_lsp(1)). If the \fB-c\fR option is used, then \fIidentifier\fR will
++be interpreted as a client name, and its UUID will be looked up internally and used for the relevant metadata operation. If the \fB-p\fR option is used, then \fIidentifier\fR will
++be interpreted as a port name and its UUID  will be looked up internally and used for the relevant metadata operation.
++.P
++The \fIkey\fR is an arbitary string that identifies the metadata to be operated upon.
++.P
++The \fIvalue\fR is an arbitrary string that defines the value of the metadata to be created.
++.P
++The \fItype\fR is an optional MIME type, given as a string. An empty type for a piece of metadata results in it being interpreted as "text/UTF-8". 
++.SH OPTIONS
++.TP 6
++-l
++list all metadata currently defined
++.TP
++-l identifier
++list all metadata currently defined for \fIidentifier\fR
++.TP
++-l identifier key
++show the value of the metadata associated with key for \fIidentifier\fR
++.TP
++-d identifier
++deletes all metadata for \fIidentifier\fR
++.TP
++-d identifier key
++deletes the metadata associated with \fIkey\fR for \fIidentifier\fR
++.TP
++-D
++delete all currently defined metadata
++.TP
++-s identifier key value [ type ]
++sets the metadata associated with \fIkey\fR to \fIvalue\fR for \fIidentifer\fR, with its type set to \fItype\fR if given
++.TP
++-c 
++interpret a given identifier as a client name rather than a UUID
++.TP 
++-p
++interpret a given identifier as a port name rather than a UUID
++
++
++
+diff -Nur jack1-0.125.0/man.orig/jackrec.0 jack1-0.125.0/man/jackrec.0
+--- jack1-0.125.0/man.orig/jackrec.0	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/jackrec.0	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1,23 @@
++.TH JACKREC "1" "!DATE!" "!VERSION!"
++.SH NAME
++jackrec \- JACK toolkit client for recording audio
++.SH SYNOPSIS
++.B jackrec
++\-f filename \-d seconds [ \-b bitdepth ] port1 [ port2 ... ]
++.SH DESCRIPTION
++.B jackrec is a basic, but useful, audio recorder that will record
++audio from 1 or more JACK ports to a file on disk. The file format is
++always RIFF/WAV, with samples stored as signed integers. The sample
++bit depth can be selected using the \fI-b\fR option. The file will
++have as many channels as there are ports specified on the command line
++- each channel will contain the data recorded from one port. The user
++should generally specify the duration (in seconds) using the \fI-d\fR
++option. If not specified, jackrec will record until terminated by a
++signal (eg. from Ctrl-c).
++.PP
++This application is not intended to be a heavy duty audio recorder,
++and originated as an example client to show how to handle threading
++and disk I/O in a JACK client. However, it is a useful, simple
++recorder and is included in the JACK toolkit as a result.
++
++
+diff -Nur jack1-0.125.0/man.orig/jack_samplerate.0 jack1-0.125.0/man/jack_samplerate.0
+--- jack1-0.125.0/man.orig/jack_samplerate.0	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/jack_samplerate.0	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1,9 @@
++.TH JACK_SAMPLERATE "1" "!DATE!" "!VERSION!"
++.SH NAME
++jack_samplerate \- JACK toolkit client to print current samplerate
++.SH SYNOPSIS
++.B jack_samplerate
++.SH DESCRIPTION
++.B jack_samplerate prints the current samplerate, and exits.
++
++
+diff -Nur jack1-0.125.0/man.orig/jack_showtime.0 jack1-0.125.0/man/jack_showtime.0
+--- jack1-0.125.0/man.orig/jack_showtime.0	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/jack_showtime.0	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1,13 @@
++.TH JACK_SHOWTIME "1" "!DATE!" "!VERSION!"
++.SH NAME
++jack_showtime \- The JACK Audio Connection Kit example client
++.SH SYNOPSIS
++.B jack_showtime
++.SH DESCRIPTION
++.B jack_showtime
++prints the current timebase information to stdout
++.SH AUTHOR
++Paul Davis
++.PP
++This manpage was written by Stefan Schwandter <swan at debian.org>
++
+diff -Nur jack1-0.125.0/man.orig/jack_transport.0 jack1-0.125.0/man/jack_transport.0
+--- jack1-0.125.0/man.orig/jack_transport.0	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/jack_transport.0	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1,13 @@
++.TH JACK_TRANSPORT "1" "!DATE!" "!VERSION!"
++.SH NAME
++jack_transport \- JACK toolkit client for transport control
++.SH SYNOPSIS
++.B jack_transport
++.SH DESCRIPTION
++.B jack_transport
++is a toolkit client for the JACK Audio Connection Kit. It provides command-line
++control over the JACK transport system. Type help at jack_transport's
++command prompt to see the available commands.
++.SH AUTHOR
++Jeremy Hall
++
+diff -Nur jack1-0.125.0/man.orig/jack_unload.0 jack1-0.125.0/man/jack_unload.0
+--- jack1-0.125.0/man.orig/jack_unload.0	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/jack_unload.0	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1,19 @@
++.TH JACK_UNLOAD "1" "!DATE!" "!VERSION!"
++.SH NAME
++jack_unload \- The JACK Audio Connection Kit example client
++.SH SYNOPSIS
++.B jack_unload 
++client-name
++.PP
++The client-name must be the name of a loaded client that can be unloaded.
++.SH DESCRIPTION
++.B jack_unload
++is the counterpart to 
++.B jack_load
++and unloads the specified client.
++.SH EXAMPLE
++.B jack_unload in_process_test
++.SH AUTHOR
++Jeremy Hall
++.PP
++This manpage was written by Robert Jordens <jordens at debian.org> for Debian.
+diff -Nur jack1-0.125.0/man.orig/jack_wait.0 jack1-0.125.0/man/jack_wait.0
+--- jack1-0.125.0/man.orig/jack_wait.0	1970-01-01 01:00:00.000000000 +0100
++++ jack1-0.125.0/man/jack_wait.0	2016-09-15 00:01:00.000000000 +0200
+@@ -0,0 +1,41 @@
++.TH JACK_WAIT "1" "!DATE!" "!VERSION!"
++.SH NAME
++jack_wait \- JACK toolkit client to check and wait for existence/exit of jackd.  
++.SH SYNOPSIS
++\fBjack_wait\fR [ \fI-s\fR | \fI--server\fR servername ] [ \fI-t\fR | \fI--timeout\fR timeout_seconds [ \fI-cqwhv\fR ]
++.SH DESCRIPTION
++\fBjack_wait\fR When invoked with \fI-c\fR it only checks for the existence of a jack server. When invoked with \fI-w\fR the
++program will wait for a jackd to be available.
++The \fI-q\fR makes it wait for the jackd to exit.
++
++.SH OPTIONS
++.TP
++\fB-w\fR, \fB--wait\fR
++.br
++Wait for jackd to be available.
++.TP
++\fB-q\fR, \fB--quit\fR
++.br
++Wait for jackd quit.
++.TP
++\fB-c\fR, \fB--check\fR
++.br
++Only check for existence of jackd, and exit.
++.TP
++\fB-s\fR, \fB--server\fR \fIservername\fR
++.br
++Connect to the jack server named \fIservername\fR
++.TP
++\fB-t\fR, \fB--timeout\fR \fItimeout_seconds\fR
++.br
++Only wait \fItimeout_seconds\fR.
++.TP
++\fB-h\fR, \fB--help\fR
++.br
++Display help/usage message
++.TP
++\fB-v\fR, \fB--version\fR
++.br
++Output version information and exit
++
++
diff --git a/link.patch b/link.patch
index 541a2d6..a632365 100644
--- a/link.patch
+++ b/link.patch
@@ -1,16 +1,16 @@
 - fix for "Unresolved symbols found"
 - avoid unnecessary linking with -ldb
---- jack1-0.124.1/jackd/Makefile.am.orig	2014-02-01 16:19:21.505595646 +0100
-+++ jack1-0.124.1/jackd/Makefile.am	2014-02-01 16:22:41.085587271 +0100
+--- jack-audio-connection-kit-0.125.0/jackd/Makefile.am.orig	2016-10-06 18:57:26.766926734 +0200
++++ jack-audio-connection-kit-0.125.0/jackd/Makefile.am	2016-10-06 18:58:38.250259246 +0200
 @@ -51,7 +51,7 @@
-         ../libjack/midiport.c ../libjack/ringbuffer.c ../libjack/shm.c \
-         ../libjack/thread.c ../libjack/time.c  ../libjack/transclient.c \
-         ../libjack/unlock.c ../libjack/uuid.c ../libjack/metadata.c
--libjackserver_la_LIBADD  = simd.lo -ldb @OS_LDFLAGS@ 
-+libjackserver_la_LIBADD  = simd.lo -ldb @OS_LDFLAGS@ $(CAP_LIBS)
+ libjackserver_la_CFLAGS = $(AM_CFLAGS)
+ 
+ libjackserver_la_SOURCES = engine.c clientengine.c transengine.c controlapi.c
+-libjackserver_la_LIBADD  = $(top_builddir)/libjack/simd.lo $(top_builddir)/libjack/libjackcommon.la $(top_builddir)/libjack/libjackdaemon.la -ldb @OS_LDFLAGS@
++libjackserver_la_LIBADD  = $(top_builddir)/libjack/simd.lo $(top_builddir)/libjack/libjackcommon.la $(top_builddir)/libjack/libjackdaemon.la -ldb $(CAP_LIBS) @OS_LDFLAGS@
  libjackserver_la_LDFLAGS  = -export-dynamic -version-info @JACK_SO_VERSION@
  
- simd.lo: $(srcdir)/../libjack/simd.c
+ man_MANS = jackd.1 jackstart.1
 --- jack1-0.124.1/configure.ac.orig	2014-02-01 16:33:36.412226435 +0100
 +++ jack1-0.124.1/configure.ac	2014-02-01 16:42:57.178869571 +0100
 @@ -232,7 +232,7 @@
================================================================

---- gitweb:

http://git.pld-linux.org/gitweb.cgi/packages/jack-audio-connection-kit.git/commitdiff/c4c52f595f1c5757f2c3c6f929ae77db7a49d0a2

More information about the pld-cvs-commit mailing list