Problem Alesis MultiMix16 FireWire

Posted on

Member Since: Jan 03, 2009

Hi all,

I have a major problem with my newly purchased Alesis MultiMix16 FireWire.

I use Windows XP SP3 and Sonar 6 Producer Edition. I also had a Creative Soundblaster installed and I have disabled the on board sound card.

I downloaded the latest drivers and firmware from the Alesis website and installed everything.
That went as expected, the device could be selected in the Sounds and Audio Devices dialog as described in the manual. It was selectable in Sonar as well. Unfortunately when using Sonars build in midi sounds I couldn't select the MultiMix as the output device. Selecting the Soundblaster here obviously resulted in not hearing these tracks in the return signal on the MultiMix. Trying to solve this I apparently screwed up some things because I can no longer select the MultiMix in the Sounds and Audio Dialog in Windows. The removal of the Soundblaster and uninstalling and reinstalling the MultiMix drivers haven't changed anything either.

So now I'm not able to record anything. I have an audition coming up and I use this setup for practicing the songs as well.

Any help would be greatly appreciated.

Grtz,

Nico.

[ Back to Top ]


Member
Since: Jan 03, 2009


Jan 03, 2009 06:57 pm

First of all Alesis Multimix 16 Firewire it not working on Windows SP3. I had the same problem.
Reinstall the system using Windows SP2, than you need to add two more hotfixes from microsoft.
Windows Installer 3.1 - you can download it from here:
www.microsoft.com/downloa...;displaylang=en

and performance of 1394 devices from here:
www.microsoft.com/downloa...;displaylang=en

Now you can do a clean install of all your drivers but for alesis multimix 16 use the updated drivers from alesis.com.

I have a multimix 16 firewire and it work excellent now. I have a couple of questions about midi connections but maybe these days we can talk.

Good luck.

Czar of Midi
Administrator
Since: Apr 04, 2002


Jan 03, 2009 09:36 pm

Hey jakman, thanx for that. This is the second time I've seen this now and that seems to be the solution. I'm surprised that Alesis has yet to have a fix for it yet.

Related Forum Topics:



If you would like to participate in the forum discussions, feel free to register for your free membership.