<div><span class="gmail_quote">On 6/24/07, <b class="gmail_sendername">Loki Davison</b> <<a href="mailto:loki.davison@gmail.com">loki.davison@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On 6/25/07, Chuckk Hubbard <<a href="mailto:badmuthahubbard@gmail.com">badmuthahubbard@gmail.com</a>> wrote:
<br>> On 12/1/06, Dave Phillips <<a href="mailto:dlphillips@woh.rr.com">dlphillips@woh.rr.com</a>> wrote:<br>> ><br>> > 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>> ><br>> Hi Dave and everyone. I am still wrestling with this. I have the new ALSA<br>> driver that supports my card, finally, but under 64studio I still get
<br>> 20-some xruns a second, and Audacity is unable to connect to jackd.<br>> PortAudio appears for a split second in the jack connection dialog, and<br>> disappears. Some of you told me 64studio was preconfigured for low-latency
<br>> audio out of the "box" and all the apps were tuned to the distro, but it<br>> 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?
<br>> There's still a lot of info out there that is obsolete, so I'm wary of<br>> Google.<br>> Just a note: I have been trying for several years to get low-latency audio<br>> working right on Linux. This is a new machine, though, as of November 06,
<br>> and I had to wait 7 months for my audio card and wireless (still not working<br>> right) to be nominally supported, so I haven't tried much for about 6<br>> months. I'm still amazed at how everything just seems to work without
<br>> tweaking for some folks, and I'm wondering if there's something fundamental<br>> I'm just not doing. My problems have baffled some of the very developers<br>> who created drivers specifically for the hardware I have. What could be
<br>> wrong?<br>><br>> -Chuckk<br>><br><br>I also had problems for ages getting my soundcard to work. After a<br>long time i found a good solution. I bought a decent soundcard. Got<br>cardbus on the laptop? grab an echo cardbus thing. They are cheap on
<br>ebay in the USA. I got my Gina3g from the USA for 200 USD. Pretty damn<br>cheap compared to a new guitar or bass. If you have firewire you can<br>try that too after looking what cards work. The cardbus is easier<br>though.
</blockquote>
<div> </div>
<div>Thanks Loki. My soundcard works though. The wireless does not, but I'm just posting here to find out how to improve my audio performance.</div>
<div> </div>
<div>-Chuckk</div></div>