Jack Audio Configuration

[Debutante]

HOW THE f**k DO YOU CONFIGURE THIS SHITE!!!!

Simple to use my ass. Patchmix is simple to use.

First Problem - I'd ,like it to work. Period. Just getting it going with FL has been a nightmare. I can choose JackRouter as my sound device (not interested in using my own asio ATM, just this thing or Windows drivers) after that nothing. Anyone have a pic of their setting page that I can see just - how to get this program going with FL at sampling rate 96?????

http://sourceforge.net/apps/mediawiki/j ... in_Windows

I saw this one and it was shite.

The connections page is pretty straight forward, but how can I get JACK to ouput audio with FL - and be able to use Jacks transport functions?

Then later how do you network?

[deastman]

I've been struggling with this for months, trying to get it to work right with the internal soundcard on my win7x64 laptop. No luck...

[jeffh]

Well, whenever Jack doesn't work 100% properly on Linux (which is 75-99% of the time for anyone who isn't L337), Jack's developers and apologists always blame the ALSA drivers, or whatever other convenient scapegoat there is for the given situation... It's good to know that it's equally a turd on Windows with official OEM drivers, ROFL...

..and then they talk about JACK for the iPad like it's some killer app... as if the iPad has nearly enough CPU horsepower to do anything useful other than remote-control a DAW running on PC hardware...

but from a reliability standpoint, you're better off running a real physical cable from your soundcard Outs to your soundcard Ins (assuming you have more than 2 Ins/Outs) just to make a small number of connections...

But if you start getting into a Jack-centric workflow where you are making many connections as part of your normal production process, you'll find that Jack offers all of the disadvantages of hardware, with none of the advantages of software... Suddenly saving your work becomes a multi-step error-prone ordeal. It's the 80s hardware-only studio all over again where you just leave the whole studio running day-and-night until the song is finished because you're bound to lose some of your work when you start turning things off...

Yours Truly,
**the int3rw3bz legendary anti-Jack crusader mega-troll**

[Debutante]

RIGHT

That's all the confirmation I need.

Good riddance to this shite. I've never harshly bitched about the unusability of a piece of software before, but f**k this. Please excuse the polarity, but this app filled me with so much false hope: a SIMPLE synchronous LAN transport system - my personal Shangrila. Cubase's Systemlink can be jittery sometimes.

At least I'm not crazy. I know my puter shit-ish, no noob, and I couldn't figure out what was wrong. People bitched about E-mus Patchmix, and when I got it I thought it was a cinch. "Match sample rates, choose buffer size and go"??? NOOOOT!

It's completely ridiculous. I literally wasted an entire Saturday on this crap. Didn't go out or anything waste Saturday.

I'm uninstalling it and deleting the downloaded app with Spybot's Secure Shredder just to thoroughly freakin' woodchip this crap - for my feelings, you see...

TA!

[CTStump]

Where were you guy's when this thread came up, I tried it and here was my response:

http://www.kvraudio.com/forum/viewtopic ... t=#5348329

And this was this apologist's reply:

http://www.kvraudio.com/forum/viewtopic ... t=#5348425

I don't understand the "Linux is great" mentality of these yeahoo's and their nerd fantasy.

p.s. I should mention that Bitwig has decided to use this INSTEAD of Rewire, go figure.

[wasi]

From the enclosed readme (so named), which is installed along with Jack when you double click the installer:

=============================================
QJACKCTL on Windows
=============================================

