JACK2 1.9.12 release and future plans

Discuss anything new and newsworthy! See http://planet.linuxaudio.org for more Linux Audio News!

Announcements of proprietary software may fit better in the Marketplace.

Moderators: raboof, khz, MattKingUSA

User avatar
falkTX
Established Member
Posts: 6646
Joined: Sat Jan 09, 2010 3:04 pm

JACK2 1.9.12 release and future plans

Postby falkTX » Thu Dec 21, 2017 4:30 pm

A few days ago a new version of JACK2 was released.
You can grab the latest release source code at https://github.com/jackaudio/jack2/releases.
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 JACK.
(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 JACK2.

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!

User avatar
magicalex
Established Member
Posts: 174
Joined: Sun Jan 24, 2016 6:34 pm
Contact:

Re: JACK2 1.9.12 release and future plans

Postby magicalex » Thu Dec 21, 2017 5:04 pm

Happy holidays to you too and thank you for your tireless work improving Linux audio for us!
My name is Sandy and I sing songs: SandySingsSongs.com

Luc
Established Member
Posts: 741
Joined: Fri Mar 27, 2015 1:04 pm

Re: JACK2 1.9.12 release and future plans

Postby Luc » Thu Dec 21, 2017 8:27 pm

So JACK1 has more features than JACK2?

I never thought that JACK2 could be much better than what it already is. JACK2 nowadays makes me wonder how anyone who makes music on the computer can ever live without it.

This roadmap sounds interesting and exciting.

Thank you for your invaluable work, falkTX!

tseaver
Established Member
Posts: 23
Joined: Mon Mar 13, 2017 6:07 am

Re: JACK2 1.9.12 release and future plans

Postby tseaver » Thu Dec 21, 2017 8:35 pm

Thank you for your many labors, falkTX: I know from personal experience how much pain and effort goes into being the maintainer of multiple FLOSS projects.
Ubuntu, Mixbus32C; acoustic blues / country / jazz

User avatar
sysrqer
Established Member
Posts: 1797
Joined: Thu Nov 14, 2013 11:47 pm
Contact:

Re: JACK2 1.9.12 release and future plans

Postby sysrqer » Thu Dec 21, 2017 9:21 pm

Nice one falktx, your plan sounds very sensible.

I hope one day the version numbering can be addressed, from a layman's point of view it's always been puzzling why jack 1 and 2 both are 1.x.

Jack Winter
Established Member
Posts: 376
Joined: Sun May 28, 2017 3:52 pm

Re: JACK2 1.9.12 release and future plans

Postby Jack Winter » Thu Dec 21, 2017 9:34 pm

JACK1 is at 0.125.0 ;)
Reaper/KDE/Archlinux. i7-2600k/16GB + i7-4700HQ/16GB, RME Multiface/Babyface, Behringer X32, WA273-EQ, 2 x WA-412, ADL-600, Tegeler TRC, etc 8) For REAPER on Linux information: https://wiki.cockos.com/wiki/index.php/REAPER_for_Linux

User avatar
sysrqer
Established Member
Posts: 1797
Joined: Thu Nov 14, 2013 11:47 pm
Contact:

Re: JACK2 1.9.12 release and future plans

Postby sysrqer » Thu Dec 21, 2017 10:20 pm

Jack Winter wrote:JACK1 is at 0.125.0 ;)

oh well, yeah, that kind of reinforces my point, even more confusing then.

ufug
Established Member
Posts: 387
Joined: Tue Jan 10, 2012 12:28 am

Re: JACK2 1.9.12 release and future plans

Postby ufug » Thu Dec 21, 2017 11:37 pm

I had no idea you did all this, falkTX. I am so grateful for your work. If it wasn't for the projects you've built (and maintain) many of us would not be able to work effectively on Linux. Thank you. :D

Thank you and I wish you an excellent 2018!

superprick
Established Member
Posts: 112
Joined: Fri Dec 28, 2012 10:47 pm

Re: JACK2 1.9.12 release and future plans

Postby superprick » Fri Dec 22, 2017 12:38 am

is there anyone working on incorporating AVB into Jack. It is an open standard

stanlea
Established Member
Posts: 550
Joined: Wed Apr 25, 2012 9:49 pm

Re: JACK2 1.9.12 release and future plans

Postby stanlea » Fri Dec 22, 2017 9:44 pm

superprick wrote:is there anyone working on incorporating AVB into Jack. It is an open standard


I think that AVB must be incorporated in the kernel.

dsreyes1014
Established Member
Posts: 166
Joined: Mon Dec 24, 2012 1:42 pm

Re: JACK2 1.9.12 release and future plans

Postby dsreyes1014 » Fri Dec 22, 2017 10:09 pm

superprick wrote:is there anyone working on incorporating AVB into Jack. It is an open standard


There was an attempt to add it it to kernel i believe but it has gone nowhere. I'd welcome this as my MOTU Ultralite AVB works really good through USB already. It would be icing on the cake.

simonvanderveldt
Established Member
Posts: 37
Joined: Mon Sep 04, 2017 9:30 pm

Re: JACK2 1.9.12 release and future plans

Postby simonvanderveldt » Sun Dec 24, 2017 12:33 pm

@falktx thanks for the update and your never ending contributions to the Linux audio ecosystem! Really appreciated!
And enjoy the holidays! :)

Also really like it that finally there's a direction for JACK and like it even more that it is to bring them together.

falkTX wrote:This includes meta-data (JACK2 does have the API, but a non-functional one) and the new internal clients.

Does this mean integration of something like "a2jmidid" into JACK?
I'm interested in why this was done for JACK1. Never really understood why it was integrated into JACK1. Is it technically better to do it within JACK vs in a separate piece of software? And what does it offer over just directly making using of ALSA seq (or raw for that matter)?

A totally different question: Is OSC support something that you're considering (for some point in the future)?

User avatar
falkTX
Established Member
Posts: 6646
Joined: Sat Jan 09, 2010 3:04 pm

Re: JACK2 1.9.12 release and future plans

Postby falkTX » Sun Dec 24, 2017 3:52 pm

aaahaaap wrote:
falkTX wrote:This includes meta-data (JACK2 does have the API, but a non-functional one) and the new internal clients.

Does this mean integration of something like "a2jmidid" into JACK?
I'm interested in why this was done for JACK1. Never really understood why it was integrated into JACK1. Is it technically better to do it within JACK vs in a separate piece of software? And what does it offer over just directly making using of ALSA seq (or raw for that matter)?

It was done in jack1 as a direct way to handle internal clients right when jackd starts. Also jack1 raw and seq alsa midi modes are not that great, a2jmidid is way better.
Also it integrated zita-a2j/j2a code, which means starting jack with several audio interfaces at the same time. (though of course only one of them would be "master" and fully in sync).

And regarding doing this in JACK directly vs separate tool, I think for obvious reasons it's better to have it integrated into jack itself.
Only 1 thing to start instead of several things.

aaahaaap wrote:A totally different question: Is OSC support something that you're considering (for some point in the future)?

There's already OSC in jack, done via special MIDI messages. See https://github.com/ventosus/jack_osc
With meta-data working for JACK2, we'll be able to have this seamlessly. Not the perfect solution, but works.


Return to “Linux Music News”

Who is online

Users browsing this forum: No registered users and 2 guests