"Updated binaries coming soon" MacOS and Windows

[zardini123]

In the Downloads section of the JACK website, it states for MacOS and Windows "Updated binaries coming soon."

Why aren't the old binaries available to still download? Is there a specific reason to hold off providing a download for Windows and MacOS users until the update is available?

[falkTX]

See jackaudio/jack2#623 this was requested by users, because those binaries can cause problems.
I have reserved some time this year in october to finish up the final things needed to get the new binaries out, so an announcement is to come later.

[zardini123]

Gotcha. Is this hold-off of the downloads also related to how JackRouter doesn't show as an audio device on newer macOS versions? I see there is talk about JackRouter in that issue, but instead regarding Windows.

[falkTX]

There has been reports of JackRouter not working on the new macOS, but then some people say it works for them... so I dont know.

But anyway, I am not going to maintain JackRouter, so it wont be included in either macOS or Windows installers.
Anyone interested on it can create a new project and maintain it there.

[zardini123]

Oh, JackRouter/JackOSX is not maintained alongside JACK? Where is it maintained, then?

I think it'd be valuable information for future users to include the information on the website about how JackRouter is related to JACK, and where users can go to download it if they desire.

[falkTX]

Oh, JackRouter/JackOSX is not maintained alongside JACK? Where is it maintained, then?

It is part of JACK2 (so far as I know), but JACK changed maintainers. I do not know how JackRouter was developed, built or any such details, also dont really have a reason to use it.
It is fair to ask for details on where to get the source, if not in the jack2 repo then perhaps some parts are on old osxjack project.

I might be wrong here, but seems to me JackRouter has nothing in particular that needs direct access to JACK codebase. That is, it can perfectly fine be an external client, packaged separately for those that want it.

[zardini123]

So in other words, the stuff that will be included in the macOS and Windows installations is simply the command line utilities/backends? No frontend applications like JackRouter and jackctl?

I'm still sincerely confused about what's considered "dead" and therefore not to be included in releases. There is a JackRouter folder under windows in the jack2 repo, but not macosx in the develop branch.

[falkTX]

So in other words, the stuff that will be included in the macOS and Windows installations is simply the command line utilities/backends? No frontend applications like JackRouter and jackctl?

Kinda. the libraries, example clients and qjackctl will be included.
Just not JackRouter.

There is a JackRouter folder under windows in the jack2 repo, but not macosx in the develop branch.

Ah, then you need to use cvs to get the old macos related code.
See https://sourceforge.net/p/jackosx/code/

[zardini123]

Ah, then you need to use cvs to get the old macos related code.

Wow, it certainly must be old if it uses CVS for version control. "Last update 2012." Impressive. No wonder y'all aren't using it anymore.

Kinda. the libraries, example clients and qjackctl will be included.

I remember researching about doing inter-application realtime audio transfer in macOS awhile ago, and the biggest tip was using JACK to do so. Of course, connecting applications was using JackRouter. Does native JACK provide the ability for applications to attach to JACK simply due to JACK being exposed as a "virtual audio interface" (just like with JackRouter)?

[falkTX]

Does native JACK provide the ability for applications to attach to JACK simply due to JACK being exposed as a "virtual audio interface" (just like with JackRouter)?

applications need to implicitly support jack in order to talk to jack and the other jack applications.
it is possible to bridge other APIs into jack, and this is what jackrouter allows, but then these applications cannot talk to other jack applications (as much as a real "native" client can)

[zardini123]

applications need to implicitly support jack in order to talk to jack and the other jack applications.
it is possible to bridge other APIs into jack, and this is what jackrouter allows, but then these applications cannot talk to other jack applications (as much as a real "native" client can)

Gotcha, makes a lot of sense. Thank you for all the explanations. I hope some day the osxjack/jackrouter projects are reinitiated.

I certainly think providing disambiguation for JACK, osxjack, and jackrouter on the JACK website would be fantastic, either in the downloads or in the FAQ page.

[falkTX]

I certainly think providing disambiguation for JACK, osxjack, and jackrouter on the JACK website would be fantastic, either in the downloads or in the FAQ page.

I completely agree. will keep this in mind when it is time to release.

[dyfer]

Ah, then you need to use cvs to get the old macos related code.
See https://sourceforge.net/p/jackosx/code/

Some time ago I was inquiring about jackosx sources. @sletz has shared his latest files, supposedly matching with the last JackOSX release. I've put them up here, on top of source files mirrored from CVS: https://github.com/dyfer/jackosx/

As noted in the README, I'm not maintaining that code.