How to uninstall ancient Multimix driver? (Mac)

[woodman]

I know this is a long shot as far as getting an answer, but I've boxed myself into a corner here with my Alesis Multimix Firewire interface/mixer. I disabled the interface a couple of years ago when I got Pro Tools and was forced to use an Mbox USB1 interface (although I continued to use the mixer component of the Alesis). I'm working in Logic now and don't plan to go back to PT, so I want to ditch the Mbox and reinstate the Multimix Firewire.

After several unsuccessful attempts to install current MultiMix12 driver/firmware on my iMac (10.6.8), I got desperate and tried installing the driver from the CD that came with the unit (1.1d9.pkg) — a stupid move as it turned out. ... It installed, but my system informs me it won't run on an Intel machine — but there's no uninstaller on the CD, and the uninstaller for the current driver won't get rid of it.

The Alesis site warns that drivers past a certain age must be removed by a third-party uninstaller. I found an Alesis doc online recommending DesInstaller for problems like this, but it must be outdated — I downloaded DesInstaller 3 beta, but it won't work on this system (this version dated back to 2006).

The old driver shows up in my prefs' "Other" pane, but not in the "Sound" pane, nor in Audio MIDI setup. A system search reveals nothing under "Alesis" or "Multimix," so the driver file corresponding to the icon in the Prefs pane is probably buried in a folder somewhere with an arcane name.

Any ideas on how to root it out and get rid of it? The Alesis site had suggestions for Windows uninstallers, but none for Mac that I could find.

[ScatMan]

Might try going to Macintosh HD-->System-->Library-->Extensions and see if there is a file named Multimix, Alesis, etc.

..Or if it doesn't have an obviously named file, maybe check Date Modified. This might give a clue as to what file is what.

I use a Focusrite Saffire Pro 40 interface, and the driver (Saffire.kext) is in that folder.

[woodman]

Originally Posted by ScatMan

Might try going to Macintosh HD-->System-->Library-->Extensions and see if there is a file named Multimix, Alesis, etc.

..Or if it doesn't have an obviously named file, maybe check Date Modified. This might give a clue as to what file is what.

That's exactly what I did — dug into ALL the Libraries and found a half-dozen Alesis/Multimix files. Some were from the old driver but others from more recent installation attempts of the current driver. So much for the Alesis uninstaller! In the process, the Multimix icon disappeared from the Prefs pane.

What I don't get is why none of these files showed up in a Finder search ...

[ScatMan]

Originally Posted by woodman

That's exactly what I did — dug into ALL the Libraries and found a half-dozen Alesis/Multimix files. Some were from the old driver but others from more recent installation attempts of the current driver. So much for the Alesis uninstaller! In the process, the Multimix icon disappeared from the Prefs pane.

What I don't get is why none of these files showed up in a Finder search ...

Yeah, the finder won't search some folders. Don't know why, maybe some Mac gurus could explain.

As far as deleting the driver, I did an experiment on my end

I moved my driver file (Saffire.kext) to the trash and rebooted. Communication with the interface was disabled (opened a Logic project and got a message to the effect: "the previous audio interface is no longer available").

I then restored the file back to the folder I mentioned in my first post and rebooted. Communication with the interface was restored.

Another thought regarding your interface (you might have already tried this): Go to applications-->Utilities and launch Audio MIDI Setup. Does the Alesis show up as an option?

If so, check that "Use this device for sound output" is selected.

[woodman]

Scat, after getting the old crap outa the way, I tried to install the current driver (after first running uninstall) and jumped through all the Alesis hoops, even unplugging the computer to make sure Firewire is reset. ... Nothing in the Prefs pane, System Profiler's Firewire window, or Audio MIDI Setup window. But beyond that ....

* AlesisFirewire.kext is showing up in HD>System>Library>Extensions
* AlesisFirewire MIDIDriver.plugin is showing up in HD>Library>Audio> MIDI Drivers
* AlesisFirewire.startup appears in HD>Library>Preferences

