Hello, Thats odd. I did nothing special and I have a rather old Turion64 mk I, just a clean install of latest 64 Studio 1.0. I started jackd (with qjackctl) with jackd -R -p128 -dalsa -dhw:2 -r48000 -p64 -n2 (which reads realtime mode, 64 frames, 2 Buffers, 128 ports max, no softmode, no hardwaremonitoring etc...) and it works great with the internal card. Its good for live action with PD and Zynaddsubfx synths. RME Hammerfall needs a bit more in my current configuration so it runs with 5ms which is still great in my opinion, remember that hardware midisynths can have some lag too. I remember reading for instance that the Roland D-70 had a horrible timing and the LFOs on my Casio FZ-1 Sampler get slower the more keys you press :) A full loaded Ardour session with lot of tracks need higher values because the internal hdd is certainly not the fastest. The pure install worked great with the opensource nv grafik driver which is actually a bit faster when it comes to 2d drawing. But I wanted the 3D driver badly because I do a lot of realtime 3D grafics during my live performances. The driver in the repos wanted to do strange things like deinstalling complete X11 so its not a good idea. But it was no big thing to download and run the AMD64 driverinstaller from Nvidias site. But yes, I wish it would be opensourced, but at least there is a running hardware OpenGL implementation, situation was worse in Linuxland some years ago. So first suggestion to Chuckk would be trying different jackd settings. ACPI is known to be broken because strange implementations by the manufactures. Under nonrealtime 32bit Ubuntu I needed to boot with acpi=off noacpi parameters to avoid xruns, for strange reasons I dont need it on 64 Studio anymore. Maybe a low ressource windows manager helps in your case so check out Blackbox which is in the Debian AMD64 repos. Blackbox is really bare bones so dont forget to install xterm so you can start programms. When you rightclick in the bare desktop a menu comes up with the xterm entry. Of course Blackbox can be configured to be more convinent, its just for testing. In general I am happy with 64 Studio. Nonrealtime stuff like Cinelerra is much more responsive too. What I miss are some packages but I guess they will be added/updated soon. Namely csound 5 would be great, I cant get it running at the moment. The repos holds an old 4.23 version and a pure data version without many important externals and a bug with the tablewrite function. I tried to compile on my own but failed so far, I get many errors, I already posted to the appropriate mailinglists. Some convinence laptop stuff is not working like cpu freq scaling, I guess these modules are not in the kernel and I am not sure if they belong there for a realtime system or if they beat down the performance. Cheers, Malte -- Malte Steiner media art + development -www.block4.com- next events: concert 29.dec 2006 Notstandskomitee vs. TBC Hoerbar Hamburg more at blog 4, also available as rss feed: http://java.block4.com/blog4/

On 12/21/06, Malte Steiner <steiner(a)block4.com> wrote: More and more I don't want to work my way through all of this. Thank you for the tips, but I'm finding now audio isn't working at all. I was able to compile Pure Data 1.40, its externals, and Csound5, but the more I think about it the less certain I am which laptop I was using. -Chuckk

Malte Steiner wrote: IIRC we're talking about compiling Csound5, yes ? I checked my old mail to the Csound list, I had problems with the FLTK stuff compiling on the AMD64. I received a helpful suggestion via this list (after no response on the Cs list) and discovered that the compiler optimization switch (-O) should be removed. I removed it, and voila, I have a working Csound5 on an AMD64 machine. It sounds like you have/had a problem with JACK versioning ? Did you resolve that issue ? Best, dp