[linux-audio-user] Re: linux-audio-user Digest, Vol 9, Issue 3

[Greg Moss]

> ------------------------------
>
> Message: 4
> Date: 01 Jun 2004 13:44:13 -0500
> From: "Jack O'Quin" <joq at io.com>
> Subject: Re: [linux-audio-user] JACK, Realtime-lsm, 2.6, Clients can't
> 	connect
> To: A list for linux audio users <linux-audio-user at music.columbia.edu>
> Message-ID: <87d64j9kzm.fsf at sulphur.joq.us>
> Content-Type: text/plain; charset=us-ascii


> Greg Moss <gmoss at 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?


Yes sorry about that, jackstart -R -d alsa

I think with Jackd I don't get realtime:

registered builtin port type 32 bit float mono audio
required capabilities not available
capabilities: =
loading driver ..
new client: alsa_pcm, id = 1 type 1 @ 0x8055830 fd = -1
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
Couldn't open hw:0 for 32bit samples trying 24bit instead
Couldn't open hw:0 for 24bit samples trying 16bit instead
Couldn't open hw:0 for 32bit samples trying 24bit instead
Couldn't open hw:0 for 24bit samples trying 16bit instead
new buffer size 1024
JACK: unable to mlock() port buffers: Operation not permitted
registered port alsa_pcm:capture_1, offset = 4096
registered port alsa_pcm:capture_2, offset = 8192
registered port alsa_pcm:playback_1, offset = 0
registered port alsa_pcm:playback_2, offset = 0
++ jack_rechain_graph():
client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
cannot set thread to real-time priority (FIFO/20) (1: Operation not
permitted)
no realtime watchdog thread
cannot use real-time scheduling (FIFO/10) (1: Operation not permitted)
2401 waiting for signals
load = 0.0516 max usecs: 22.000, spare = 21311.000

But I can with JAckstart

#jackstart -v -R -d alsa


registered builtin port type 32 bit float mono audio
capabilities: = cap_setpcap,cap_ipc_lock,cap_sys_nice,cap_sys_resource+eip
loading driver ..
new client: alsa_pcm, id = 1 type 1 @ 0x8055830 fd = -1
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
Couldn't open hw:0 for 32bit samples trying 24bit instead
Couldn't open hw:0 for 24bit samples trying 16bit instead
Couldn't open hw:0 for 32bit samples trying 24bit instead
Couldn't open hw:0 for 24bit samples trying 16bit instead
new buffer size 1024
registered port alsa_pcm:capture_1, offset = 4096
registered port alsa_pcm:capture_2, offset = 8192
registered port alsa_pcm:playback_1, offset = 0
registered port alsa_pcm:playback_2, offset = 0
++ jack_rechain_graph():
client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
2490 waiting for signals
load = 0.0820 max usecs: 35.000, spare = 21298.000


> > 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 should add that alsaplayer is going through jack, from best I can tell -
I am getting audio from it, and the "alsaplayer -o jack" command didn't
produce a "Failed to load output plugin "jack". Trying defaults." reply


> > I've tried mobprobing as any=1 and with the gid option too.
>
> Are you using allcaps=1?

yes, and I'm having the same problems


> This could be caused by other problems, such as the JACK --tmpdir
> directory.

This seems possible, perhaps alsaplayer doesn't try to make use of the
tmpdir?

> What version of JACK?  Of realtime-lsm?

jackstart -V
back from read, ret = 1 errno == Success
jackd version 0.98.1
default tmp directory: /tmp

Realtime is realtime-lsm-0.1.1

> What do these commands print?
>
>   $ lsmod | grep realtime

realtime               10128  0

>   $ grep Realtime /var/log/messages


Jun  1 19:07:05 localhost kernel: Realtime Capability LSM exiting
Jun  1 19:14:37 localhost kernel: Realtime LSM enabling all capabilities
Jun  1 19:14:37 localhost kernel: Realtime LSM initialized (group 101,

> --

Is there any other info I can provide that might help?

Thanks,

-G.