Skip to content

Commit

Permalink
jack-example-tools release 1
Browse files Browse the repository at this point in the history
Signed-off-by: falkTX <[email protected]>
  • Loading branch information
falkTX committed Jan 15, 2022
1 parent 638a5ee commit 3177f8c
Showing 1 changed file with 22 additions and 0 deletions.
22 changes: 22 additions & 0 deletions _posts/2022-01-15-jack-example-tools-release-1.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
---
title: "jack-example-tools release 1"
author: "falkTX"
date: "2022-01-15T17:40:48+0000"
---
After years of them seeing no changes, the JACK2 example clients and tools have finally been synced with JACK1.
We only needed [PipeWire](https://pipewire.org/) to come along and force us to do it. :)
I mentioned the need to merge/sync the JACK1 and JACK2 headers and tools
[quite some months ago](https://jackaudio.org/news/2020/10/15/jack2-v1915-release-and-current-status.html),
but there wasn't much progress on that until very recently.

For an explanation, Linux distributions like Arch that do not typically split packages (hypothetically)
installing `pipewire-jack` would remove `jack2` and replace it with PipeWire's version.
But tools like `jack_connect`, `jack_wait`, etc are part of the `jack2` package, not `pipewire-jack`.
Installing `pipewire-jack` would (hypothetically) remove these tools.
There are quite a few set ups out there that rely on them, so a solution was needed for this.

David Runge has started the effort of splitting these tools from the JACK repositories into a new one.
The idea is that JACK will no longer ship with them, and they become an extra set of tools to install separately.
This allows to switch between JACK versions (JACK1, JACK2 or PipeWire) and keep the same exact set of tools.

You can find these tools in the [jack-example-tools](https://github.com/jackaudio/jack-example-tools) repository.

0 comments on commit 3177f8c

Please sign in to comment.