So it's clear that new stuff was installed, but it's not translating systemwide. (One notable absence: there was previously a Multimix Drivers file in HD>Library>Startup that hasn't reappeared.) ... Extremely frustrating. In days of searching the Web for solutions, it's clear that Alesis drivers are infernally undependable — driver issues are commonplace.

This is an older unit (bestowed on me almost four years ago by our pal Getbent), and I wonder if I should try installing an older driver, like the first one updated to support Snow Leopard (my current system).

[Geoff738]

Woody,

I'd make sure you have the latest software updates and anything else you can pull off the Alesis site to get your interface current. And then restart the Mac and see what happens.

Basically, I'm advocating for restarting pretty much any time you make a change - and see what does or doesn't happen.

Hope you can get it up and running.

Cheers,
Geoff

Originally Posted by woodman

Scat, after getting the old crap outa the way, I tried to install the current driver (after first running uninstall) and jumped through all the Alesis hoops, even unplugging the computer to make sure Firewire is reset. ... Nothing in the Prefs pane, System Profiler's Firewire window, or Audio MIDI Setup window. But beyond that ....

* AlesisFirewire.kext is showing up in HD>System>Library>Extensions
* AlesisFirewire MIDIDriver.plugin is showing up in HD>Library>Audio> MIDI Drivers
* AlesisFirewire.startup appears in HD>Library>Preferences

So it's clear that new stuff was installed, but it's not translating systemwide. (One notable absence: there was previously a Multimix Drivers file in HD>Library>Startup that hasn't reappeared.) ... Extremely frustrating. In days of searching the Web for solutions, it's clear that Alesis drivers are infernally undependable — driver issues are commonplace.

This is an older unit (bestowed on me almost four years ago by our pal Getbent), and I wonder if I should try installing an older driver, like the first one updated to support Snow Leopard (my current system).

[woodman]

Originally Posted by Geoff738

Woody,

I'd make sure you have the latest software updates and anything else you can pull off the Alesis site to get your interface current. And then restart the Mac and see what happens.

Basically, I'm advocating for restarting pretty much any time you make a change - and see what does or doesn't happen.

Hope you can get it up and running.

Man, I've spent two days on the Alesis site and tried the install for the current driver at least six or seven times (mandatory restart after installation), each time trying to follow the prescribed ritual. It's been maddening. ... Some of the info on their site is obviously outdated (like the DesInstaller link) so it's hard to figure what the straight story is. Tomorrow I'll try to get somebody on the phone and see how that goes.

This mixer's like an old friend now and I'm not gonna give up until every stone is turned. The hell of it is, the interface worked great before the Digi era, and now I can't even get a driver installed.

[ScatMan]

Hope the customer tech support works for you.

[woodman]

Wrangled with it all morning and got an installation where the driver installed, visible in the Extensions library as well as the Extentions window in System Profiler. The control panel shows up in Applications, and Audio MIDI Setup shows the MIDI driver but no audio driver. It's not showing up in either Prefs pane or the Firewire window of System Profiler.

So, thinking I was making progress, I called Alesis tech support. After 25 minutes of music I'd never have heard otherwise, a real person picked up and asked me what product, etc. and what was the problem. I began to explain what was going on, but before I got through my second sentence, he interrupted with, "It's a hardware problem." Each time I would start a counterargument, he'd interrupt again with, "Hardware problem." I asked him about the widespread issues with Multimix drivers all over the Internet and he said all those were hardware problems too.

By this time steam was coming out of my ears. I asked if he could explain the proper sequence for installation (per their Web page) and he said that didn't matter — you should be able to install and it should just work — unless of course you have a hardware problem. Obviously the guy didn't know jack-***** and is getting paid to answer the phone and tell everybody it's not his problem. With bitter sarcasm I told him "Thanks for your HELP" and hung up.

I don't think I've ever been stonewalled that hard in a tech-support call. Usually they at least let you explain your problem before blowing you off. So after three wasted days, guess I'll hook the Mbox back up til I can figure a better interface solution. I'll continue to use the mixer portion, because it's a great unit — but their software/firmware writers and tech support SUCK! Man, I'm still steamed!

[ScatMan]

Tech support..I've had just as many pleasurable experiences as nightmares!

Did he even try to explain what he meant by "hardware problem"? Computer? Multimix?

I've read of problems with firewire device/computer firewire chipset compatibility, but I have no personal experience.

Some I've read say the problem was with non - TI (Texas Instruments) firewire chipsets in their computer.

Maybe wouldn't hurt to check what you have: Hold CMD+s while booting up. Down the list it will read: FireWire (OHCI) with the chipset manufacturer right after.

[Geoff738]

That sux.

Is the Mbox still installed all through this?

In the audio/midi setup folder, click on audio on the top. What does the aggregate devices editor tab show?

I went through something that sounds kinda similar when I had an Mbox (funnily enough), but I can't remember what the solution was. I do remember I couldn't put the Mac to sleep because I'd have to restart it again for it to recognize the cursed thing.

Cheers,
Geoff

[woodman]

Originally Posted by Geoff738

Is the Mbox still installed all through this?

In the audio/midi setup folder, click on audio on the top. What does the aggregate devices editor tab show?

The Mbox software was still installed, but the box was physically disabled from the system (unplugged from USB and the mixer). The Audio devices showing are Built-in Microphone, Built-in input, Built-in Output, and Digi CoreAudio Device (0 in/0 out). I think I'm pissin' up a rope here.

[getbent]

sorry to be late to this wood!

you should not have to uninstall the old driver... one thing you may want to try is to make sure that the interface is NOT connected when you try to install the driver.

Wait until the installer calls for the device (it may not) if it does, connect it then...

If that doesn't work... the tech support guy may be right and the 1394 part of your multimix has gone titsup... it happens... that thing is getting long in the tooth...

and..... alesis doesn't make firewire stuff anymore, so, they aren't still engineering for it....

wish I was closer, I could dink with it and if it could work, I could make it happen...

My multimix died about a year ago... there are repairs for noisy multimixes, but if the 1394 goes... it is a little mixer only...

[woodman]

Originally Posted by getbent

sorry to be late to this wood!

you should not have to uninstall the old driver... one thing you may want to try is to make sure that the interface is NOT connected when you try to install the driver.

Wait until the installer calls for the device (it may not) if it does, connect it then...

If that doesn't work... the tech support guy may be right and the 1394 part of your multimix has gone titsup... it happens... that thing is getting long in the tooth...

and..... alesis doesn't make firewire stuff anymore, so, they aren't still engineering for it....

wish I was closer, I could dink with it and if it could work, I could make it happen...

My multimix died about a year ago... there are repairs for noisy multimixes, but if the 1394 goes... it is a little mixer only...

I had no clue about Alesis being out of the Firewire game ... explains a lot.

As you say, this unit's getting along in years — I've used it for four years and you probably used it a couple of years before that. But the mixer itself has been an invaluable component of my operation and I'll keep using it until it bites the dust (or I get rich, whichever comes first).

For now, guess it's back to the USB1 Mbox, but I'll be looking ahead at something like the Presonus Firebox Mobile ... small enough to fit in the friendly confines of the Woodshed, but from most accounts has decent pre's and converters. I would patch it through the Multimix Alt 3/4 bus as I've done with the Mbox.

You mentioned repairs for noise issues ... could you go into that a little?

[vjf1968]

Woodman, did you check Time Machine and restore the computer to the point before this journey started? Just a shot in the dark.

[woodman]

Originally Posted by vjf1968

Woodman, did you check Time Machine and restore the computer to the point before this journey started? Just a shot in the dark.

This iMac's fairly new (less than a year) and the last time I used the Multimix interface was two computers ago. Since the system-related stuff installed but it's not being seen by the Firewire bus, I'm thinking Getbent may be right in that the 1394 component gave up the ghost.

[Geoff738]

Originally Posted by woodman

This iMac's fairly new (less than a year) and the last time I used the Multimix interface was two computers ago. Since the system-related stuff installed but it's not being seen by the Firewire bus, I'm thinking Getbent may be right in that the 1394 component gave up the ghost.

Sorry Wood - looks like that's three days of your life you won't get back. (Sorry for recommending that you give it a try.)

If we're going back to the previous set-up, lets see if we can figure out if there is a feedback loop in there. And how to fix it.

Cheers,
Geoff

[woodman]

Originally Posted by Geoff738

Sorry Wood - looks like that's three days of your life you won't get back. (Sorry for recommending that you give it a try.)

If we're going back to the previous set-up, lets see if we can figure out if there is a feedback loop in there. And how to fix it.

That's what I'm working on (the studio still isn't fully back up) ... sometimes if you tear a system down and put it back together again, you get lucky. But it sure has been instructive to listen to some of my mixes through the iMac's built-in speakers! That's been a weak link in my translation process, and from now on I'll listen to every mix through those cheese-eating speakers. They really identify those annoying highs.

But as for the three days, I figure I fought the good fight and lost honorably. Lessons learned. Gotta count your blessings, or else beat your head against the wall.

[64Strat]

Woodman, I've been following this thread with interest. Sorry it has been such a pain! I'm not a Mac guy, so I couldn't offer any advice. But my takeaway is that the noise floor we heard in the songs was not the two wire AC power like originally thought but some sort of interference from the audio interface or a feedback loop in the system. I hope you get it resolved successfully!

[getbent]

the noise has nothing to do with the computer. The noise is from the alesis itself...



I've fixed several of these, they just seem to go over time.

that may solve one of your challenges.