[ardour-users] Running Jack with Hammerfall HDSP

Jason Jones j at poeticintensity.com
Mon Sep 20 21:39:02 PDT 2004


Dan Sawyer wrote:

>Okay, I know I'm missing something ridiculously simple here, but I can't get 
>Jack to run reliably.  Any help would be tremendously appreciated. Here's 
>what's going on (output from qjackctl):
>
>
>17:49:23.205 /usr/bin/jackd -v -R -t500 -dalsa -dhw:0 -r48000 -p4096 -n2 -s 
>-i26 -o26
>17:49:23.216 JACK was started with PID=30533 (0x7745).
>getting driver descriptor from /usr/lib/jack/jack_dummy.so
>getting driver descriptor from /usr/lib/jack/jack_alsa.so
>jackd 0.94.0
>Copyright 2001-2003 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
>registered builtin port type 32 bit float mono audio
>loading driver ..
>new client: alsa_pcm, id = 1 type 1 @ 0x8057a30 fd = -1
>apparent rate = 48000
>creating alsa driver ... hw:0|hw:0|4096|2|48000|26|26|nomon|swmeter|soft-mode|
>32bit
>control device hw:0
>configuring for 48000Hz, period = 4096 frames, buffer = 2 periods
>new buffer size 4096
>JACK: unable to mlock() port buffers: Operation not permitted
>registered port alsa_pcm:capture_1, offset = 16384
>registered port alsa_pcm:capture_2, offset = 32768
>registered port alsa_pcm:capture_3, offset = 49152
>registered port alsa_pcm:capture_4, offset = 65536
>registered port alsa_pcm:capture_5, offset = 81920
>registered port alsa_pcm:capture_6, offset = 98304
>registered port alsa_pcm:capture_7, offset = 114688
>registered port alsa_pcm:capture_8, offset = 131072
>registered port alsa_pcm:capture_9, offset = 147456
>registered port alsa_pcm:capture_10, offset = 163840
>registered port alsa_pcm:capture_11, offset = 180224
>registered port alsa_pcm:capture_12, offset = 196608
>registered port alsa_pcm:capture_13, offset = 212992
>registered port alsa_pcm:capture_14, offset = 229376
>registered port alsa_pcm:capture_15, offset = 245760
>registered port alsa_pcm:capture_16, offset = 262144
>registered port alsa_pcm:capture_17, offset = 278528
>registered port alsa_pcm:capture_18, offset = 294912
>registered port alsa_pcm:capture_19, offset = 311296
>registered port alsa_pcm:capture_20, offset = 327680
>registered port alsa_pcm:capture_21, offset = 344064
>registered port alsa_pcm:capture_22, offset = 360448
>registered port alsa_pcm:capture_23, offset = 376832
>registered port alsa_pcm:capture_24, offset = 393216
>registered port alsa_pcm:capture_25, offset = 409600
>registered port alsa_pcm:capture_26, offset = 425984
>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
>registered port alsa_pcm:playback_9, offset = 0
>registered port alsa_pcm:playback_10, offset = 0
>registered port alsa_pcm:playback_11, offset = 0
>registered port alsa_pcm:playback_12, offset = 0
>registered port alsa_pcm:playback_13, offset = 0
>registered port alsa_pcm:playback_14, offset = 0
>registered port alsa_pcm:playback_15, offset = 0
>registered port alsa_pcm:playback_16, offset = 0
>registered port alsa_pcm:playback_17, offset = 0
>registered port alsa_pcm:playback_18, offset = 0
>registered port alsa_pcm:playback_19, offset = 0
>registered port alsa_pcm:playback_20, offset = 0
>registered port alsa_pcm:playback_21, offset = 0
>registered port alsa_pcm:playback_22, offset = 0
>registered port alsa_pcm:playback_23, offset = 0
>registered port alsa_pcm:playback_24, offset = 0
>registered port alsa_pcm:playback_25, offset = 0
>registered port alsa_pcm:playback_26, 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)
>30533 waiting for signals
>load = 0.4875 max usecs: 832.000, spare = 84501.000
>load = 0.7313 max usecs: 832.000, spare = 84501.000
>17:49:25.344 Could not connect to JACK server as client.
>
>
>_______________________________________________
>ardour-users-ardour.org mailing list
>ardour-users at lists.ardour.org
>http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org
>
>
>  
>
Are you running jack with root privileges, or the appropriate kernel 
patches?  Looks like it's having a hard time getting the access it needs 
to the real-time scheduler..  I could be wrong, but - I thought I'd try. :)

--Jason



More information about the Ardour-Users mailing list