Sick Of M-audio Fw410, aaarrgh!! Options

[eMpTy]

Once again M-Audio comes out with a crap driver for the FW410, I am getting so sick of this.

So I install the new driver thinking it is going to rectify the not able to wake up problem, first thing I do is open the panel check to see the driver number then go to load a saved set and as soon as the load button is pressed some crash notice comes up with a file location and some other stuff. So I go to open Grab to get a screen shot, switch back to the FW410 Panel using TAB+Command and as soon as I touch the screen I get an OS crash with the multi language white writing on a black background.

I am so annoyed by M-Audio and the problems I have had with this product from day one, CDs that didn't work, crashed OSX multiple times, not working as advertised and shit driver after shit driver.

I will try not buy any of their products again and I hope you don't either for your sake.

Sorry to be so negative but it is too much already.

This post has been edited by eMpTy: Mon 12 Jul 2004, 03:13

[fictionmusic]

Well I kinda agree....I have had nothing but problems with the firewire 410. Lately I have been wondering if it wasn't the spdif ins that were giving me trouble (coming from a TC Finalizer) but even still it crashes logic and I get core audio messages quite a lot. Their support has been pretty good though and they get in touch in a day or 2 but all in all I won't be in a big hurry to buy any more interfaces from them.

At least now I can switch sample rates in Logic without the 410 crashing everything

[stoprunner]

I've just downloded the new driver, but reading your post doesn't encourage me to update, since I've had so many difficulties for a while with my 410. It's been running strong for a couple of weeks now, and seems to work fine, I would think three times before updating. Still, my powerbook is "electrified" by the bus powered 410 with my external drive attached to it. I'll keep on eye in your developments eMptY

[sethjacquay]

After the 1.2.2 updates, I did this because I upgraded
to 10.3.4. I had a two kernel panics in a row,
but for whatever reason that all seems to have went away.

Now on restart everything boots up fine.

I haven't had any problems for about three
weeks now and the FW-410 is working like a charm!

[Merlind]

Never had any problem with the Firewire410…
Hope it's gonna stay that way.

Powerbook G4 1,25 Ghz, 1GB RAM, OSX 10.3.5, DP4, MACHFIVE…[COLOR=blue][I][SIZE=1]

[twain]

I agree the 410 has loads of problems. For me it's massive latency. I don't have the best computer in the world, but I'm sure it's mainly the 410. For example if I use the ozone instead the latency is much much better. I hate the ozone as well though, since it has a very strange tendency to cut out and not transmit sound, which then recquires me to restart not only the ozone but the program I'm running.
These are definately the last 2 m-audio products I buy. Several other people macs I know have the same problems, but yet most people seem to agree that their drivers are great for PC's. Apparently they just don't give a shit about properly developing drivers for macs.
This whole thing sucks though, now I feel like I'm wasting my time screwing about with the 410, and might as well go ahead and buy a new AI, but I don't really have the money since I've already wasted so much on m-audio.

[Marcao]

I agree the 410 has loads of problems. For me it's massive latency. I don't have the best computer in the world, but I'm sure it's mainly the 410. For example if I use the ozone instead the latency is much much better. I hate the ozone as well though, since it has a very strange tendency to cut out and not transmit sound, which then recquires me to restart not only the ozone but the program I'm running.
These are definately the last 2 m-audio products I buy. Several other people macs I know have the same problems, but yet most people seem to agree that their drivers are great for PC's. Apparently they just don't give a shit about properly developing drivers for macs.
This whole thing sucks though, now I feel like I'm wasting my time screwing about with the 410, and might as well go ahead and buy a new AI, but I don't really have the money since I've already wasted so much on m-audio.

Hi Twain, I have a FW-410 running Pro-Tools on an Athlon 64-x2 pc and basically I have only problems :

1- I have severe latency when recording audio in Pro-Tools and I just can't find an answer to whether this problem has a solution or not,

2-The TS instrument plug goes easily inside the front panel input but I have to use some strentgh to pull it out


Has anybody found a solution for this problems

[kactus]

Hi,

I've had the FW410 for 4 years, is my main audio interface, i did a lot of gigs with it and everything always worked. In studio situations, the FW410 is connected to FW port of PBG4 Titanium 867, and i've a couple of FW hard drives and a DVD recorder all daisychained through the FW410, and still no problems, i've updated the drivers anytime M-audio puts a new one. Working in Mac OX 10.4.1.
There's was time when I did a lot of SPDIF transfers from a Tascam DAP-1 portable Dat, and even then no problems. Sometimes I work with complex setups live (I ususally work with MAX/MSP - in studio I also work with Logic, ProTools, Peak...), for instance receiving a SPDIF Stereo signal and a analog stereo signal at the same time, manipulated both signals and send them trough outs 1-2/3-4 to the PA, and using 5-6 to feed a dry mix of the 4 channels into another laptop, all very smoothly with no problems.

I like it, but nowadays there are more interesting interfaces, with more ins and smaller size and price,
when I bought it there was only 2 FW interfaces in the market this one and a really "Beast" the Metric halo,
but it was a rack size interface, so hard to carry around in gigs.

CS