Talk:JACK Audio Connection Kit

What is that

Wow, looks like I'll start the discussion. That flow chart makes no sense at all. EvanR 08:04, 28 February 2006 (UTC)

Agreed. Also, once it is revised, I think it'd be a good idea for an image in place of text. Sam 23:21, 21 July 2006 (UTC)

I also have no idea what that chart means --MarSch 13:10, 9 October 2006 (UTC)

Net support GNU/Linux to Windows

Does anyone have references to info that would explain whether Jack supports playing audio applications on GNU/Linux to a remote Windows machine that has the actual speakers attached? 71.172.68.78 (talk) 10:16, 13 September 2009 (UTC)

Notability

Someone has put a notability tag on this article. This seems absurd to me. The notability guidelines for products include the following: "Information on products and services should generally be included in the article on the company itself". What company might that be, in the case of JACK? This is open-source software. There is no "company" involved.

In my opinion, JACK is notable, if only because it's almost impossible to do pro audio work in Linux without it. If we need more sources to establish notability, we should certainly be able to find them. SoCalDonF (talk) 01:09, 16 December 2009 (UTC)

I agree. In support of this, I added a mention of Paul Davis's 2004 Open Source Award for Jack (and a reference to the TechRepublic article). Thanks to Jack O'Quin on the linux audio mailing list for bringing the reference to my attention. Ndokos (talk) 01:08, 17 February 2010 (UTC)

I have added some citations (more are needed, but it's kind of hard to find quotable support for perceived consensus in an open-source culture), and removed the notability tag - this article has issues, but notability is clearly not one of them. JACK has been a key part of linux audio infrastructure for years. I have also tried to demonstrate its role in nudging Linus towards better real-time performance in the kernel.--Nettings (talk) 10:26, 17 February 2010 (UTC)

JACK1 no longer maintained

Please label this article for historical purposes only and create a new page. Consider deleting it as outdated and no longer relevant. JACK Audio Connection Kit is JACK1, which is no longer maintained. JACK2 has become JACK. From a 2020 README

"JACK2 is a C++ version of the JACK low-latency audio server for multi-processor machines. It is a new implementation of the JACK server core features that aims in removing some limitations of the JACK1 design.

"jack and jack1 are API compatible enough that applications can be built against either, and in fact most (possibly all?) apps can be built against one and run with the other with no problems.

"jack1 wasn't designed to benefit from multiple CPU cores/threads. It may (or may not) offer slightly better performance on single-core systems."

Base all references on https://jackaudio.org/

See: https://jackaudio.org/news/2017/12/21/jack2-v1-9-12-release-and-future-plans.html Hpfeil (talk) 14:23, 23 May 2020 (UTC)

Thanks for the reference, @Hpfeil:. I found this in particular useful: https://jackaudio.org/news/2017/12/21/jack2-v1-9-12-release-and-future-plans.html.

Rather than splitting into two articles, I've tried to do a sufficient job of covering both here. But as I'm no expert, please feel free to suggest or make further revisions and clarifications.★NealMcB★ (talk) 22:40, 20 August 2020 (UTC)

Adoption

Jack seems to be on the decline, particularly for cross-platform applications, and dispensed with or made optional by widely-used studio-ware like Ardour, LMMS, Carla. Connections are more capably handled than in the past by applications themselves, perhaps the article should reflect this. From around 2005-20015 Jack was reckoned the audio standard for Linux, now it's more legacy. Oldwes (talk) 16:45, 4 December 2024 (UTC)