• Hardware
  • heads up for fast track ultra users (p.2)
2013/07/06 15:47:58
Jim Roseberry
Thanks
I have a FastTrack Ultra 8R.
Been sitting on a shelf... because they removed high-performance mode. 
2013/07/06 16:00:17
swamptooth
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.  
2013/07/07 06:45:05
fireberd
I'm using 64 bit.  Both Windows 7 Home Premium 64 bit and Windows 8 Pro 64 bit, and Sonar X2 64 bit.
I have an 8R.  If you have a different model Fastrack Ultra maybe there is a difference?
2013/08/30 08:15:18
Noel Borthwick [Cakewalk]
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.
2013/08/30 22:48:02
swamptooth
I'm quite impressed that you were able to nail that down Noel!  That had to be quite a bit of investigative work on your part, and I'm very grateful that you took the time to look into it.  My thanks to you and the other bakers, it seems like you all get a hefty amount of criticism here on the forum but I have honestly seen nothing from anyone on your team besides a genuine interest in helping your customers resolve their issues and straightforward attempts to get nail down the issues when they happen.  Your company never fails to amaze me with the level of support you provide.  Pass my thanks along to the team as well. 
 
Best, 
2013/09/04 22:42:09
fireonline
Thank You, Thank You, Thank You Noel, the regedit works, Cakewalk Sonar is STILL the worlds BEST, thanks again.
2013/09/05 01:20:16
swamptooth
hey mark saw you on the avid forums.  glad we got this sorted! :D
thanks again, noel.
2013/09/11 04:18:56
pagec
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
2013/09/11 08:38:03
fireberd
I just installed the latest version, 6.1.9.  Win 7 64 bit and Sonar X2a 64 bit.  On playback everything is working OK, without doing the registry modification as noted. 
 
I haven't tried any recording, but Sonar automatically recognized my Fastrack Ultra 8R and set it as the audio device (ASIO).
 
 UPDATE:  I installed the new version on Windows 8 64 bit/Sonar X2a 64 bit and it is working OK there too.  It is the same PC, dual boot Win 7/Win 8.
2013/09/11 09:54:06
jazzwombat
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
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account