On Sat, Jul 4, 2009 at 9:13 AM, Paul Neaveill<boycotthell2005(a)yahoo.com> wrote:
First, am new to the group here and my first post/question here. Think this is a
wonderful site and hoping someone can answer some questions for me that have been dogging
me for quite some time for our Ubuntu system. Have been asking for help there at the
forum, but of little help.
The dream:
We want to set up a studio with digital piano and 2 synths, MIDI'd through to the
computer via Tascam us122.
The problem:
For some reason, we just cannot figure out how to get Jack to setup properly.<code>
11:10:02.299 Patchbay deactivated.
11:10:02.302 Statistics reset.
11:10:02.559 ALSA connection graph change.
11:10:02.796 ALSA connection change.
11:10:07.471 Startup script...
11:10:07.472 artsshell -q terminate
11:10:08.148 Startup script terminated with exit status=256.
11:10:08.150 JACK is starting...
11:10:08.151 /usr/bin/jackd -dalsa -dhw:0 -r44100 -p16 -n2 -m -I1 -O1
11:10:08.159 JACK was started with PID=9030.
jackd 0.109.2
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|16|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 16 frames (0.4 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 16bit little-endian
ALSA: cannot set period size to 16 frames for capture
ALSA: cannot configure capture channel
cannot load driver module alsa
no message buffer overruns
11:10:08.350 JACK was stopped successfully.
11:10:08.351 Post-shutdown script...
11:10:08.352 killall jackd
jackd: no process killed
11:10:08.794 Post-shutdown script terminated with exit status=256.
11:10:09.262 Could not connect to JACK server as client. - Overall operation failed. -
Unable to connect to server. Please check the messages window for more info.</code>
tried 64/32/ and now 16 for the period/ capture based on some forum advice somewhere.
Thanks in advance
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
What sound card are you using? 16 frames is a very short period size
and is apparently incompatible with your sound card. I would try a
larger number and work your way down, finding the lowest one where you
don't get xruns with the software you intend to use.