Hi all,
The build of qjackctl included with jackdmp for windows is getting really
old.
The biggest problem is that the default "startup time" is set too low,
making it
seem like "jack crashes". (I"ve got many complains that "jack crashes").
Another problem is that you manually have to append "-S" to the "Server
Prefix".
So here:
https://github.com/kmatheussen/qjackctl
...I've cloned the official qjackctl repository, fixed these two problems,
and added some files to make it straight forward to build qjackctl under
mingw32.
(Building is just running the "build_mingw32.sh" script)
Windows binary: http://folk.uio.no/~ksvalast/qjackctl.zip
Perhaps this build, or something similar, can be included in the next
release of jack for windows?
Sometime in the next two weeks, I will find the time to deal with a variety
of pull requests for JACK 1, update some articles on jackaudio.org (notably
FAQ stuff), and do a new release of JACK 1.
This will be my last work on JACK. The time has come for me to step down
from my role as "benign dictator (and jack1 maintainer)". There several
reasons for this:
* most linux distributions use JACK2 as their default, so JACK1's
relevance has diminished. I
still believe JACK1 to be a superior choice from some technical
perspectives, but there is
no doubt that JACK2's integration with dbus and thus its
interoperability with PulseAudio
has made this the safe and simpler choice for Linux.
* I really don't have the time to even think about things related to JACK
these days. It does
any future development a disservice to have me as the bottleneck, which
I effectively am
at the moment.
* Because 110% of my time is spent on Ardour, the fact that Ardour now has
non-JACK
audio/MIDI I/O options has diminished the significance of JACK for my
own work.
* as the years have gone on, although I am still delighted by the
technical quality and
the conception of JACK, I no longer think that it is a particularly good
idea for most users. There
are times when it is useful
I will continue to pay for the hosting of jackaudio.org (even though JACK2
continues to be distributed, managed and communicated about via other
channels), although if someone wanted to migrate this to some other more
communitarian platform, we could look into that.
I would be happy if someone volunteered to step up as maintainer of JACK1.
It would obviously be even better if someone was willing to take the big
leap to JACK3, a version that combines all the best parts of JACK1 and
JACK2, but I think it is more realistic to accept at this point that this
is not going to happen.
If nobody does step up, then there is a good chance that JACK1 will become
officially unmaintained. This isn't of much consequence, because once the
latest pull requests are merged, there won't be any known bugs in the code,
and also because not many people use it anymore. This also means, of
course, that "maintainer" is not much of a task, should someone feel
hesitant about taking it on.
--p
+ jack-devel
pls see question for Paul below.
On Sat, Jan 30, 2016 at 8:48 AM Benjamin Schmaus <benjamin.schmaus(a)gmail.com>
wrote:
> as the years have gone on, although I am still delighted by the technical
> quality and
> the conception of JACK, I no longer think that it is a particularly
> good idea for most users. There
> are times when it is useful
>
> Could you elaborate on this? Curious to know more.
>
> On Sat, Jan 30, 2016 at 8:39 AM Joakim Hernberg <jhernberg(a)alchemy.lu>
> wrote:
>
>> On Sat, 30 Jan 2016 11:13:06 -0500
>> Paul Davis <paul(a)linuxaudiosystems.com> wrote:
>>
>> > This will be my last work on JACK. The time has come for me to step
>> > down from my role as "benign dictator (and jack1 maintainer)". There
>> > several reasons for this:
>>
>> Sorry to hear about that (as a jack1 user). I thank you for all your
>> work and wish you all the best with future endeavors!
>>
>>
>> --
>>
>> Joakim
>> _______________________________________________
>> Jack-Devel mailing list
>> Jack-Devel(a)lists.jackaudio.org
>> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>>
>
Hey,
I was wondering, seeing as the latest distributed compiled package (on http://jackaudio.org/downloads/) for osx is version 0.90, and it is stated as beeing for Snow Leopard ; was wondering if i should try to compile it myself from the 1.9.10 tarball (or even the git repos ?) ; because i'm not very knowledgeable in coding so i'm afraid i have no idea how to compile it. Opening the xcode project in the git repo, then trying to compile it ; leads very fast to a critical " 'aften/aften.h' file not found" error ; and i don't see a "aften" file in the distribution.
In short, i do'nt know how stable is the 1.9.10 or Github version, but i'm not sure it is very wise either to use the maybe outdated 0.9 ? but for now, i don't know how i could do else...
Thanks in advance,
Victor
