M-Audio and Tiger, Computer Hardware Options

[_news_]

Comments about:

M-Audio and Tiger

[macmidiguy]

I've got the M-Audio USB midisport 8x8 midi interface.

It has been my TIGER experience that I need to re-install the "driver" every day because otherwise there is no midi communication between my midi devices and my software sequencers ( e.g DigitalPerformer 4.5.2 ).

When I look at the Audio Midi Setup the midisport/midi devices are greyed out. When I re-install the M-Audio driver all is OK and I get midi communication.

This is rather strange becuase the midisport is an M-Audio product.

I am using the current availbe M-Audio driver.

I sure don't have that problem in Panther.

[fabulousray]

I have a firewire 410, dual 1.8 g G5, OSX 10.4

I just got through talking to the supervisor of tech support at M-Audio and he says the driver updates for Tiger could happen as soon as a couple of days or a week or two. It turns out Apple dropped the ball by giving them a different release of Tiger than the retail release, and so they are having to do regressive testing on the drivers. He assured me they are working as quickly as possible and considers it a top priority.
Since there have been extensive changes in the BSD subsystems of OSX, loading your previous drivers could be a mixed bag.

[macmidiguy]

Thanks fabulousray for providing me that info update.

It sure is a pain in the studio to re-install that M-Audio USB midisport 8x8 midi interface driver.

And if M-Audio could also update the driver for their audiophile 2496 PCI card this guy will be very happy.

[fabulousray]

Hey, no problem macmidiguy, glad to be of service! I think I'm gonna wait for the update or until the new versions of Onyx and Diskwarrior, two very essential mac maintenance utilities, for 10.4 come out. It is very frustating to not have this capacity at my fingertips, as I am sure it is for you and most Tiger users at the moment.[COLOR=orange][COLOR=blue]

[macmidiguy]

I can hardly wait for Diskwarrior 3.0.3 (free download update ) to be issued soon according to their www site and an email I received from their tech guy.

At the moment I am using Cocktail and Macaroni for my daily maintenance plus TechToolPro. So far I have not had to use TechToolPro to rebuild TIGER'S directory.

[cidsinga]

I'm running 10.4 with M-Audio 2496 driver version 2.01 and had no problems at all...

Ce message a été modifié par cidsinga - jeu. 12 mai 2005, 23:16.

[fabulousray]

dual 1.8 G5 Firewire 410 Tiger driver

Go to the website and download Firewire_OSX_1.5, which says on the site is an update for OSX 10.3.8 & 10.3.9, and then open the installer. The installer states this update is good for the OSX versions listed PLUS 10.4 and above. No problems with the driver!!! Works like a dream!
It turns out M-Audio's webmaster must be a total moron, because the website still states the firewire drivers are still in development.

Firewire_OSX_1.5 is the current driver for 10.4 TIger!!!!!!!

[macmidiguy]

And if M-Audio could also update  the driver for their audiophile 2496 PCI card this guy will be very happy.

M-Audio have issued a "Tiger' version for their Audiophil 2496 PCI card and that driver works.

I am still waiting for M-Audio to fix their USB MIDISport 8 x 8 driver. As I noted previously the version they have works if I re-install it every time I want to use my 8 x 8 MIDISport.

Ce message a été modifié par macmidiguy - sam. 28 mai 2005, 03:05.

[mihai]

Firewire_OSX_1.5 is the current driver for 10.4 TIger!!!!!!!

I am using the 1.5 driver with a firewire 410 on a dp2.3 G5 running 10.4.1 with no problems at all.............now if only Steinberg can get Halion player to stop crashing I'll be really happy

[Ideasite]

I have a Firewire 410 and I can tell you that M-Audio does not write good driver code. The device will somehow loose it's connection to they system when there is any other firewire activity. This means that they have not written the driver to standard firewire specs. This is not a bandwidth issue because it happens when other firewire devices are connected to a completely separate firewire port on a firewire card -- not just another firewire port.

Also, firewire has more than enough bendwidth for both audio and other firewire bus activity. As their badly written driver is loosing its connection to the device, it introduces extremely damaging pops into the audio stream. I have had to add a foot power switch just to protect my equipment.

The driver also requires that the system be completely shut off - not just restarted. There is no technical reason for this, other than poor code in the driver. In unix, any process can be restarted on the fly, including core audio and the firewire driver. Due to errors in the driver, firewire bus power must be cycled to the Firewire 410 to re-boot it's internal code before it will re-connect to the CPU.

In addition, changes to the volume using the keyboard take about 3 seconds per level to happen. What on Earth, other than bad code, should cause this kind of delay on a G5 2.5 mHz machine with 8 gig of RAM?

This is inexcusibly dumb and downright dangerous. M-Audio states that no manufacturer can predict what new versions of operating systems will require, but any manufacturer can get the specs for the Mac OS, core audio and firewire, without a large investment, and write suitable driver code. M-Audio has simply failed in this regard.

The Firewire 410, and the rest of the drivers should stay connected, allow hot swapping of devices, not introduce unecessary pops in the audio stream. M-Audio is letting us all down if they can't achieve this simple set of goals for their products.