Austin wrote: Those look like usb driver errors. have you run lsusb and/or some of the other usb debug tools and sent to the usb-devel list? That's strange I can run it for hours with no problems using -p 1024 -n3 Yeah. One day it might actually be possible to use all four channels at one time via jackd. I've only once been able to get it running solid and lately it has become impossible. -- Patrick Shirkey - Boost Hardware Ltd. Http://www.boosthardware.com Http://www.djcj.org - The Linux Audio Users guide ======================================== Being on stage with the band in front of crowds shouting, "Get off! No! We want normal music!", I think that was more like acting than anything I've ever done. Goldie, 8 Nov, 2002 The Scotsman

Austin wrote: What do you get if you use jackd -v -R -a -d alsa -d hw:1 -p 1024 -n 3 running as root. -- Patrick Shirkey - Boost Hardware Ltd. Http://www.boosthardware.com Http://www.djcj.org - The Linux Audio Users guide ======================================== Being on stage with the band in front of crowds shouting, "Get off! No! We want normal music!", I think that was more like acting than anything I've ever done. Goldie, 8 Nov, 2002 The Scotsman

On Fri, 2003-11-07 at 10:31, Brian Redfern wrote: Yes. Since you'll want to mount /tmp in ram, more is better. I've monitored mine (with 500 MB), and it never seems to fill up, so I think that's adequate. Austin -- Austin Acton Synthetic Organic Chemist, Teaching Assistant, Ph.D. Candidate Department of Chemistry, York University, Toronto MandrakeLinux Volunteer Developer, homepage: www.groundstate.ca

Benjamin Flaming <lau(a)solobanjo.com> writes: Me, too. I'd love to have 512MB, but JACK runs fine with 256MB. About the only problem I experience is netscape or emacs getting swapped out if I have a lot of realtime audio running. Nothing fails. -- joq

Jack winds up freezing my machine up with certain apps, I've been able to run it with rosegarden, but I still haven't been able to get it to work. On Fri, 2003-11-07 at 09:43, Jack O'Quin wrote:

Ryan &lt;ruinaudio(a)comcast.net&gt; writes: This may be known to some people. I recall vague mention of USB problems on various mailing lists. But, nothing specific. Although this sounds like a very serious problem, I don't see any bug report in <http://jackit.sourceforge.net/mantis>, the JACK Mantis database. If it makes JACK useless, someone should report it, providing enough information for developers to work on the problem. Regards, -- Jack O'Quin Austin, Texas

Brian Redfern wrote: This doesn't happen for me. I use jack + quattro with a celeron 1 Ghz pIII, ASUS microATX mobo, 512 MB RAM, sis630 VGA. kernel-2.4.21-ll usb-ohci. gcc-2.95.4 enlightenment-0.16.x alsa-driver-0.9.4 (Jul 31 2003 cvs) jackd-0.90 tarball which Paul made because I cannot compile cvs for some reason. I can run for hours without dropouts as root with: jackd -v -R -a -d alsa -d quattro2 -p 1024 -n 3 -zt (I cannot actually use alsa as a normal user on this machine but I never want to anyway. ;) I wouldn't say the jack driver is useless for me. In fact I just realised that even though I get spurious amounts of error messages: late driver wakeup: nframes to process = 2048. with -n 4 I can run all four channels without obvious playback errors and with only a couple of dropouts for a simple 10 second record test in ardour (while also running alsaplayer). However my computer has issues with changing virtual desktops while running jackd so this crashed after about two minutes. Straight after I changed desktops though. Running with -n 3 and recorded for 7 minutes before jackd shutdown. The sound quality is poorer (very obvious crackling and pops) but I didn't switch desktops. This time I prevented a hard reboot by alt+sysreq+e , alt+sysreq+i. BTW I also experience the problem of jackd not accepting ^C in the term with this version. Running with -n 6 the sound quality is much cleaner. I was able to listen to the previous 7 minutes then record for another 2 before jackd died. Trying again I was able to record for about 9 minutes before jackd crashed. Luckily, this time I was able to ^C out :/ This is what the output from jack looks like: --------- load = 11.0997 max usecs: 2507.000, spare = 20712.000 late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. load = 10.8494 max usecs: 2461.000, spare = 20758.000 late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 2048. late driver wakeup: nframes to process = 3072. delay of 23439.000 usecs exceeds estimated spare time of 20758.000; restart ... delay of 23439.000 usecs exceeds estimated spare time of 20758.000; restart ... delay of 23439.000 usecs exceeds estimated spare time of 20758.000; restart ... ALSA lib pcm_hw.c:494:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pi pe could not start playback (Broken pipe) jackd watchdog: timeout - killing jackd Aborted -------- The load = 10.8494 max usecs: 2461.000, spare = 20758.000 messages are almost exactly equally spaced until the last one where we get late driver wakeup: nframes to process = 3072. jackd seems to be happy as long as the late driver wakeup doesn't exceed 3072. Maybe this could be enforced somehow to make a simple fix for USB devices. Although I would rather see the complete solution implemented. (hint hint nudge nudge). -- Patrick Shirkey - Boost Hardware Ltd. Http://www.boosthardware.com Http://www.djcj.org - The Linux Audio Users guide ======================================== Being on stage with the band in front of crowds shouting, "Get off! No! We want normal music!", I think that was more like acting than anything I've ever done. Goldie, 8 Nov, 2002 The Scotsman

On Fri, 2003-11-07 at 06:55, Patrick Shirkey wrote: It seems to work fine if I use -n 4 or greater. Why do you choose 3? Isn't 2, 4, 8... more common? Also, I'm trying to adapt the .asoundrc to use hw:1, becuase Mandrake's hardware manager forces my internal soundcard to hw:0. Obviously there are just some changes from "card 0" to "card 1", but do I have to modify the pcm.quattro, pcm.q4, and pcm.q4b sections? Thanks for your help, Patrick. Austin -- Austin Acton Synthetic Organic Chemist, Teaching Assistant, Ph.D. Candidate Department of Chemistry, York University, Toronto MandrakeLinux Volunteer Developer, homepage: www.groundstate.ca

Probably have the wrong version of alsa for the qauttro, but anyways crazy tunes, I've got a linux only composition up on my website, I recently sold all my hardware and am now working on all my new tunes using just linux, at the moment with csound. Csound is fascinating 'cause you can distribute the "source code" of the compostion along with the audio file: http://asapien.org On Wed, 2003-11-05 at 02:17, Patrick Shirkey wrote: