<br><div><span class="e" id="q_1135f88154655a26_0">On 12/1/06, <b class="gmail_sendername">Dave Phillips</b> <<a href="mailto:dlphillips@woh.rr.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
dlphillips@woh.rr.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Bill Allen wrote:<br><br>> At the risk of repeating myself, in the time that I've been just<br>> reading this thread (not to mention the time that you've been putting<br>> into trying the stuff mentioned) I could have downloaded 64Studio, set
<br>> aside a 5-10 GB partition, installed it, and had a working system with<br>> all the real-time patched AMD64 music-enabled system that you can get.<br>> Yes, you've got to dual boot, I do it all the time. Ubuntu is my
<br>> family system that we use for work and play, but when I want to do<br>> music I boot into 64Studio. It's simply a lot easier than trying to<br>> make a general purpose distro into a music enabled one.<br>
<br>Hear the man. I started writing a similar reply yesterday, but Bill's<br>said it better here. Given the availability of multimedia-optimized<br>distros I just don't see the point of putting myself through what the
<br>distro maintainers have already been through and mastered. Maybe it's an<br>age thing, at mine I get someone else to do the heavy lifting. :)<br><br>Really, I work with Linux audio software to make music. I lost interest
<br>in mucking about with kernel configurations long ago. Yes, I'm glad I<br>know how to do some of that stuff by myself, but I no longer consider it<br>a necessary part of the process. I agree with Bill, use 64Studio,
<br>PlanetCCRMA, or some other optimized distro and save yourself time and<br>energy.<br><br>Best,<br><br>dp<br><br></blockquote></div><br></span></div>Hi Dave and everyone. I am still wrestling with this. I have the new ALSA driver that supports my card, finally, but under 64studio I still get 20-some xruns a second, and Audacity is unable to connect to jackd. PortAudio appears for a split second in the jack connection dialog, and disappears. Some of you told me 64studio was preconfigured for low-latency audio out of the "box" and all the apps were tuned to the distro, but it doesn't seem to work that way for me.
<br>Anyone know an up-to-date guide to low-latency audio on Debian or Linux? There's still a lot of info out there that is obsolete, so I'm wary of Google.<br>Just a note: I have been trying for several years to get low-latency audio working right on Linux. This is a new machine, though, as of November 06, and I had to wait 7 months for my audio card and wireless (still not working right) to be nominally supported, so I haven't tried much for about 6 months. I'm still amazed at how everything just seems to work without tweaking for some folks, and I'm wondering if there's something fundamental I'm just not doing. My problems have baffled some of the very developers who created drivers specifically for the hardware I have. What could be wrong?
<br><br>-Chuckk<br clear="all"><span class="sg"><br>-- <br><a href="http://www.badmuthahubbard.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.badmuthahubbard.com</a>
</span><br clear="all"><br>-- <br><a href="http://www.badmuthahubbard.com">http://www.badmuthahubbard.com</a>