Re: [linux-audio-user] Tracking down overruns

I'm glad to meet you. I've been playing with Pro Tools since 4.3.1, and my studio is running currently running MIX plus on an old beige G3/300 running MacOS 9. I've often wanted to migrate over to Windows, but we'd lose all of our plug-ins. Pro Tools is actually one of my biggest motives for moving to Linux - one gets tired of jumping through flaming hoops every time DigiDesign or Apple release new hardware or software. Well...I *do* have a third drive hooked up to the Promise controller, but upon installing it, I discovered that my power supply doesn't want to supply power to another drive - even though I have enough power hookups. I can only use the drive if I disconnect power from my LS120, CD-ROM or Windows hard drive. Time to buy a new power supply.... I'm running Blackbox - we seem to be cousins. For what it's worth, I've also posted my XF86Config: http://www.comevisit.com/NorthernSunrise/latency/XF86Config It has a few things I need to fix, but nothing that I think would affect audio performance. My machine is absolutely adamant that the sound card *has* to go there :( I spent many frustrating and fruitless hours trying to address this issue. I sifted through every single BIOS setting, juggled the cards all over the place, but the only way I could get the card off IRQ 5 was by disabling that IRQ. When I did this, it moved the card up to IRQ 4, and so on. In short, my machine *always* gives the sound card the lowest-priority IRQ, and provides no way (that I could find) to assign IRQs manually. Ultimately, I put things back as they were, and decided to be more careful next time I buy a board. I *might* be able to force it to share an IRQ with something else. Would this be worth tampering with? Since I wasn't ready to use it, I don't think I built drivers for it when I built the kernel. Might this explain the discrepancy? Also, I've done quite a bit of scouring around for information on disk cache settings. Mostly, what I find are messages asking how to set a maximum disk cache size, followed by silence, or by replies saying not to bother with it. Often the discussion quickly descends into a debate about the soundness of Linux's VM system, with the original question about the disk cache system being ignored. I did find a patch by Rik van Riel (http://surriel.com/patches/2.4/2.4.20-rmap15c) which appears to provide sysctl parameters for cache size restraints, but I'd have to download and build a 2.4.20 kernel, downgrade my module utilities, etc. Even if something else is causing my overruns now, I certainly suspect that real-time performance could be enhanced by a bit of cache settings tweaking. If anyone has any info on doing this with a 2.6.test5 kernel, I would love to get it. My curiosity has been awakened :) Thanks again for the continued help! |) |)enji Benjamin Flaming -------------------- "The trouble with computers, of course, is that they're very sophisticated idiots."