You are not logged in.
I'm trying to set up JACK (or JACK2) on my system, and according to the wiki page I currently have jack2 installed, and alsa-plugins. Also, my .asoundrc matches the one in the wiki.
(also I took the freedom to edit the wiki, i.e. to remove the information about the non-existant AUR package, and write how to install jack2 package from [community]).
Currently I'm using a script that runs in my pre-KDE startup, which contains the following:
jack_control start #starts the jack server
jack_control ds alsa #selects alsa as the driver (backend)
jack_control eps realtime True #set engine parameters, such as realtime
jack_control dps period 256 #set the driver parameter period to 256
However, I'm obviously either missing something or doing something wrong.
Firstly, when I start qjackctl, I get the following output in the "Messages/Status" window:
12:38:45.769 Patchbay deactivated.
12:38:46.161 Statistics reset.
12:38:46.163 ALSA connection change.
12:38:46.175 D-BUS: Service is available (org.jackaudio.service aka jackdbus).
12:38:46.197 JACK connection change.
12:38:46.287 Client activated.
Cannot lock down memory area (Cannot allocate memory)
Thu Dec 2 12:38:46 2010: New client 'qjackctl' with PID 6171
OK, so apparently JACK (or qjackctl?) can't allocate memory for something; how do I fix this?
Secondly, when I try to play some music (such as, with 0xDEADBEEF), the music plays for a few seconds, and then I get just noise. The "Messages/Status" window in qjackctl shows this:
12:38:55.530 JACK connection graph change.
12:38:55.710 JACK connection change.
Thu Dec 2 12:38:55 2010: New client 'alsa-jack.jackP.6175.0' with PID 6175
Thu Dec 2 12:38:55 2010: Connecting 'alsa-jack.jackP.6175.0:out_000' to 'system:playback_1'
Thu Dec 2 12:38:55 2010: Connecting 'alsa-jack.jackP.6175.0:out_001' to 'system:playback_2'
12:38:57.824 XRUN callback (1).
Thu Dec 2 12:38:57 2010: [1m[31mERROR: JackEngine::XRun: client = alsa-jack.jackP.6175.0 was not run: state = 2[0m
Thu Dec 2 12:38:57 2010: [1m[31mERROR: JackAudioDriver::ProcessAsync Process error[0m
Thu Dec 2 12:38:57 2010: [1m[31mERROR: JackPosixMutex::Unlock res = 1[0m
Thu Dec 2 12:38:57 2010: [1m[31mERROR: JackPosixMutex::Unlock res = 1[0m
Thu Dec 2 12:38:57 2010: [1m[31mERROR: JackPosixMutex::Unlock res = 1[0m
Thu Dec 2 12:38:57 2010: [1m[31mERROR: JackPosixMutex::Unlock res = 1[0m
Thu Dec 2 12:38:57 2010: [1m[31mERROR: JackEngine::XRun: client = alsa-jack.jackP.6175.0 was not run: state = 1[0m
Thu Dec 2 12:38:57 2010: [1m[31mERROR: JackAudioDriver::ProcessAsync Process error[0m
Thu Dec 2 12:38:57 2010: [1m[31mERROR: JackEngine::XRun: client = alsa-jack.jackP.6175.0 was not run: state = 1[0m
Thu Dec 2 12:38:57 2010: [1m[31mERROR: JackAudioDriver::ProcessAsync Process error[0m
Thu Dec 2 12:38:57 2010: [1m[31mERROR: JackPosixMutex::Unlock res = 1[0m
Thu Dec 2 12:38:57 2010: [1m[31mERROR: JackPosixMutex::Unlock res = 1[0m
Thu Dec 2 12:38:57 2010: [1m[31mERROR: JackEngine::XRun: client = alsa-jack.jackP.6175.0 was not run: state = 1[0m
Thu Dec 2 12:38:57 2010: [1m[31mERROR: JackAudioDriver::ProcessAsync Process error[0m
Thu Dec 2 12:38:57 2010: [1m[31mERROR: JackPosixMutex::Unlock res = 1[0m
Thu Dec 2 12:38:57 2010: [1m[31mERROR: JackPosixMutex::Unlock res = 1[0m
These errors continue repeating until I stop the "music" (although I'm not hearing music anymore, lol).
Also, I've noticed sound in Flash doesn't work anymore.
If anyone could help me out with this - i.e. shed some light on this, help me configure JACK/JACK2 properly, and get my sound to work - I'll be very grateful.
Essentially, I'm trying to record some videos (video tutorials for my friends, as well as maybe something else in the future), for which I need both my microphone and the PCM output to be recorded. However, my Intel ICH-9 soundcard doesn't support capturing PCM or "Stereo Mix" or anything similar - all the capture channels I see in my alsamixer are "Mic", "Front Mic", "Line" and "CD".
Thanks everyone in advance!
Only the best is good enough.
Offline
I have this problem too, but I think it might have something to do with using a realtime kernel (something like kernel26-rt-ice or kernel26rt from the AUR)
Offline
I am not sure. Supposedly this should work without the -rt extensions. And besides, I am using the kernel26-lqx at the moment, which (IIRC) contains the -rt patches, and it still has the same effect.
Only the best is good enough.
Offline
I fixed that a year ago on another box that died. There is a solution for another distro I just have to find the article. I'll look for it today since I'm snowed in. And I never used th RT kernel.
Offline
This worked for me with the memory.
http://freebob.sourceforge.net/index.ph … root_users
And this for the xruns.
http://ubuntuforums.org/showthread.php?t=1625467
Sorry, I know nothing of kde.
Offline