1 Jun
2004
1 Jun
'04
2:29 p.m.
I'm running a 2.6 kernel with the realtime module added. I'm able to get
jack running with realtime capabilites using
jackstart -r -d alsa
from the command line. But if I run qjackctl, jack starts up, and I get
"Could not connect to JACK sever as client." error.
Alsaplayer seems to be ok, but ardour is a no go.....
I've tried mobprobing as any=1 and with the gid option too.
Any ideas.....
Greg
1 Jun
1 Jun
2:52 p.m.
Greg Moss <gmoss(a)TheWorld.com> writes:
I'm running a 2.6 kernel with the realtime module
added. I'm able to get
jack running with realtime capabilites using
jackstart -r -d alsa
I assume you're actually using -R. What happens if you run jackd
instead of jackstart?
from the command line. But if I run qjackctl, jack
starts up, and I get
"Could not connect to JACK sever as client." error.
Alsaplayer seems to be ok, but ardour is a no go.....
I've tried mobprobing as any=1 and with the gid option too.
Are you using allcaps=1?
Any ideas.....
This could be caused by other problems, such as the JACK --tmpdir
directory.
What version of JACK? Of realtime-lsm?
What do these commands print?
$ lsmod | grep realtime
$ grep Realtime /var/log/messages
--
joq
7274
days inactive
7274
days old
linux-audio-user@lists.linuxaudio.org
1 comments
2 participants
participants (2)
-
Greg Moss -
Jack O'Quin