Jack doen't start anymore

  • alidh
Posted: Thu, 01/03/2008 - 13:43
Strange, after a clean install of 64studio testing jack doesn't work anymore: These are the messages which I get: 14:34:53.317 Patchbay deactivated. 14:34:53.378 Statistics reset. 14:34:53.464 MIDI connection graph change. JACK tmpdir identified as [/dev/shm] 14:34:53.635 MIDI connection change. 14:34:56.408 Startup script... 14:34:56.409 artsshell -q terminate JACK tmpdir identified as [/dev/shm] 14:34:56.669 Startup script terminated with exit status=256. 14:34:56.671 JACK is starting... 14:34:56.673 /usr/bin/jackd -R -dalsa -dhw:0,0 -r44100 -p64 -n2 -s -m 14:34:56.689 JACK was started with PID=5260 (0x148c). jackd 0.103.0 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. cannot use real-time scheduling (FIFO at priority 10) [for thread -1210914512, from thread -1210914512] (1: Operation not permitted) cannot create engine 14:34:56.706 JACK was stopped successfully. 14:34:56.707 Post-shutdown script... 14:34:56.707 killall jackd jackd: geen proces afgebroken 14:34:56.933 Post-shutdown script terminated with exit status=256. 14:34:58.014 Startup script... 14:34:58.017 artsshell -q terminate JACK tmpdir identified as [/dev/shm] 14:34:58.269 Startup script terminated with exit status=256. 14:34:58.271 JACK is starting... 14:34:58.273 /usr/bin/jackd -R -dalsa -dhw:0,0 -r44100 -p64 -n2 -s -m 14:34:58.287 JACK was started with PID=5264 (0x1490). jackd 0.103.0 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. cannot use real-time scheduling (FIFO at priority 10) [for thread -1210861264, from thread -1210861264] (1: Operation not permitted) cannot create engine 14:34:58.327 JACK was stopped successfully. 14:34:58.329 Post-shutdown script... 14:34:58.331 killall jackd jackd: geen proces afgebroken 14:34:58.548 Post-shutdown script terminated with exit status=256. 14:35:00.392 Could not connect to JACK server as client. Please check the messages window for more info. JACK tmpdir identified as [/dev/shm]
‹ Midi: 2 Soundfonts on one Instrument? too much midi clients ›

disable «Realtime», remove

  • Happy Eddie
  • 01/05/08
  • Sat, 01/05/2008 - 21:23
  • Copy comment link
disable «Realtime», remove the -R parameter in /usr/bin/jackd or run as root.

Sorry, I think a messed up

  • alidh
  • 11/29/07
  • Thu, 01/03/2008 - 19:49
  • Copy comment link
Sorry, I think I "messed up" 64studio a bit. Did a clean install and shift to Testing, and thought I installed also the new kernel from 64studio, but there's no multimedia in the kernel's name... :/ ;) So I'm wondering if there is a different kernel in testing compared to stable and if 64studio testing is compatible with Debian testing. Than I will install a new multimedia-kernel and rebuild my nvidia module... http://www.64studio.com/node/372

Try increasing frames/period

  • Pablo
  • 07/11/07
  • Thu, 01/03/2008 - 14:27
  • Copy comment link
What audio card are you using? Report the output of "cat /proc/asound/cards" Anyway, if you are using your onboard audio card I think 64 frames/period is not a good option. Increase that value until you have jack running stably with no x-runs (red numbers). You had 256 before, as you showed in a screenshot in http://www.64studio.com/node/321. You might be asking too much to your audio card, that's why JACK crashes. Other possible reason is the priority. The message says something about it. I am not sure what it really means that but try increasing that value too. Pablo