This is a latest version of Rui Nuno Capela QJACKCTL application (http://qjackctl.sourceforge.net/) compiled on Windows.
It is compiled from the latest CVS version which is using QT4 framework. To uses it:

- start qjackctl.exe and configure it the following way:

- in Setup/Setting, use "jackd -S" at the "Server Path" item. WARNING: on Windows the "-S" parameter is *mandatory* to have the jack server correctly working!!

- in Setup/Setting, use "portaudio" at the "Driver" item

- in Setup/Misc, check the "Start JACK audio server at application startup" box

- quit QJACKCTL and start is again, it should now launch the jack server. Quitting QJACKCTL will now close the jack server.

Starting the jack server with another audio device installed on the machine (like an ASIO card) can now be done directly in QJACKCTL.
A ">" button at the right of the interface button allows to list the name of all available devices, driven either by "MME", "DirectSound", or "ASIO".
Alternatively using the following command allows to display the names of available devices:

- jackd -d portaudio -l to display the entire list of available audio devices. (jackd -d portaudio -h will display all portaudio driver features)

Then start jackd with the device you want, by using its name, for example:

- jackd -R -S -d portaudio -d "ASIO::MOTU Audio ASIO", then start QJACKCTL. QJACKCTL will see the jackd server already running and then can be used normally.


=============================================
Jack MIDI
=============================================

A first version of a JACK MIDI <==> Windows MIDI bridge (using Windows MME API) is available.
If can be activated using the -X parameter in jackd command line. So add "-X winmme" in QJACKCTL settings (something like "jackd -S -X winmme").
The WinMME driver will scan MIDI input/output ports, open corresponding JACK MIDI ports and convert MIDI in/out into JACK MIDI messages.
QJACKCTL MIDI connection windows can then be used.


=============================================
JackRouter JACK/ASIO driver
=============================================

JackRouter is an ASIO driver that allows any ASIO compatible application to become a JACK client, thus exchange audio with any other "native" or "Jackified" application. This driver is registered in the system by the installer and becomes available in the list of ASIO drivers when the JACK server is running. A "JackRouter.ini" configuration file allows the application to configure how the JackRouter driver behaves.

- [IO]:
- input/output : the application can obtain any number if JACK input/output ports (not necessarily equal to the audio card input/output number). [Note that some applications force their input/output channel number].
- float-sample : be default the JackRouter will present audio samples in integer format for the application. Use float-sample=1 so that audio samples are presented in float format for the application (thus saving float/integer conversion time).


- [AUTO_CONNECT] :
- input/output : when 1, the application JACK port will automatically be connected to the machine input/output JACK ports.
- alias : with ASIO drivers, real channels names will be associated to the JACK port as aliases and will be returned when the application request channels names.

The short version is double click on the installer, run qjackctl and add -S. You dont configure anything else at all.

Ignore the website, it's obsolete.

Can I hear an AAAMEN!

[wasi]

On windows, check the exe's permissions. Everything that is not official Microsoft cleared has issues because UAC messes it up. That is not Jack's fault, I have it with everything from Image Line, through NI to Ableton stuff. It just seemingly randomly doesn't allow stuff and you have to go in and set it manually. Right click --> "Security". It sucks, but it's a Windows issue. Seems much worse with win8 too. At least for me.

[UltraJv]

Why not use VAS :

http://www.virtualaudiostream.com/

[CTStump]

From the enclosed readme (so named), which is installed along with Jack when you double click the installer:

=============================================
QJACKCTL on Windows
=============================================

This is a latest version of Rui Nuno Capela QJACKCTL application (http://qjackctl.sourceforge.net/) compiled on Windows.
It is compiled from the latest CVS version which is using QT4 framework. To uses it:

- start qjackctl.exe and configure it the following way:

- in Setup/Setting, use "jackd -S" at the "Server Path" item. WARNING: on Windows the "-S" parameter is *mandatory* to have the jack server correctly working!!

- in Setup/Setting, use "portaudio" at the "Driver" item

- in Setup/Misc, check the "Start JACK audio server at application startup" box

- quit QJACKCTL and start is again, it should now launch the jack server. Quitting QJACKCTL will now close the jack server.

Starting the jack server with another audio device installed on the machine (like an ASIO card) can now be done directly in QJACKCTL.
A ">" button at the right of the interface button allows to list the name of all available devices, driven either by "MME", "DirectSound", or "ASIO".
Alternatively using the following command allows to display the names of available devices:

- jackd -d portaudio -l to display the entire list of available audio devices. (jackd -d portaudio -h will display all portaudio driver features)

Then start jackd with the device you want, by using its name, for example:

- jackd -R -S -d portaudio -d "ASIO::MOTU Audio ASIO", then start QJACKCTL. QJACKCTL will see the jackd server already running and then can be used normally.


=============================================
Jack MIDI
=============================================

A first version of a JACK MIDI <==> Windows MIDI bridge (using Windows MME API) is available.
If can be activated using the -X parameter in jackd command line. So add "-X winmme" in QJACKCTL settings (something like "jackd -S -X winmme").
The WinMME driver will scan MIDI input/output ports, open corresponding JACK MIDI ports and convert MIDI in/out into JACK MIDI messages.
QJACKCTL MIDI connection windows can then be used.


=============================================
JackRouter JACK/ASIO driver
=============================================

JackRouter is an ASIO driver that allows any ASIO compatible application to become a JACK client, thus exchange audio with any other "native" or "Jackified" application. This driver is registered in the system by the installer and becomes available in the list of ASIO drivers when the JACK server is running. A "JackRouter.ini" configuration file allows the application to configure how the JackRouter driver behaves.

- [IO]:
- input/output : the application can obtain any number if JACK input/output ports (not necessarily equal to the audio card input/output number). [Note that some applications force their input/output channel number].
- float-sample : be default the JackRouter will present audio samples in integer format for the application. Use float-sample=1 so that audio samples are presented in float format for the application (thus saving float/integer conversion time).


- [AUTO_CONNECT] :
- input/output : when 1, the application JACK port will automatically be connected to the machine input/output JACK ports.
- alias : with ASIO drivers, real channels names will be associated to the JACK port as aliases and will be returned when the application request channels names.

The short version is double click on the installer, run qjackctl and add -S. You dont configure anything else at all.

Ignore the website, it's obsolete.

Can I hear an AAAMEN!

Duuuuuuuuude, THIS DOES NOT WORK!!!!!!(at least for me and probably most others)

All that does is default to the windows sound registry which is either the motherboard audio or stereo WDM/WASAPI drivers, NOT THE ASiO DRIVER in an external sound card!!!!, you still have to use to old method of NAMING THE ASIO DRIVER in order to set that up.

Also the "-X winmme" suffix WILL not read external MIDI drivers EITHER.

EVERYTIME your suggested use of the README is tried it CRASHS, in my opinion IT SUCK's BIG TIME

[chk071]

Well, whenever Jack doesn't work 100% properly on Linux (which is 75-99% of the time for anyone who isn't L337), Jack's developers and apologists always blame the ALSA drivers, or whatever other convenient scapegoat there is for the given situation... It's good to know that it's equally a turd on Windows with official OEM drivers, ROFL...

Sounds like the linux guys who always complain about bad drivers support for hardware like graphics cards and stuff like that. I'm happy that someone who develops for linux brings this up btw. Hopefully some change of mind occurs one day, and the linux guys get their shit right, seriously. I know, harsh words, but i experienced much shit in the linux world...

[wasi]

CTStump, are you selecting your soundcard in settings via the '>' and did you check permissions? If running as admin fixes it, it's a permissions issue. I had one install that didn't work because QJackCtl didn't get the appropriate permissions.

[CTStump]

CTStump, are you selecting your soundcard in settings via the '>' and did you check permissions? If running as admin fixes it, it's a permissions issue. I had one install that didn't work because QJackCtl didn't get the appropriate permissions.

This might be a good time to calm this debate.

I have my UAC permissions off, always have, also I did get the ASIO Drivers to show the first time doing it the old way of setting up the target in the short cut With the suffix changed in -d to my named ASIO driver which took quite a while to find and never showed in the drop down or with your suggested method(> drop down in the Qjackctl panel, which by the way crashed every time when I started jack after configuration). I still haven't been able to set up MIDI. I tried to give it the benefit of the doubt but as I said it failed BIG TIME.

My whole point has been that IT IS NOT an easy process and if it frustrates me IT WILL frustrate others with less patience(or knowledge of their system). It so reminds of those days long ago setting up Linux for sound which was a nightmare and god help you if you had to mess with an Nvidia card(early 2000). To me that is not a "NEW" way of doing things.

I'm going to leave it at that for now and go on stand by to cool things down.

[LawrenceF]

A timely thread since I'll very likely be having a look at Ardour 3 on OSX later tonight.

It was pretty automatic on Win with MixBus but I think OSX it requires a little config, not sure.

[jeffh]

Sounds like the linux guys who always complain about bad drivers support for hardware like graphics cards and stuff like that.

Frankly, the Linux driver situation has never been better(especially for soundcards), it's come a long way in the past 5 years... Unfortunately, there's quite a few developers who immediately try to deflect any blame for their software not working to drivers because "you know, Linux drivers suck" nearly everytime there's a problem... Jack possibly being the biggest offender of all here...

I'm happy that someone who develops for linux brings this up btw. Hopefully some change of mind occurs one day, and the linux guys get their shit right, seriously.

The problem with Jack in Linux is that people think it's a "low latency audio system" AND a "connection kit". No, it is NOT a "low latency audio system", it is JUST a "connection kit". It attempts to make a connection to ALSA and configure it for low-latency, and then it begs and pleads for you to install a Linux kernel with experimental real-time thread pre-emption settings that bork most PCs(ie: ALSA is a low-latency audio system, not Jack)... You know, shit that Windows and OSX developers **somehow** manage to solve at the application level without exotic OS kernel settings... So what you're getting is ALSA, but with many new bugs layered on top of it, in exchange for a woefully incomplete routing protocol that is being used just like a host/plugin architecture most of the time, but with far more overhead...

That's actually on my short-list of things to do now... I'm going to rework my threading/scheduling/buffering with the same "cheats" that Windows and Mac devs use to achieve "OMG 16 SAMPLEZ/0.001MS OF LATENCY" running atop a normal OS configuration. Not even because I'm of the opinion that most people need stupidly-low latency, mostly because I'd just like to prove once and for all that the way Linux developers have been approaching audio for the last 15 years is just stupid, and that they could learn a thing or two from how Windows developers do things...

I know, harsh words, but i experienced much shit in the linux world...

Yeah, this is the usual n00b->community interaction when attempting to use Linux audio:

n00b: Jack doesn't work, this sucks
community: You're doing it wrong, plz post the output of these 20 terminal commands, and change these 30 settings and you'll be fine

n00b: Application X can't do function Y that my Windows DAW does
community: You don't need function Y, and if you're producing genre Z that requires it, you shouldn't be producing genre Z because it's not real music. May I suggest switching to classic rock as a genre?

n00b: Having to connect 20 different applications in Jack is cumbersome compared to monolithic Windows DAWs
community: You're just not L337 enough to properly understand the "power" of Linux audio

[chk071]

Hehehe, sounds familiar. Even though one has to admit that it has gotten a hell of a lot better with the years... nowadays i don't even have to hack into the console in 99,9% of the cases. Thus said, i chose hardware which is supposed to work out of the box though, also the hardware compatibility has gotten much better, though. It seems the audio stuff is mostly still in the children shoe's, and will probably stay there, as development for linux always has been slow, due to the natural reasons, people doing free open source software in their free time, few dev's, few people who use it. Well, well, well...