Disable ASIO Mode in SoundBlaster Xfi

fireberd · 16 Oct 2010

I have a conflict problem that has developed in my Sonar (8.5.3 PE 64 bit version) where my Xfi Titanium Fatal1ty Pro is showing up at an ASIO device in Sonar and Sonar is defaulting to this when I start Sonar, even though I have a Firewire connected Focusrite Saffire Pro 40 that is my audio I/O device when using Sonar.

At one time it wasn't an issue and I'm not sure if there was a SoundBlaster update that caused the problem or if there is a corruption in Sonar.

The other issue with the SoundBlaster and ASIO is that in the Windows Device Manager it's listed as "Creative Xfi Audio Processor (WDM). Note the WDM and not ASIO.

Is there a way to disable ASIO operation of the Xfi?

Aphelion · 16 Oct 2010

Unfortunately, I don't think ASIO shows up as a separate entry in Device Manager most of the time.

I guess you looked in control Panel/Sound and seen if it shows up as an output device, make sure you have "show disabled and disconected" devices enabled.

It may take a registry edit to eliminate the Creative ASIO selection from the Windows available ASIO driver list. You might be able to disable it in the Sonar registry section, I don't know if Sonar would pick it up again when it booted.

Copy down the exact name given to the Creative ASIO driver, that is, the same way that Sonar has it listed.

Run a registry serach on the name, you will probably find several entries.

Try editing only the Sonar section and see if that works. Putting a semi-colon ; before the device name changes it into a "remark" and it's no longer picked up by the system,.

Ap

fireberd · 17 Oct 2010

A registry search for "ASIO" doesn't turn up anything.

It looks like I will have to disable the SB in the Device Manager when I use Sonar and another ASIO device such as my firewire connected Focusrite Saffire Pro 40. I have another recording unit a USB connected MAudio Fastrack Ultra 8R that works in both ASIO and WDM mode, and when WDM is selected and it does not have the conflict problem with the SB. The Saffire Pro 40's preamps are superior to the MAudio unit and have a "sweeter" recording sound.

Aphelion · 17 Oct 2010

fireberd said:

A registry search for "ASIO" doesn't turn up anything.

Wow, I have a lot of ASIO entries in the registry.

When you open the registrty editor you may have to select the top entry (Computer) before hitting F3 and typing in the search string. Hitting F3 again also continues the search.

Ap

fireberd · 18 Oct 2010

I'll try the ASIO again. But I did start the search from the beginning of the registry. But, I've been looking at some .ini files in Sonar and I think the problem may be there. I have a request into Sonar Tech Support and I'll see what they say. I see the SoundBlaster listed in several .ini files. I guess I could make a copy of the file and rename it and then make a new copy without the SoundBlaster and see what happens.

Update: I did another search and did come up with ASIO entries. I must not have been at the top when I started, as I though I was.

Aphelion · 18 Oct 2010

fireberd said:

Update: I did another search and did come up with ASIO entries. I must not have been at the top when I started, as I though I was.

I'm pretty sure you can disable the Creative ASIO driver from the registry, if you give me a day I can tell you the exact spot to edit.

Ap

fireberd · 18 Oct 2010

I saw the Creative ASIO. I don't like doing that as I would have to go back and enable it if needed. The easier way is to just disable the SoundBlaster in the Windows Device Manager rather than messing with the registry.

But, if there is something that I can do in Sonar (which is the only problem) then, after thinking about the problem, I'd rather do that. I'll hold off and see what Sonar Tech support says.

Thanks/Jack

Aphelion · 18 Oct 2010

fireberd said:

I saw the Creative ASIO. I don't like doing that as I would have to go back and enable it if needed. The easier way is to just disable the SoundBlaster in the Windows Device Manager rather than messing with the registry.

But, if there is something that I can do in Sonar (which is the only problem) then, after thinking about the problem, I'd rather do that. I'll hold off and see what Sonar Tech support says.

Thanks/Jack

I thought you were going to disable it permanetly so the registry is not the way to go.

It does seem odd that Sonar doesn't maintain the selection, perhaps editing the order in one of Sonar's .ini files would do the trick. Good luck.

Ap

fireberd · 19 Oct 2010

Sonar tech support's response was a typical dumb rear end "consumer" response. I wasted my time e-mailing them.

After considering the problem, I don't want to permanently disable the SB ASIO mode as I use the PC for both regular Windows and for the DAW. It looks like the best alternative is to disable the SoundBlaster in the Windows Device Manager when I want to use Sonar and then re-enable it when I'm finished with Sonar.

The only thing that still bugs me is that it didn't work that way initially and at some point either Windows/SoundBlaster was changed and/or an initialization file in Sonar has changed. As there will probably be a new Sonar version out in the next couple of months I'll hold out for the new version and a complete new install and see what that does.