The build of qjackctl included with jackdmp for windows is getting really
The biggest problem is that the default "startup time" is set too low,
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
...I've cloned the official qjackctl repository, fixed these two problems,
and added some files to make it straight forward to build qjackctl under
(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?
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,
I'm wondering whether it's safe to do non-blocking reads or writes from
inside the process callback.
From what I've seen, non-blocking I/O doesn't cause the process to go
into blocked state, and the realtime scheduler should not switch to
another process. But the documentation doesn't seem to allow them:
> [...] it cannot call functions that might block for a long time. This
> includes all I/O functions (disk, TTY, network), [...]
So, is it safe to use non-blocking I/O in the process callback?
Simple question about JACK that I haven't been able to find anywhere else.
Hoping someone here's kind enough to set me straight. :)
Coming from PulseAudio, I noticed that JACK's documentation and discussions
seem to barely mention things regarding channels....but do refer to ports
often. So I was wondering what kind of mapping there is between say L and R
channels and JACK ports? Or does a mapping even exists?
is the build for Mac OS X currently maintained? Where are the
most up-to-date build instructions to be found? I see there's a
waf wscript set up in the macosx folder, but there's also the
XCode project. Which one is the 'official' way to build, which
one would you prefer to have fixed if I dig into this (neither
works out of the box)?