Hi,
Back in January/February at the start of this year, Paul announced that
he would be stepping down, and he requested that someone would stand for
being the new maintainer.
As far as I know, this didn't happen, up until Filipe Coelho(?) offered
to maintain JACK1. After speaking with Paul around March, he said that
once Ardour 5.0 was released he would do the final release of JACK1 and
then hand over maintainership.
There are a few pull requests on the GitHub, some of which are critical
to the core functionality of JACK1, like the patch for OSX which begins
to modernise JACK1's usages of the CoreAudio APIs (while still
maintaining backward compatibility).
I'd like to help the JACK community in getting OSX support
up-to-scratch. There is a promising project called CaptainJack
(https://github.com/Qix-/CaptainJack) which aims to be a modern
replacement for JackOSX, which is a vital part of the JACK ecosystem
within OSX. While it is just a start, it shows there is at least some
interest.
My question to the community is: Should an effort be put in to revive JACK1?
And to Paul; I know it's only been a little over a month since 5.0 was
released, but is it possible you could do this 'final release' of JACK1
soon so we can get the ball rolling again, or at least give some sort of
time-frame on when this can be achieved.
I personally think there should be an effort, the main issue at this
time is how the clients are sorted, and there is a patch for this. I
would be willing to step forward to fix all the issues related to OSX,
and reattempt integration of Fons' topological sort patch. In addition
to this, JACK1 is a good code-base, albeit slightly outdated, which
makes a great reference implementation for JACK3.
--
Josh
Hi,
I found some extremely useful stuff and it was a real discovery for me, just give it a try! You may find more information here <http://spoquizugu.comicbooktheatre.com/e4eor>
me
Forwarding to Jack-devel (it was a direct reply to me, but I can't do
anything with it at this stage).
-------- Forwarded Message --------
Subject: Re: [Jack-Devel] Negative xruns
Date: Fri, 9 Sep 2016 12:11:01 +0200
From: Miroslav Urbanek <mu(a)miroslavurbanek.com>
To: Josh de Kock <josh(a)itanimul.li>
Here you go.
MU
Hi,
I wonder how you normally handle the situation when the
program exits abnormally (for instance if the user kills a client)
while freewheeling.
I'm not so interested in detecting this when it happens, but
I want to handle it somewhat gracefully when my program
is started again. I.e. I don't want the program not producing
any sound and not informing that something is wrong.
As far as I can see, there is no function to check whether
jack is currently freewheeling (or is there?). So are there any
potential problems just calling "jack_set_freewheel(g_jack_client, 1)"
during program startup? (i.e. whether we are freewheeling or not)
Maybe I have misunderstood how things work, or I'm using too old
version of jack, but here's what happens:
1. Start jack 2 (jack-audio-connection-kit-devel-1.9.9.5-1.fc17.x86_64)
2. Press the "Start transport rolling" button in qjackctl.
3. Qjackctl reports "Rolling" in the display.
4. Create jack client
5. Call jack_transport_query(client, NULL).
6. jack_transport_query(client, NULL) always returns JackTransportStopped
Shouldn't jack_transport_query(client, NULL) return JackTransportRolling?
(It doesn't matter whether I activate the client or not before calling
jack_transport_query(client, NULL)).