[Answered] Installed X3 ...Now no ASIO drivers!

Did you install as admin?
Did you reboot after the install?

To run as admin, RIGHT click the .exe and choose "Run As Administrator"

I would also try to re-install the MOTU drivers. I had a similar issue to yours a long time ago and that fixed it. I can't remember what might have caused it tho..

Have you tried turning off the motu unit and then physically unplugging and replugging the USB/Firewire back to the computer? I've had my MOTU get into a permanently hosed state once that was only solved by a full reset like that. I have X3 and a MOTU and its working fine. Also check if the drivers are available in X2 or any other program under ASIO. 
As a last resort uninstall and reinstall the MOTU drivers. 

I ran the install as admin. It didn't work. I'll take a look at a stand alone program and see if the asio driver is available. MOTO suggested that if by chance it doesn't...repair the drivers through the Windows control panel. I'll take these steps and get back.

This interface is a MOTU 896mk3. It's FIREWIRE!
 
OK, I've checked several stand alone synths, ie FM8, Rapture, and all of them have ASIO drivers enabled and functioning.
I then opened an instance of Sonar X2. Then it told me that I have ASIO drivers to replace others and it worked. All ASIO drivers appeared in the list and it functioned properly.
When I load an instance of X3...No ASIO drivers!
i could try a repair. Not sure if that's going to do anything. Seems to me like there is an issue with X3 not seeing the drivers but I don't know. I'm going to do it anyway as it's really the only thing I can try.
 
So, how is it that X2 sees the drivers without issue but X3 doesn't? I can do a bunch of uninstalls and the such. But, again. I've run everything as administrator on the new install, rebooted it and whatever else I can think of to do. I'm just puzzled that mine doesn't work but everyone elses does. What system requirements would I possibly be missing on this system that would prohibit me from using my interface? Hmm, very puzzled.

Very weird indeed. Can you post a screen shot of your x2 and x3 asio device configuration screens so I can see the device names?
Anyone else here running an 896?

 

 
Here are the 2 screenshots. Thanks!
 
 

 

 
Great Thanks....just in case that didn't work....AGAIN....There are the links!
 
 
http://s265.photobucket.com/user/jackasspenguin/media/2013-10-11_0044.png.html?sort=3&o=0
 
http://s265.photobucket.com/user/jackasspenguin/media/2013-10-11_0112.png.html?sort=3&o=1
 
 

Did you select ASIO driver mode under Preferences/Audio/Playback and Recording?

I don't think you understand the question here... Can you post a screenshot NOT Of the devices tab, but of the driver settings tab, as that is where you change the driver... Not in the devices tab.

One thing that is interesting is that X2 is working when X3 isn't. Audio settings are saved separately between X2 and X3 so resetting the X3 settings could fix up your install. Give this a try and let me know if this helps. 
 
1) Make sure SONAR is fully closed and navigate to your appdata folder (paste &appdata% into your file explorer window to get there)
2) Open the Cakewalk folder
3) Open the X3 Folder
4) Locate the file called "AUD" or "AUD.ini"
5) For safe keeping it's best to save this file somewhere. I recommend simply moving the file to the desktop.
6) With the file now moved out of the folder, Make sure your motu is ON and plugged in and relaunch SONAR X3
 
SONAR will automatically recreate The AUD.ini file with clean settings.

http://s265.photobucket.com/user/jackasspenguin/media/2013-10-11_1606.png.html?sort=3&o=1
 
This the appdata notepad file I deleted. So, when I opened X3, it behaved like the first time I opened X3 and did the driver profile thing. And..only showed the MME drivers doing it's thing.
 

http://s265.photobucket.com/user/jackasspenguin/media/2013-10-11_1610.png.html?sort=3&o=0
 
This is the Driver Settings tab. And there are no options in any drop down menu to select anything other than the mme motu audio driver... which is no surprise, If it doesn't show up in the devices,,,why would it show up in the device settings?
 
 I had a thought...If X2 is working properly and seeing the Asio drivers..What file is that? If X2 is finding the asio drivers does it not create that pointer in the App Data for X2? What if I deleted the instructions in X3 app data and replaced it with the app data from X2? Would my computer explode?
 
 
 

sergiobklyn
Did you select ASIO driver mode under Preferences/Audio/Playback and Recording?

 
This is the key question... Maybe it's changed in X3 and is set elsewhere?

Can we please, please get beyond whether or not I have selected the ASIO drivers under preferences? This isn't a matter of whether or not I didn't choose to use them. First of all, Sonar is going to use the ASIO drivers whether I select them or not. Again! right now! I'm using X2 in all it's splendor rockin' some ASIO drivers like the dickens. Thankfully I can still mess with Addictive Drums and continue doing something.  So,,,,, lets move forward here.
 
So, I uninstalled X3 and disabled every Firewall, every Antivirus, everything that might be interfering with an install that I've seen mentioned or can think of... Installed in as administrator..stood with on one foot with my mouth open..... blah blah blah. Still...NO ASIO DRIVERS! I even opened a project with X1 just for gits and shiggles. Yes! I have ASIO DRIVERS in X1 too. So, at the end of all this..what we know is I have ASIO Drivers in X1 and X2 but Not X3!