Why does the Alesis iO26 FW driver disappear in the Sounds Control Panel?

Question

Why does the Alesis iO26 FW driver disappear in the Sounds Control Panel?

After installing and selecting the Alesis iO26 Firewire DAW in the Sounds Control Panel, the Alesis option suddenly disappears after a while for no apparent reason, so und and all that shows is the Realtek device. The Device Manager says the Alesis is jut fine, and I can bring up the Alesis Mixer and monitor my inputs. However, the windows OS thinks Alesis is gone! Deleting and re-loading the Alesis driver does not fix the problem.

I don't know if this is a "Windows XP PRO on a Mac" problem or an Alesis problem. I did verify that the registry is pointing to the proper location of the Alesis driver, as that is a bug in the current Alesis driver. This is driving my nuts!

Macbook 2.4gig Penryn w/4gig memory, Hitachi 200gig 7200rpm hd WinXP Pro, Leopard 10.5.2 & Windows XP Pro via BootCamp

Posted on May 25, 2008 4:34 PM

Reply

Answer 1

adriasca

Level 1

24 points

May 26, 2008 4:35 AM in response to Richard Van Nostrand

Hi Richard... this is the same problem I've found in this topic (search it) "Firewire Edirol FA-101 recognize like 61883 device"...
The Edirol FA-101 (an Audio device like your) don't work in Windows under Boot Camp with Apple Mac Pro Hardware and his drivers installed...
Your post is to conferm that Apple hardware has big problems with Firewire 1394 peripherals.

Like you, I can't find in Sound Control Panel the detailed list of the Audio device of Edirol FA-101 (4 analog stereo channel IN, 4 analog stereo channel OUT and 2 stereo channel SPDIF).

I thing this is to demonstrate that Apple drivers had to be update regarding the Firewire management.

Now I'll open a post to ask this update to Apple (If you agree).

1 Firewire problem could be a Windows responsibility... BUT 2 Firewire audio peripherals...

Reply

Answer 2

May 26, 2008 10:15 AM in response to adriasca

Thanks for your reply. Yes- please go ahead and notify Apple that this is probably a "Windows XP Pro running on a Mac" related problem. It's interesting that you experienced this using the FA-101. I just deleted my Alesis iO26 1394 Firewire device and installed the latest FA-101 driver. I have Audio out but no Audio in in Windows XP Pro. This problem happens in both SP2 and SP3. I did install the WindowsXP-KB885222-v2-x86-ENU.exe hotfix for the SP2/1394 problem with no success in fixing this problem. Very strange, as the FA-101 is rock solid on my other gear. And, of course it works perfectly in OS X Leopard.

Regards-

Richard

Reply

Answer 3

May 27, 2008 5:00 PM in response to adriasca

Here is another part of the puzzle. I returned my Alesis iO26 audio interface to the dealer, who graciously took it back even though I have had it for 9 weeks. I bought another 1394-based Firewire audio interface (at double the cost)- a MOTU Traveler. I installed the software drivers in Mac. The Mac side worked flawlessly.

I booted into Windows XP Pro, installed the drivers, and the audio interface worked as it should. I recorded 8 tracks of audio from my ADAT via light pipe using SONAR 7. The audio was perfect- all 8 tracks played back without any glitches.

I restarted the laptop (still in XP) and the MOTU interface had disappeared! I was back to the RealTek audio interface again.

This time, I went into the Device Manager and disabled the OHCI Compliant IEEE 1394 Host Controller, restarted the laptop, enabled the Host controller and the MOTU audio interface suddenly returned- fully operational.

This does NOT sound like a WinXP problem because the MOTU Traveler has been around for a long time and is very stable.

Don't know if this helps, but it sure points to a problem with Apple's implementation of it's Boot Camp drivers.

This, coupled with the fact that the RealTek audio driver generates 25 .bin files (such as Arabic.bin, Czech.bin, Danish.bin, and others) in c:/Documents and Settings/'username'/Local Settings/Temp every time it runs.

Many thanks

Richard

Reply

Answer 4

adriasca

Level 1

24 points

May 27, 2008 5:07 PM in response to Richard Van Nostrand

I agree with you... AND THIS IOS A REALLY SEVERE PROBLEM REGARDING APPLE (the problem is on APPLE SIDE).

So, I want to repeat what I've discovered right now... a very strange thing... cpuld it be an Apple driver problem regarding REALTEK hardware (that is Apple hardware)...
This is what I've found...
OK my friends... I've a news.

I've found that when the installation proccess is going to finish there are some things that should be added in System Startup global entry but "somethings" makes that will not be able to be added anyway.

I've have an idea, but I don't know that could be true... is there a possibilities that REALTEK DRIVER makes a check about new changes in the Sound Control Panel and "roll -back" to a certain condition, deleting new entry in the System startup?

So, this is what Ive found:

(1) ---------------------------------
Change done by the Edirol installation process (it could be this way): value "MSPQM" (new data: "rundll32.exe streamci,StreamingDeviceSetup {DDF4358E-BB2C-11D0-A42F-00A0C9223196},{97EBAACB-95BD-11D0-A3EA-00A0C9223196},{ 97EBAACB-95BD-11D0-A3EA-00A0C9223196}")
But it has deleted by "something": value "MSPQM" (new data: "")

(2) ----------------------------------
Change done by the Edirol installation process (it could be this way): value "WDM_SPLITTER1" (new data: "rundll32.exe streamci.dll,StreamingDeviceSetup {2F412AB5-ED3A-4590-AB24-B0CE2AA77D3C},{9B365890-165F-11D0-A195-0020AFD156E4},{ 6994AD04-93EF-11D0-A3CC-00A0C9223196},C:\WINDOWS\INF\WDMAUDIO.inf,WDM_SPLITTER.I nterface.Install")
But it has deleted by "something": value "WDM_SPLITTER1" (new data: "")

(3) ------------------------------------
Change done by the Edirol installation process: value "MSPCLOCK" (new data: "rundll32.exe streamci,StreamingDeviceSetup {97ebaacc-95bd-11d0-a3ea-00a0c9223196},{53172480-4791-11D0-A5D6-28DB04C10000},{ 53172480-4791-11D0-A5D6-28DB04C10000}")
But it has deleted by "something": value "MSPCLOCK" (new data: "")

Now, I don't know what exactly is... I have to think about it... but IF SOMEONE HAS AN IDEA... LET ME KNOW ASAP.

Reply

Answer 5

adriasca

Level 1

24 points

May 27, 2008 5:14 PM in response to Richard Van Nostrand

MY FRIEND... if you read what I've posted just a couple of minutes ago, you could see that me and you have came to a same conclusion... THE PROBLEM COULD BE REALTEK MANAGEMENT FROM APPLE DRIVER.

I ask you... it's possible that there is a DEEP CHECK about Audio driver choose by Apple to LIMIT the use of Apple hardware with Windows-Audio Units???
Could be possible??? I can't believe... but it could be.
If so, is a severe fact & problem.

What do you think???

Reply

Answer 6

Jul 6, 2008 6:02 PM in response to adriasca

Sorry I didn't check in here for a while. I don't think there is any conspiracy here- just sloppy driver code by RealTek. Apple's programmers won't allow this problem to remain long, but we'll have to wait for them to fix this. I guess bugging them will either make them mad, or they'll fix this in "Apple Time"

Good Luck.

Richard

Reply