Mac OS X just hit 10.3.8, but I'm still having problems with changes introduced in 10.3.7:
M-Audio interfaces' latest drivers appear to cause incompatibility with
the new OS; my Duo and FireWire Solo both stopped receiving and sending
audio signal (though they appear normally) after the update. With the
Solo, rolling back to the previous driver version 1.4 (also on the
M-Audio site) fixed the problem, though with the Duo I'm stuck for the
moment. (There's a trick to getting the old version: when looking for
drivers on their site, don't specify your OS, just your hardware.)
I'll update you if I learn anything — other audio hardware here at CDM HQ appears to be unaffected.
At least all those Windows XP security updates aren't doing anything.
10.3.7 broke compatibility with my Digigram VXpocket 2 cardbus card (distortion in the input sound). 10.3.8 did not help. I’ve filed a report to Apple Bug Reporter and Digigram (which says that it’s Apple’s fault). [Ken Gee, CANADA]
10.3.7 forced me to reinstall the drivers for my Audiophile 2496. The 1.1.8 version (see VersionTracker) works, but I had to install it with extensions off as an admin user. This has happened before when I was on Jag occasionally, but it had been a while. MAudio just doesn’t have their stuff together. BTW, 10.3.8 breaks nothing, so if you survive 10.3.7, you’re good to go.
The main that took M-Audio out of the running for my recent interface purchase: drivers. I’ve heard repeated horror stories (and more than a few) about incompatibilities and instability. Even if the devices sound good, at a great price, you can’t use them without good drivers. As “Guest” said above, M-Audio just doesn’t have it together in this department.
I experienced the same problem with an Ozone on a PB 1.67. The 10.3.8 update seems to have fixed the problem.
no problems on 10.3.7
but i think the drivers could be much better. if i use a motu interface i get 64samples latency if i use a m-audio i have to use 512samples to run the same project 🙂