Does anyone (Steve?) have any ideas what I could try - it is driving me balmy and I have even started thinking (vaguely) about rebuilding my machine with a clean disk, but I don't really want to.
I should start out by saying that even though I've got a Mia, I've never run it with AA2.0. Come to that, I haven't even run it with 1.5; it's on the oldest machine of the lot which still uses... wait for it... Win ME! I really ought to do something about this, I know, but it's not exactly urgent because there are plenty of other MOTU and E-mu devices around for the other machines.
But I'll tell you something weird about OS's and Audition. The laptop went in for a video card repair, and I sent it off with a blank spare HD in it - didn't want to send it off with the original disk because I didn't want HP to screw it up. Machine came back working fine, and HP had installed a fresh XP OS on the disk I'd supplied - you'd think that this was a cheap way of getting a new OS, but the cost of the repair means that it doesn't
quite seem like it... So, I put the original (worked fine before) disk back in the machine, and suddenly had the whole thing slow down by a staggering amount, and this was rather more noticeable with Audition than anything else loaded on the disk.
This isn't actually a problem - I've reinstalled everything on the new (larger) HD, but I am still speculating about what causes the massive slowdown on the other one. The obvious thing that's changed is everything to do with the video system - HP have done a hardware change here, not just a replacement. The old driver works still, and
claims to be the right one, but I'm not so sure.
I can't preclude AA here - it's definitely sensitive to something going on. But I don't think that it's Audition
per se that has the problem - it's the relationship that it has with some other part of the OS (like the video driver?) that appears to be causing the bottleneck. But I can't prove it. If you do benchmark tests, the entire machine runs slower with the 'old' OS, and this really doesn't make a lot of sense - the OS's are essentially both the same, being XP Home with the same build state. But the effect on Audition is rather more marked than it is with anything else.
I'm also open to suggestions/conjecture about this, although I'm not likely to implement any ideas thrown up, because I don't need to. I
would like to know what causes it though, and what it is about Audition that makes it so sensitive to the machine state, just for future reference purposes. I'm guessing that there are going to be registry entry differences, but as to what they entail or alter, I really don't know. Trying to get more information out of HP is a non-starter. I believe that the shipping state of Audition has any potential OS optimisations for different processors turned off, so it's unlikely to be caused by anything like this. And I wouldn't recommend turning them on either - this would probably cause more stability problems.
I'm still going with some sort of PCI bus bottleneck here, and I'm also still
very suspicious about the video card driver...