On 6/25/07, Chuckk Hubbard <badmuthahubbard@xxxxxxxxx> wrote:
On 6/24/07, Loki Davison <loki.davison@xxxxxxxxx> wrote: > > On 6/25/07, Chuckk Hubbard <badmuthahubbard@xxxxxxxxx> wrote: > > On 12/1/06, Dave Phillips <dlphillips@xxxxxxxxxx> wrote: > > > > > > Bill Allen wrote: > > > > > > > At the risk of repeating myself, in the time that I've been just > > > > reading this thread (not to mention the time that you've been > putting > > > > into trying the stuff mentioned) I could have downloaded 64Studio, > set > > > > aside a 5-10 GB partition, installed it, and had a working system > with > > > > all the real-time patched AMD64 music-enabled system that you can > get. > > > > Yes, you've got to dual boot, I do it all the time. Ubuntu is my > > > > family system that we use for work and play, but when I want to do > > > > music I boot into 64Studio. It's simply a lot easier than trying to > > > > make a general purpose distro into a music enabled one. > > > > > > Hear the man. I started writing a similar reply yesterday, but Bill's > > > said it better here. Given the availability of multimedia-optimized > > > distros I just don't see the point of putting myself through what the > > > distro maintainers have already been through and mastered. Maybe it's > an > > > age thing, at mine I get someone else to do the heavy lifting. :) > > > > > > Really, I work with Linux audio software to make music. I lost > interest > > > in mucking about with kernel configurations long ago. Yes, I'm glad I > > > know how to do some of that stuff by myself, but I no longer consider > it > > > a necessary part of the process. I agree with Bill, use 64Studio, > > > PlanetCCRMA, or some other optimized distro and save yourself time and > > > energy. > > > > > > Best, > > > > > > dp > > > > > > > > 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. > > 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. > > 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? > > > > -Chuckk > > > > I also had problems for ages getting my soundcard to work. After a > long time i found a good solution. I bought a decent soundcard. Got > cardbus on the laptop? grab an echo cardbus thing. They are cheap on > ebay in the USA. I got my Gina3g from the USA for 200 USD. Pretty damn > cheap compared to a new guitar or bass. If you have firewire you can > try that too after looking what cards work. The cardbus is easier > though. 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. -Chuckk
What do you mean by works really? My previous soundcard was fine for playing mp3s but useless for recording with jack or doing anything without xruns. New card, no problems. Works very well. Loki _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
