Hi,
I got this report from a qjackctl user with some Celeron 500: 18:18:41.657 Patchbay deactivated. 18:18:41.798 Statistics reset. 18:18:41.962 Startup script... 18:18:41.963 artsshell -q terminate 18:18:42.093 MIDI connection graph change. 18:18:42.577 Startup script terminated with exit status=256. 18:18:42.579 JACK is starting... 18:18:42.580 jackd-realtime -R -P1 -dalsa -dhw:0 -r44100 -p4096 -n9 -D -Chw:0,0 -i2 -o2 18:18:42.588 Could not start JACK. Sorry. 18:18:44.345 JACK was stopped successfully. 18:18:44.557 MIDI connection change. 18:18:57.859 Startup script... 18:18:57.859 artsshell -q terminate 18:18:58.395 Startup script terminated with exit status=256. 18:18:58.396 JACK is starting... 18:18:58.397 /usr/bin/jackd -R -P1 -dalsa -dhw:0 -r44100 -p4096 -n9 -D -Chw:0,0 -i2 -o2 18:18:58.406 JACK was started with PID=3755 (0xea. jackd 0.99.54 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. loading driver .. apparent rate = 44100 creating alsa driver ... hw:0|hw:0,0|4096|9|44100|2|2|nomon|swmeter|-|32bit control device hw:0 configuring for 44100Hz, period = 4096 frames, buffer = 9 periods Note: audio device hw:0,0 doesn't support a 32bit sample format so JACK will try a 24bit format instead Note: audio device hw:0,0 doesn't support a 24bit sample format so JACK will try a 16bit format instead ALSA: got smaller periods 2 than 9 for capture ALSA: cannot configure capture channel cannot load driver module alsa 18:19:01.156 Could not connect to JACK server as client. could not attach as JACK client (server has exited) 18:19:01.388 JACK was stopped successfully. 18:19:35.705 Startup script... 18:19:35.714 artsshell -q terminate 18:19:36.289 Startup script terminated with exit status=256. 18:19:36.295 JACK is starting... 18:19:36.299 /usr/bin/jackd -R -P1 -dalsa -r44100 -p4096 -n4 -D -Chw:0,0 -Phw:0,0 -i2 -o2 18:19:36.329 JACK was started with PID=3759 (0xeaf). jackd 0.99.54 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. loading driver .. apparent rate = 44100 creating alsa driver ... hw:0,0|hw:0,0|4096|4|44100|2|2|nomon|swmeter|-|32bit control device hw:0 configuring for 44100Hz, period = 4096 frames, buffer = 4 periods Note: audio device hw:0,0 doesn't support a 32bit sample format so JACK will try a 24bit format instead Note: audio device hw:0,0 doesn't support a 24bit sample format so JACK will try a 16bit format instead ALSA: got smaller periods 2 than 4 for capture ALSA: cannot configure capture channel cannot load driver module alsa 18:19:39.076 Could not connect to JACK server as client. could not attach as JACK client (server has exited) 18:19:39.283 JACK was stopped successfully. 18:19:53.738 Startup script... 18:19:53.743 artsshell -q terminate 18:19:54.336 Startup script terminated with exit status=256. 18:19:54.342 JACK is starting... 18:19:54.346 /usr/bin/jackd -R -P1 -dalsa -r48000 -p4096 -n4 -D -Chw:0,0 -Phw:0,0 -i2 -o2 18:19:54.377 JACK was started with PID=3763 (0xeb3). jackd 0.99.54 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. loading driver .. apparent rate = 48000 creating alsa driver ... hw:0,0|hw:0,0|4096|4|48000|2|2|nomon|swmeter|-|32bit control device hw:0 configuring for 48000Hz, period = 4096 frames, buffer = 4 periods Note: audio device hw:0,0 doesn't support a 32bit sample format so JACK will try a 24bit format instead Note: audio device hw:0,0 doesn't support a 24bit sample format so JACK will try a 16bit format instead ALSA: got smaller periods 2 than 4 for capture ALSA: cannot configure capture channel cannot load driver module alsa 18:19:58.023 Could not connect to JACK server as client. could not attach as JACK client (server has exited) 18:19:58.229 JACK was stopped successfully. 18:20:13.712 Startup script... 18:20:13.717 artsshell -q terminate Any ideas? Alexandre ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Jackit-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/jackit-devel |
> Hi, > > I got this report from a qjackctl user with some Celeron 500: > [...] > 18:18:58.397 /usr/bin/jackd -R -P1 -dalsa -dhw:0 -r44100 -p4096 -n9 -D > -Chw:0,0 -i2 -o2 [...] > ALSA: got smaller periods 2 than 9 for capture > ALSA: cannot configure capture channel > cannot load driver module alsa [...] > > Any ideas? > Try "Playback only" mode (-P) or change the capture device (-Chw:0,0) to something else. It seems to complain that the number of periods (-n9) cannot be that large, at least for capture. I would retry the default (-n2). Bye now. -- rncbc aka Rui Nuno Capela [hidden email] ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Jackit-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/jackit-devel |
Free forum by Nabble | Edit this page |