[PlanetCCRMA] Help: Alsa & Jack

Gregory McCourt greg.mccourt@englishfirst.com
Sun Apr 3 19:44:01 2005


-----Original Message-----
From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Gregory McCourt <greg.mccourt@englishfirst.com>
Date: 03 Apr 2005 16:04:12 -0700
Subject: Re: [PlanetCCRMA] Help: Alsa & Jack

...

It does not look like you are doing anything wrong. I may be that your
card is not happy with the parameter you are choosing. The first thing I
would try is to increase the number of periods from 2 to 3, and/or
decrease the period size to 512. 

-- Fernando

Hi Fernando,
I tried your two suggestions, but with no luck.

1. Setting buffer=3 rather than 2 results in:

09:30:34.035 Patchbay deactivated.
09:30:34.311 Statistics reset.
09:30:34.315 Could not open ALSA sequencer as a client. MIDI patchbay will be not available.
ALSA lib seq_hw.c:451:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory
09:31:14.603 Startup script...
09:31:14.603 artsshell -q terminate
09:31:14.843 Startup script terminated with exit status=256.
09:31:14.843 JACK is starting...
09:31:14.843 /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p1024 -n3
09:31:14.845 JACK was started with PID=8110 (0x1fae).
jackd 0.99.36
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
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|1024|3|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames, buffer = 3 periods
Couldn't open hw:0 for 32bit samples trying 24bit instead
Couldn't open hw:0 for 24bit samples trying 16bit instead
ALSA: got smaller periods 2 than 3 for capture
ALSA: cannot configure capture channel
cannot load driver module alsa
09:31:14.881 JACK was stopped successfully.
09:31:16.979 Could not connect to JACK server as client.


2. By setting period=512 with buffer=2, it seems to want to start, but dies right away:

09:33:32.112 Startup script...
09:33:32.112 artsshell -q terminate
09:33:32.352 Startup script terminated with exit status=256.
09:33:32.352 JACK is starting...
09:33:32.352 /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p512 -n2
09:33:32.364 JACK was started with PID=8114 (0x1fb2).
jackd 0.99.36
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
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|512|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 512 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
nperiods = 2 for capture
nperiods = 2 for playback
09:33:34.377 Server configuration saved to "/home/greg/.jackdrc".
09:33:34.377 Statistics reset.
09:33:34.392 Client activated.
09:33:34.392 Audio connection change.
09:33:34.393 Audio connection graph change.
09:33:34.405 XRUN callback (1).
09:33:36.402 XRUN callback (99 skipped).
09:33:38.412 XRUN callback (100 skipped).
09:33:40.421 XRUN callback (99 skipped).
jackd watchdog: timeout - killing jackd
09:33:42.430 XRUN callback (99 skipped).
zombified - calling shutdown handler
09:33:42.649 Shutdown notification.
09:33:42.649 Client deactivated.
09:33:42.650 JACK is stopping...
cannot read result for request type 7 from server (Connection reset by peer)
cannot send request type 7 to server
cannot read result for request type 7 from server (Broken pipe)
09:33:42.850 JACK was stopped successfully.


Any other suggestions of adjustments I could try? Thanks for your time.

greg