[PlanetCCRMA] very strange alsa, no jack

Fernando Pablo Lopez-Lezcano nando@ccrma.Stanford.EDU
Wed Apr 7 11:42:01 2004


> > > registered builtin port type 32 bit float mono audio
> > > required capabilities not available
> > > capabilities: =i
> > > loading driver ..
> > > new client: alsa_pcm, id = 1 type 1 @ 0x8057c90 fd = -1
> > > creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|rt|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
> > > registered port alsa_pcm:playback_3, offset = 0
> > > registered port alsa_pcm:playback_4, offset = 0
> > > registered port alsa_pcm:playback_5, offset = 0
> > > registered port alsa_pcm:playback_6, offset = 0
> > > ++ jack_rechain_graph():
> > > client alsa_pcm: internal client, execution_order=0.
> > > -- jack_rechain_graph()
> > > 7184 waiting for signals
> > > 
> > > required capabilities not available??? Is this because I'm not using the 
> > > real low-latency kernel?  Even though it says 'waiting for signals', when 
> > > I try to start something with a jack output, it says it can't find it.
> > 
> > Are you running the client processes as the same user as the server?
>
> I'm a newbie, but my machine is stand-alone (not networked)...so yes I 
> believe this must be the case.

What I meant is, you login as user xxx and then run both jack and the
client there, without doing a "su root" for anything. 

> > What kernel are you booted in? ("uname -r" to find out). Capabilities
> > are enabled in both Planet CCRMA kernels...
> $ uname -r
> 2.4.20-28.1.caps.rh90.ccrma

Then you should be fine. Try adding the "-R" flag to the jackstart
invocation to see if you go into realtime priority or not. 

-- Fernando