Jack - Revision history

DKlann: Add discussion about and link to the github issue about Pipewire.

2025-10-07T13:09:37Z

Add discussion about and link to the github issue about Pipewire.

DKlann: Update links from "http" to "https". Verified links.

2024-04-17T02:32:20Z

Update links from "http" to "https". Verified links.

Ltyndale at 05:47, 11 February 2024

2024-02-11T05:47:27Z

Ltyndale: /* Enabling Promiscuous Mode on Rivendell V3 */

2024-02-11T05:46:59Z

‎Enabling Promiscuous Mode on Rivendell V3

Ltyndale: /* Adding JACK Clients */

2024-02-11T05:27:11Z

‎Adding JACK Clients

Ltyndale: /* Enabling Promiscuous Mode on Rivendell V3 */

2024-02-11T05:21:52Z

‎Enabling Promiscuous Mode on Rivendell V3

Ltyndale: /* Overview */

2024-02-11T05:20:27Z

‎Overview

Ltyndale: /* Configure Rivendell 3 For Use With JACK */

2024-02-11T05:18:57Z

‎Configure Rivendell 3 For Use With JACK

Ltyndale at 05:18, 11 February 2024

2024-02-11T05:18:12Z

Ltyndale: /* Overview */

2024-02-11T05:10:37Z

‎Overview

← Older revision		Revision as of 13:09, 7 October 2025
Line 221:		Line 221:
	This is complete as of April, 2021: <del>To do: in ''pmw-jack-setup'': use data in ''/proc/asound'' to automatically discern the number of input and output channels for ALSA devices.</del>		This is complete as of April, 2021: <del>To do: in ''pmw-jack-setup'': use data in ''/proc/asound'' to automatically discern the number of input and output channels for ALSA devices.</del>

