Firewire 410 Mac Users Read this

tribalogical · Post by **tribalogical** » Fri Jan 14, 2005 9:29 am

I suspect the driver update also does some kind of update to the hardware (flash ROM update or something?)..... my PC-using friends have also said the LEDs behave differently now.

Note: M-Audio does say that the new Mac driver is tested ONLY up to OSX 10.3.6, and they are still testing under 10.3.7....

So who among you (experiencing these weird problems) installed the new driver to OSX 10.3.7...?

And, is anyone here using 10.3.6 or prior with the new driver? Are you also having the same problems??

I'm not reverting my OS (I'm running 10.3.7)... so I'm not touching this driver update until M-Audio gives the 'all clear'.....

peace,
tribalogical

zeropoint · Post by **zeropoint** » Fri Jan 14, 2005 10:08 am

My firwire LEDS behaved differently when 1.4.1 was installed.....but now they're back to normal.....haven't noticed anything else to be honest.

xzusa8ky · Post by **xzusa8ky** » Fri Jan 14, 2005 5:02 pm

Hi!

After installing M-Audio Firewire 410 Driver 1.4.1 on my G5 1.8 Ghz I doent have any Midi anymore and I think that the driver is not tested from M-Audio? Shame on you M-Audio! I've gonna go back to 1.2.2 its running stabil!

Regards xzuas8ky

zeropoint · Post by **zeropoint** » Fri Jan 14, 2005 5:22 pm

tribalogical wrote:I suspect the driver update also does some kind of update to the hardware (flash ROM update or something?)..... my PC-using friends have also said the LEDs behave differently now.

Note: M-Audio does say that the new Mac driver is tested ONLY up to OSX 10.3.6, and they are still testing under 10.3.7....

So who among you (experiencing these weird problems) installed the new driver to OSX 10.3.7...?

And, is anyone here using 10.3.6 or prior with the new driver? Are you also having the same problems??

I'm not reverting my OS (I'm running 10.3.7)... so I'm not touching this driver update until M-Audio gives the 'all clear'.....

peace,
tribalogical

10.3.3 tested here......same problem....

masturfader · Post by **masturfader** » Sat Jan 15, 2005 12:07 am

damn, i was hoping theyd fix the cpu usage issues javascript:emoticon(':x')

tribalogical · Post by **tribalogical** » Sat Jan 15, 2005 6:14 pm

mammalux: 10.3.3? Getting a little long in the tooth, isn't it?

Well, in any case that sux..... I guess the new driver is still really a "beta" then...

I felt a bit miffed that the "fix list" didn't include LATENCY on the Mac update (only on the PC side).... That's about my only real issue with the 410... otherwise, it's great. But I've been waiting (and waiting) for M-Audio to get the latency fixed. I'm looking real hard at alternatives right now. >10ms latency is just not working for me.... That little red Edirol (FA-101) is sure looking tempting these days.....

Anyway. thanks for the info!

peace,
tribalogical

chrysalis33rpm · Post by **chrysalis33rpm** » Sun Feb 06, 2005 4:48 pm

I felt a bit miffed that the "fix list" didn't include LATENCY on the Mac update (only on the PC side).... That's about my only real issue with the 410... otherwise, it's great. But I've been waiting (and waiting) for M-Audio to get the latency fixed. I'm looking real hard at alternatives right now. >10ms latency is just not working for me.... That little red Edirol (FA-101) is sure looking tempting these days.....

Yeah, me too I am looking at the FA-101: So does anybody know what kind of latency it actually gives?

3phase · Post by **3phase** » Sun Feb 06, 2005 7:38 pm

I went back to Osx 10.35 just to give the new driver a fair try...the old one sucks...but the new one sucks more... there is no good syncing from Live to an external clock with the 1.41 driver...
1.24 has at least a good timingstability... and horrible latencies and dropouts from time to time when asking for too much...like simultaniously recording of 4! tracks

...