To be honest, I didn't try it myself. I just checked that it started using wine.

There are three problems with it:

1. It doesn't find the jackd.exe binary. I don't know how the path is handled
    in qjackctl under windows. Maybe the problem is that it was a 32 bit build
    of qjackctl and a 64 bit build of jack?
2. Scanning for the available pulseaudio drivers takes many seconds.
    qjackctl freezes while this happens.
3. When choosing the direct sound primary sound driver (in many 
    cases the most natural driver to try), jackd says (on one of my computers) that
    it can't start the driver because of illegal input and output arguments (I think).
    This information is written to the console. However, qjackctl just says in the
    messages window that it crashed, and doesn't show the information printed
    to the console. Perhaps it's not possible to redirect this information to the
    messages window?

On Sat, Jul 4, 2015 at 2:54 PM, Stéphane Letz <> wrote:
39 MO : with those 9 needed dll… ((-;

OK I will try it and possibly put it in new Windows package.


Le 4 juil. 2015 à 13:36, Kjetil Matheussen <> a écrit :

> 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:
> ...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 "" script)
> Windows binary:
> Perhaps this build, or something similar, can be included in the next release of jack for windows?
> _______________________________________________
> Jack-Devel mailing list