JACK update

Joey Cagle · 05-30-2007, 10:34 AM

Hey. Just wanted to post an update on my issues with JACK from the repository.

For those of you who remember from the previous board, I mentioned that I was having trouble getting JACK to start with the GUI on Grafpup 2 Beta. It just wouldn't start. I downloaded the one from dotpups.de, and it did just fine.

Well, I tried the repository version with my hard drive install of RC1, and no problem, it starts up just fine. So apparently that problem is fixed.

MensaWater · 05-31-2007, 07:35 AM

People have often told me this but I now realize its true:

I don't know JACK

Joey Cagle · 05-31-2007, 11:24 AM

JACK is a program that is required for much of the Linux audio programs, like Ardour or Rosegarden. Then some other programs, while it doesn't require it, it helps if you have JACK.

It allows for interoperability between Linux audio recording and MIDI applications.

Nathan F · 06-01-2007, 12:37 AM

It actually allows interoperability between all audio clients which are using the Jack server. So I can use Hydrogen to generate a rythm, then record that with Ardour, then process the resulting tracks by patching through JackRack. It's also supposed to be very low latency, meaning when you apply a change there should be no noticable lag.

I do have a question thoug, are you speaking of Qjackctl here? Because I don't know of any other gui. I just usually start jack manually from the command line if I need it, so I haven't tested Qjackctl much. It's actually pretty simple to do.

Code:

jackd -d alsa &

The "&" is important, because it allows the terminal to be used for something else entirely. If you wanted to you could insert that line into either .Xinitrc or .config/openbox/startup and the server would be running whenever you log in. It's been on my todo list for ages to expand the primitive session management so that you can decide which programs to start during login, with a graphical program. But I keep getting sidetracked (just like now).

I do seem to remember that when I installed Qjackctl I had to go into the settings and change a few things before it woul start up the server, but for the life of me I can't remember what they were.

Nathan

Joey Cagle · 06-01-2007, 12:14 PM

Quote:

Originally Posted by Nathan F

It actually allows interoperability between all audio clients which are using the Jack server. So I can use Hydrogen to generate a rythm, then record that with Ardour, then process the resulting tracks by patching through JackRack. It's also supposed to be very low latency, meaning when you apply a change there should be no noticable lag.

I do have a question thoug, are you speaking of Qjackctl here? Because I don't know of any other gui. I just usually start jack manually from the command line if I need it, so I haven't tested Qjackctl much. It's actually pretty simple to do.

Code:

jackd -d alsa &

The "&" is important, because it allows the terminal to be used for something else entirely. If you wanted to you could insert that line into either .Xinitrc or .config/openbox/startup and the server would be running whenever you log in. It's been on my todo list for ages to expand the primitive session management so that you can decide which programs to start during login, with a graphical program. But I keep getting sidetracked (just like now).

I do seem to remember that when I installed Qjackctl I had to go into the settings and change a few things before it woul start up the server, but for the life of me I can't remember what they were.

Nathan

Yeah, that's the GUI I'm speaking of.

Well, the important thing for me is that it starts now, so it's all good.

BTW, your description of Jack is probably better than mine. Sometimes I'm just not sure exactly how to explain what something is, haha.

I mainly use the GUI because I find it easier to manage the patchbay with that.