[ardour-users] Problems running jack and ardour on macbookpro and debian

Sampo Savolainen v2 at iki.fi
Fri May 11 02:37:30 PDT 2007


(I'm replying to the list as it seems you sent this to only me by mistake.)

Quoting Antonio Castellano <stanzarossa at email.it>:

> i always use jackd and this is the output
> 11:12:56.033 /usr/bin/jackd -v -R -P89 -p1024 -dalsa -r44100 -p1024 -n2 
> -D -Chw:0 -Phw:0
> 11:12:56.046 JACK was started with PID=23415 (0x5b77).
> getting driver descriptor from /usr/lib/libjack0.100.0-0/jack_dummy.so
> getting driver descriptor from /usr/lib/libjack0.100.0-0/jack_alsa.so
> getting driver descriptor from /usr/lib/libjack0.100.0-0/jack_oss.so
> jackd 0.101.1
> Copyright 2001-2005 Paul Davis and others.
> jackd comes with ABSOLUTELY NO WARRANTY
> This is free software, and you are welcome to redistribute it
> under certain conditions; see the file COPYING for details
> JACK compiled with System V SHM support.
> server `default' registered
> loading driver ..
> apparent rate = 44100
> creating alsa driver ...
> hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
> control device hw:0
> configuring for 44100Hz, period = 1024 frames, buffer = 2 periods
> nperiods = 2 for capture
> nperiods = 2 for playback
> registered builtin port type 32 bit float mono audio
> required capabilities not available
> capabilities: = cap_ipc_lock,cap_sys_nice+e
> new client: alsa_pcm, id = 1 type 1 @ 0x8058538 fd = -1
> 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
> registered port alsa_pcm:playback_7, offset = 0
> registered port alsa_pcm:playback_8, offset = 0
> ++ jack_rechain_graph():
> client alsa_pcm: internal client, execution_order=0.
> -- jack_rechain_graph()
> 23415 waiting for signals
> **** alsa_pcm: xrun of at least 0.030 msecs
> **** alsa_pcm: xrun of at least 0.037 msecs
> **** alsa_pcm: xrun of at least 0.038 msecs
> 
> 
> trying with 3periods/buffer i got
> new client: alsa_pcm, id = 1 type 1 @ 0x8058538 fd = -1
> ALSA: got smaller periods 2 than 3 for playback
> ALSA: cannot configure playback channe
> 
> even trying with only capture i got the same errors:
> 11:17:38.258 /usr/bin/jackd -v -R -P89 -p1024 -dalsa -dhw:0,0 -r44100 
> -p1024 -n3 -Chw:0
> 11:17:38.262 JACK was started with PID=23427 (0x5b83).
> getting driver descriptor from /usr/lib/libjack0.100.0-0/jack_dummy.so
> getting driver descriptor from /usr/lib/libjack0.100.0-0/jack_alsa.so
> getting driver descriptor from /usr/lib/libjack0.100.0-0/jack_oss.so
> jackd 0.101.1
> Copyright 2001-2005 Paul Davis and others.
> jackd comes with ABSOLUTELY NO WARRANTY
> This is free software, and you are welcome to redistribute it
> under certain conditions; see the file COPYING for details
> JACK compiled with System V SHM support.
> server `default' registered
> loading driver ..
> apparent rate = 44100
> creating alsa driver ... -|hw:0|1024|3|44100|0|0|nomon|swmeter|-|32bit
> control device hw:0
> configuring for 44100Hz, period = 1024 frames, buffer = 3 periods
> nperiods = 3 for capture
> registered builtin port type 32 bit float mono audio
> required capabilities not available
> capabilities: = cap_ipc_lock,cap_sys_nice+e

That is a strange message, but I suspect your problem probably might come
from having defined both a capture device and a general alsa device to use.
In second command line you have:

 -dalsa (selects the driver and all parameters after it
         are passed on to that driver)
 -dhw:0,0 (selects the full-duplex device to use)
 -Chw:0   (selects the capture device)

Another strong candidate would be your mixer settings. My laptop has a
intel-hda type soundcard and the driver behaves strangely at least on that
chipset. The driver returns no captured samples to the software using it if
the mixer is not set to capture any input port. If you set the "capture"
port to "capture" in the mixer, you might have better luck.



> kernel:
> $ uname -a
> Linux debian 2.6.21-rt1 #1 SMP PREEMPT Sat Apr 28 17:26:41 EEST 2007 
> i686 GNU/Linux
> 
> CONFIG_PREEMPT_RT=y
> CONFIG_PREEMPT=y
> CONFIG_PREEMPT_SOFTIRQS=y
> CONFIG_PREEMPT_HARDIRQS=y
> CONFIG_PREEMPT_BKL=y
> CONFIG_PREEMPT_RCU=y
> CONFIG_SECURITY_CAPABILITIES=m
> CONFIG_REALTIME_CAPABILITIES=m
> 
> rlimits is also well configured, and i've used both libpam from etch and
> 
> libpam from ubuntu studio.
> sorry for the big output but there isn't any page on te web speaking 
> about something like this, it look like i'm the first using jack on a 
> macbook pro
> 
> 
> thank again to all of you...



More information about the Ardour-Users mailing list