Jack For Windows

[bsork]

if you want low latency change the buffer is easy

How do you do that? I have a setup that looks almost like your screenshot (I'm at work so I'm not 100% sure, but...), with the exception that I have Server Path = "jackdmp -S" (as stated as neccesary for Windows in one of the readme files), and I've tried to change the Frames/Periods to both 128 and 64 with the buffer size in my audio interface's control panel at the same values. Still the reported buffer size in Reason is 512 with a notable delay/latency. QJackCtl changes the reported latency in the setup window as I change Frames/Periods.

Is there some other value governing the latency?

[1barEnuff]

well..this answers my question: http://createdigitalmusic.com/2007/09/1 ... nd-now-pc/

thanks

john,

[wuschel]

Thank you... it works now. But ASIO latencies are too high. I much prefer ASIO4ALL. Thanks again

if you want low latency change the buffer is easy

This is the point where I feel the need to get my €0.02 in:

Jack is not a replacement for ASIO4ALL or any other ASIO driver for that matter. Jack routes audio (and, potentially, MIDI) back and forth between applications running on the same system, but in order to get audio in and out of same system physically, you still depend on the audio driver stack Jack builds upon.

Under Linux, that would be ALSA, obviously (can someone please educate me why I can select ALSA - along with CoreAudio - in the Windows build of Jack, BTW?)

Under Windows, it sits on top of PortAudio, a very fine OSS cross platform library that deals with audio i/o.

PortAudio itself, under Windows, sits on top of either MME, DirectSound, (Kernel Streaming?), or -> you guessed it -> ASIO!

So does Jack improve the latency of your audio interface? -> No!
This is not what Jack is all about. Under Linux, the latter would be the job of ALSA, not Jack, on the MAC, it would be CoreAudio, not Jack...

What Jack does is to provide you with a supposedly low overhead audio path between applications - like a virtual audio wire - while (in its Windows incarnation) posing as an ASIO driver.

[bsork]

I finally made Jack work almost ok on my laptop (HP nc630 Centrino Duo XP Pro), routing Reason's audio output through Usine.

In case this might help someone, here's what I ended up doing to get latency down and get the audio connections (semi-)automated, since it seems that QJackQtl doesn't do things correctly on Windows. I guess the sound card and/or ASIO driver might have something to do with the problems I've encountered as well.

To get the buffer size down from 512, I had to add a command line parameter when starting jackdmp. I start the Jack server using a shortcut on the desktop with target:

Code: Select all

C:\jackdmp\jackdmp.exe -d portaudio -d "M-Audio FW ASIO" -p 128

My first attempts with a lowered buffer size created an awful distortion when running Reason into Usine, but after fiddling around with parameters, I got it to sound ok. That is, I thought so until I started mousing around... Mouse clicks and screen updates creates very audible clicks. Not acceptable...

I never got the Patchbay definitions to work, but creating a BAT or CMD file to make the connections is quite simple. Here's my definitions after turning auto-connect off for both in- and outputs in the JackRouter.ini file:

Code: Select all

jack_connect UsineMain:out1 system:playback_1
jack_connect UsineMain:out2 system:playback_2
jack_connect UsineMain:out3 system:playback_3
jack_connect UsineMain:out4 system:playback_4
jack_connect system:capture_1 UsineMain:in1
jack_connect system:capture_2 UsineMain:in2
jack_connect system:capture_3 UsineMain:in3
jack_connect system:capture_4 UsineMain:in4
jack_connect Reason:out1 UsineMain:in5
jack_connect Reason:out2 UsineMain:in6
jack_connect Reason:out3 UsineMain:in7
jack_connect Reason:out4 UsineMain:in8

This connects Usine's ins and outs to the interface, and also routes four Reason outputs to separate inputs in Usine. It must be executed after starting up the two client programs.


Does anybody have a clou as to what can be done to avoid the mentioned clicks? I have tried quite a few combinations of command line parameters to no avail. The CPU is far from working overtime with the files I've used for testing, so that should not be any problem.

[carlosagv]

new version http://www.grame.fr/~letz/jackdmp_0.71.tgz

[fliffo]

www.grame.fr/~letz/jackdmp.html

new version... now it's jack2 version 1.9.0.
comes with an easy installer and needs microsoft visual c++ 2008 redistributable.

[publicradio]

Well shoot! I installed this, and it works on my laptop but not on my desktop. I need it for audio routing so that i can have multiple clients running with ASIO. So anyway, I went into audio settings in FL Studio and changed my audio device to Jackrouter... I didn't get any sound and now there's no way to change the device back. When I try to change it to something else the whole program freezes. I'm screwed! What should I do???

[bsork]

Have you tried to uninstall Jack? I don't know anything about FL Studio, but most programs would ask for an ASIO driver on startup if the previous assignment has disappeared.

[publicradio]

YEah that did it. I should have tried that before posting. Anyway thanks.

[publicradio]

Hey so, is this going to solve my long standing multi-client asio support issue? I really, really would like to just have FL studio open all the time so I could plink around on my MIDI keyboard while I'm looking at some music video on youtube or whatever... Is this essentially a multi-client solution, provided that it works correctly?

[carlosagv]

new version 1.90 http://www.grame.fr/~letz/jack-1.9.0.tgz