−	In ~~2021~~ the [https://pipewire.org/ pipewire] audio subsystem is ~~maturing~~ and ~~aims to be~~ compatible with ~~and to eventually replace~~ both the PulseAudio and the JACK audio systems. Pipewire may include more “plumbing” tools over the long run.	+	In 2025 the [https://pipewire.org/ pipewire] audio subsystem is mature and is compatible with both the PulseAudio and the JACK audio systems. Pipewire may include more “plumbing” tools over the long run. See [https://github.com/ElvishArtisan/rivendell/issues/823 this Github discussion] with instructions on how to configure Rivendell and Pipewire to enable the two to work together.

@@ Line 68: / Line 68: @@
 :(As an aside, when you use JACK for Rivendell&rsquo;s audio routing, you can also use any other [https://jackaudio.org/applications/ JACK-enabled audio app] alongside Rivendell.)
-:(Another aside: know that Rivendell works fine using both JACK clients and [http://www.audioscience.com/ Audio Science] adapters.)
+:(Another aside: know that Rivendell works fine using both JACK clients and [https://www.audioscience.com/ Audio Science] adapters.)
 Set up JACK on a per-host basis by modifying the configuration in [[RDAdmin]]->[[RDAdmin#Manage_Hosts|Manage Hosts]]->''hostname''. In the host configuration window, touch the '''JACK Settings''' button to manage the Jack settings.
@@ Line 148: / Line 148: @@
 Once you have successfully configured Rivendell to launch JACK and configure your audio devices, you need to &ldquo;connect&rdquo; the devices to Rivendell. There are several ways to do this, including:
-:* run one or more Rivendell [http://opsguide.rivendellaudio.org/html/chapter.rml.html Macros] to make the connections (see [http://opsguide.rivendellaudio.org/html/sect.rml.commands.html#sect.rml.connect_jack_ports__jc_ JC])
+:* run one or more Rivendell [https://opsguide.rivendellaudio.org/html/chapter.rml.html Macros] to make the connections (see [https://opsguide.rivendellaudio.org/html/sect.rml.commands.html#sect.rml.connect_jack_ports__jc_ JC])
 :* run a JACK plumbing service daemon such as ''jack-plumbing'' to automate the connections
 :* run the command line ''jack_connect'' application to make the connections
 :* use a graphical tool such as [https://qjackctl.sourceforge.io/ qjackctl] or [https://drobilla.net/software/patchage patchage] to make the connections
-The most reliable methods for making JACK connections are those that perform the work automatically and in the background. Unfortunately, CentOS does not package the ''jack-plumbing'' command, so one must either download the source code from the [[wikipedia:Debian_Linux|Debian]] website: [http://deb.debian.org/debian/pool/main/j/jack-tools/jack-tools_20131226.orig.tar.bz2 here] or [http://deb.debian.org/debian/pool/main/j/jack-tools/jack-tools_20131226-1.debian.tar.gz here] and compile it (the original source code for ''jack-plumbing'' seems to have been lost in the bit bucket), or choose a different &ldquo;plumbing&rdquo; tool to manage the JACK connections.
+The most reliable methods for making JACK connections are those that perform the work automatically and in the background. Unfortunately, CentOS does not package the ''jack-plumbing'' command, so one must either download the source code from the [[wikipedia:Debian_Linux|Debian]] website: [https://deb.debian.org/debian/pool/main/j/jack-tools/jack-tools_20131226.orig.tar.bz2 here] or [https://deb.debian.org/debian/pool/main/j/jack-tools/jack-tools_20131226-1.debian.tar.gz here] and compile it (the original source code for ''jack-plumbing'' seems to have been lost in the bit bucket), or choose a different &ldquo;plumbing&rdquo; tool to manage the JACK connections.
 Here is an example of a configuration file for ''jack-plumbing''. Note that the &ldquo;comment character&rdquo; is a semicolon (&ldquo;&#59;&rdquo;) rather than the more common hash symbol (&ldquo;&#35;&rdquo;). In general, the ''jack-plumbing'' '''''connect''''' statement format is <tt>(connect "source" "destination")</tt>.  If you place this in ''/etc/jack-plumbing'' you can start the app with simply ''/bin/jack-plumbing'' (see the figure above):

@@ Line 15: / Line 15: @@
 The other way to run JACK is in Promiscuous mode.  When ''jackd''(8) (the JACK daemon) is run in promiscuous mode then Rivendell can start jackd as ''root'' and as long as the logged in user is a member of the audio group, then any JACK processes run under the logged in user will also see the JACK server.  With Rivendell V3 accomplishing this requires a few minor modifications to configuration files.  With Rivendell V4 this is the default Jack behavior.
-=== Enabling Promiscuous Mode on Rivendell V3 ===
+== Enabling Promiscuous Mode on Rivendell V3 ==
 '''Note that this is NOT necessary if you are running Rivendell V4 as it defaults to run in promiscuous mode.  It is only needed with V3.'''

@@ Line 17: / Line 17: @@
 === Enabling Promiscuous Mode on Rivendell V3 ===
-'''Note that this is NOT necessary if you are running Rivendell V4.  It is only needed with V3.'''
+'''Note that this is NOT necessary if you are running Rivendell V4 as it defaults to run in promiscuous mode.  It is only needed with V3.'''
 Setting up promiscuous mode on Rivendell V3 requires the creation of an environment variable file, and adding that variable to Systemd's Rivendell.service file.

@@ Line 117: / Line 117: @@
 After configuring Rivendell to start the JACK subsystem, you probably need to also start some JACK clients. Do this by adding each one in the '''JACK Clients to Start''' section (see the figure above for examples).
 You might consider using the ''[https://github.com/opensourceradio/ram/blob/master/usr/local/bin/pmw-jack-setup pmw-jack-setup]'' script (or something like it) to configure your ALSA sound devices to work with JACK. This script accepts two parameters: the name of the ALSA device to configure, and the &ldquo;human-readable&rdquo; name you want to give the JACK client. You can learn your ALSA device names by running the command <tt>sudo aplay -l</tt> (or <tt>su - root -c 'aplay -l'</tt>) in a terminal window. Running this command results in output like:
@@ Line 141: / Line 143: @@
 As with <tt>/usr/local/bin/jackd-start</tt>, be sure to set the permissions on ''pmw-jack-setup'' with <tt>sudo chmod +x /usr/local/bin/pmw-jack-setup</tt>.
 ==== Connecting JACK Inputs and Outputs ====

@@ Line 56: / Line 56: @@
    usermod -a -G audio **user**
-where **user** is the logged in user.
+where **user** is the logged in user.  Once you have made the various changes the easiest way to ensure all the updates are picked up is to reboot the system.
 === Configuring Rivendell to use JACK ===

@@ Line 13: / Line 13: @@
 With Rivendell 3.x there are two ways to run JACK.  By default Rivendell processes and JACK processes must be run as the same user ID. And since Rivendell processes (in the packaged version available from [[Paravel Systems - USA|Paravel Systems]]) '''''always''''' run as ''root'', this means ''jackd''(8) (the JACK daemon) must also run as ''root''.
-The other way to run JACK is in Promiscuous mode.  When ''jackd''(8) (the JACK daemon) is run in promiscuous mode then Rivendell can start jackd as ''root'' and as long as the logged in user is a member of the audio group, then any JACK processes run under that user logged in user will also see the JACK server.  With Rivendell V3 accomplishing this requires a few minor modifications to configuration files.  With Rivendell V4 this is the default Jack behavior.
+The other way to run JACK is in Promiscuous mode.  When ''jackd''(8) (the JACK daemon) is run in promiscuous mode then Rivendell can start jackd as ''root'' and as long as the logged in user is a member of the audio group, then any JACK processes run under the logged in user will also see the JACK server.  With Rivendell V3 accomplishing this requires a few minor modifications to configuration files.  With Rivendell V4 this is the default Jack behavior.
 === Enabling Promiscuous Mode on Rivendell V3 ===

@@ Line 1: / Line 1: @@
 The [https://jackaudio.org/ Jack Audio Connection Kit] (JACK) is a suite of professional-grade, low-latency tools for routing digital audio.
-== Configure Rivendell 3 For Use With JACK ==
+== Configure Rivendell 3 or 4 For Use With JACK ==
 This has been confirmed to work with Rivendell 4 and Ubuntu 22.04.3 LTS - 2/1/24 kw

← Older revision		Revision as of 05:18, 11 February 2024
Line 14:		Line 14:

	The other way to run JACK is in Promiscuous mode. When ''jackd''(8) (the JACK daemon) is run in promiscuous mode then Rivendell can start jackd as ''root'' and as long as the logged in user is a member of the audio group, then any JACK processes run under that user logged in user will also see the JACK server. With Rivendell V3 accomplishing this requires a few minor modifications to configuration files. With Rivendell V4 this is the default Jack behavior.		The other way to run JACK is in Promiscuous mode. When ''jackd''(8) (the JACK daemon) is run in promiscuous mode then Rivendell can start jackd as ''root'' and as long as the logged in user is a member of the audio group, then any JACK processes run under that user logged in user will also see the JACK server. With Rivendell V3 accomplishing this requires a few minor modifications to configuration files. With Rivendell V4 this is the default Jack behavior.
		+
		+	=== Enabling Promiscuous Mode on Rivendell V3 ===
		+
		+	'''Note that this is NOT necessary if you are running Rivendell V4. It is only needed with V3.'''
		+
		+	Setting up promiscuous mode on Rivendell V3 requires the creation of an environment variable file, and adding that variable to Systemd's Rivendell.service file.
		+
		+	First create the following file:
		+
		+	sudo nano /etc/profile.d/rivendell-env.sh
		+
		+	And then copy / paste into the file:
		+	#
		+	# Run jackd(1) in promiscuous mode
		+	#
		+	export JACK_PROMISCUOUS_SERVER=audio
		+
		+	You also need to add a line to your rivendell.service file:
		+
		+	sudo nano /lib/systemd/system/rivendell.service
		+
		+	and add the line '''Environment=JACK_PROMISCUOUS_SERVER=audio''' to the '''[Service]''' section of the file:
		+
		+	[Service]
		+	LimitNOFILE=4096
		+	Type=simple
		+	ExecStart=/usr/local/sbin/rdservice
		+	PrivateTmp=false
		+	Restart=always
		+	RestartSec=2
		+	StartLimitInterval=120
		+	StartLimitBurst=50
		+	Environment=JACK_PROMISCUOUS_SERVER=audio
		+
		+	Save the file, and run a:
		+
		+	sudo systemctl daemon-reload
		+
		+	You will also need to make sure that the logged in user is part of the audio group. From a shell:
		+
		+	usermod -a -G audio user
		+
		+	where user is the logged in user.

	=== Configuring Rivendell to use JACK ===		=== Configuring Rivendell to use JACK ===