heads up for fast track ultra users

oops... they don't work in asio mode with sonar... phlegh.  fine in ableton live, reaper and reason...
anyone get them to work?

Yeah the older driver was working for the most part in sonar and flawlessly on other daws. The new driver finally fixed the 64 sample latency issue in asio mode. Unfortunately wasapi mode and wdm with the new drivers perform poorly as well.

I would say its the Maudio drivers (which is no longer owned by Avid)  MAudio is now owned by "in Music Brands" which also owns Alesis, Akai Professional and other brands.  http://www.inmusicbrands.com/
 
Keep in mind, older drivers worked and the new ones don't - that points the finger at the driver.  Like when a software program does not work, its not a Windows OS problem its the software program - Windows does not have to be compatible with the program, the program must be compatible with Windows.

I installed the new driver this morning.  My Fastrack Ultra 8R tested OK in both Win 7 64 bit and Win 8 64bit with Sonar X2 64 bit.  I have a dual boot system so its the same hardware with both Win 7 and Win 8.  I did a quick recording test and it was OK and playback is OK, ASIO mode.
 
I've also got ProTools MP9, but I didn't test with that, as I don't have it currently installed. 

@jim - yeah, sure has.  works fine in other daws set to 64 samples for recording and playback running all 8 channels.  do you have an ultra or ultra 8r?  
 
@jack - 6.1.8 drivers, right?  are you running sonar in 32bit or 64?
tested with stand-alone dimension, z3ta+2 and rapture - no luck.  all native-instruments stand-alone devices work fine. 

hmmm... installed sonar 32bit and the asio drivers work fine there.  must be something with 64bit.  
@jim - i'd like to know if yours work in 64 and 32.  

Hi Arvid,

I tried this and indeed the X64 drivers do not show up in SONAR.
The problem is caused by a bug in the ASIO sdk. The code that tries to open the drivers compares the driver name string with 32 character string. Since the 64 bit driver string for the fast track exceeds 32 characters the string comparison fails and SONAR never sees the device. The 32 bit driver string is shorter and so doesnt run into this problem.
 
I worked around it in our code and indeed the driver loads and works fine after that. The newest driver wasn't particularly stable on the machine I tried it on. It blues screened immediately after installing the driver even before i launched SONAR :) Seemed ok after the reboot.
 
Anyway for users of earlier versions of SONAR you should be able to work around this problem by renaming the driver string in the registry to something smaller than 32 characters.
The driver key is stored here.  
 HKEY_LOCAL_MACHINE\SOFTWARE\ASIO\M-Audio Fast Track Ultra ASIO (64-bit)
 
I havent tried it but I'm assuming that changing the string description of the driver stored under that key will be sufficient to allow it to load. It shouldnt be necessary to change the key name itself.
 
Hope this helps.

Thank You, Thank You, Thank You Noel, the regedit works, Cakewalk Sonar is STILL the worlds BEST, thanks again.

Hi there,
 
I have this problem also that the new driver does not show up in Sonar. I see there is work around here, but i'm not to technical. Could someone possibly tell me what I need to do step by step. That would really be appreciated.
 
Thank You

So, the problem with the new driver is that it isn't being seen by Sonar X1 64, but Sonar X2a 64 does see it? Obviously the new driver has some issues. Has Sonar X2a fixed the issues? I'm just trying to understand the problem and find the simplest fix. (I'm less inclined to think of registry changes as 'simple'. Mea culpa.)
 
Bob

Just installed the X2a update and the 6.1.9 Fast Track Ultra driver update and discovered that the ASIO option no longer works. When I change the driver mode to WDM/KS, it identifies my M-Audio hardware and proceeds accordingly.
 
I tried the registry fix to no avail.
 
One caveat is that the driver installer would only run in Windows 7 compatibility mode.
 
Any thoughts from The Collective?
 
ADVthanksANCE
 
-Jack (in South Austin)

...and the hits just keep on coming...
 
I just revisited the registry key entry and found the description text as described and changed it from M-Audio Fast Track Ultra ASIO (64-bit) to M-Audio FTU ASIO (64-bit), and now the ASIO devices appear in my 64-bit X2a application, but only the WDM are available in the 32-bit PE8.5.3.
 
Then, I visited the 32-bit command prompt window to discover that there is no Description element in the driver key of interest, so I added one with the title of M-Audio FTU ASIO and now I have ASIO working in both worlds.
 
I now know enough about RegEdit to be a real danger to my system, so I am going to stay away from there as much as possible. >8]
 
Hopefully, this will help someone else who runs into the same issue.
 
-Jack (who is both more confused and more operational than before)