Page 1 of 1
Follow up on 10.4.10 audio problem (temp fix)
Posted: Mon Jun 25, 2007 11:13 am
by MIDI Life Crisis
Posted: Mon Jun 25, 2007 5:28 pm
by HCMarkus
Thanks MIDI... but these words at the bottom of the referenced URL gave me pause:
FireWire device problems A number of users are reporting FireWire device issues (lack of recognition, funcitonality lost) under Mac OS X 10.4.10.
One reader writes:
"My FireWire Behringer FCA-202 is no longer working under the updated system. Hope the fix it soon, so I can start recording again.
René adds:
"I recently installed Mac OS X 10.4.10 and my firewire audio interface card stopped working (It's a Mackie Onyx Satellite)."
Posted: Mon Jun 25, 2007 5:37 pm
by MIDI Life Crisis
Yes indeedy! I cannot tell you how many times I have upgraded the OS only to loose my M-Audio FW device.
Posted: Tue Jun 26, 2007 3:19 pm
by mhschmieder
This is dishearetning, as I had looked forward to 10.4.10 stabilising these issues finally.
I guess it's a good thing I didn't know about 10.4.10 before reading this forum again today. I'll definitely hold off on the upgrade.
Posted: Wed Jun 27, 2007 10:14 am
by MIDI Life Crisis
Posted: Wed Jun 27, 2007 11:56 am
by Resonant Alien
One thing I love about the RME Fireface. They write their own firewire drivers and are not as much at risk from OS upgrades as the guys that rely solely on Core Audio.
Posted: Thu Jun 28, 2007 3:51 pm
by kelldammit
for the record, on a clean install, everything went fine here, including ilok installs. traveler drivers seem to be working fine, too...
Posted: Thu Jun 28, 2007 10:49 pm
by cuttime
OK, I finally took the X4X plunge, and I've tried and tried to duplicate the said audio problems (pops, speaker power-downs, firewire interface breaks) and I can't. This leads me to believe that this is an Intel issue only, as I am running PPC. Anyone having these problems (as of X4X) on PPC platforms?