[Jack-Devel] JACK2 1.9.12 release and future plans

Filipe Coelho falktx at gmail.com
Thu Dec 21 17:32:03 CET 2017

A few days ago a new version of JACK2 was released.
You can grab the latest release source code at 
The official changelog is:
   - Fix Windows build issues
   - Fix build with gcc 7
   - Show hint when DBus device reservation fails
   - Add support for internal session files

If you did not know already, I am now maintaining JACK2 (and also JACK1).
So this latest release was brought to you by yours truly. ;)

The release was actually already tagged on the git repo quite some time 
ago, but I was waiting to see if Windows builds were possible.
I got side-tracked with other things and 1.9.12 ended up not being 
released for some time, until someone reminded me of it again... :)
There are still no updated macOS or Windows builds, but I did not want 
to delay the release further because of it.
The 1.9.11 release (without RC label) was skipped to avoid confusion 
with the versions.
So 1.9.12 is the latest release as of today. macOS and Windows binaries 
still use an older 1.9.11 version.

Being the maintainer of both JACK1 and JACK2 means I can (more or less) 
decide the future of JACK.
I believe a lot of people are interested to know the current plan.

First, JACK1 is in bug-fix mode only.
I want to keep it as the go-to reference implementation of JACK, but not 
add any new features to it.
The reason for this is to try to get JACK1 and JACK2 to share as much 
code as possible.
Currently JACK2 includes its own copy of JACK headers, examples and 
utilities, while JACK1 uses sub-repositories.
During the course of next year (that is, 2018) I want to get JACK2 to 
slowly use the same stuff JACK1 does, then switch to use the same 
repositories as submodules like JACK1 does.
This will reduce the differences between the 2 implementations, and make 
it a lot easier to contribute to the examples and utilities provided by 
(Not to mention the confusion caused by having utilities that work in 
simlar yet different ways)
We will keep JACK1 "frozen" until this is all done.

Second, but not least important, is to get the JACK1 specific features 
into JACK2.
A few things were added into JACK1 after JACk2 was created, that never 
made it into JACK2.
This includes meta-data (JACK2 does have the API, but a non-functional 
one) and the new internal clients.
The purpose is to reduce reasons users might have to switch/decide 
between JACK1 and JACK2.
JACK2 should have all features that JACK1 has, so that most users choose 

Now, you are probably getting the impression that the focus will be on 
JACK2, which is correct.
Though I realize some developers might prefer JACK1's design, the long 
"battle" of JACK1 and JACK2 needs to stop.
Development of new features will happen in the JACK2 codebase, and JACK1 
will slowly become legacy.
Well, this is my personal plan at least.

Not sure if this all can be done in 2018, but better to take things 
slowly and get things done than do nothing at all.
I will keep you updated on the progress through-out the year.
Happy holidays everyone!

More information about the Jackaudio mailing list