These are both M tracks. There are about 6 models. 
 


 
 

You're right. I meant 'II' but pronounced it '2' in my post. My box is the white one (above) which is an 'M-Track' and not an 'M-Track II' although it's identical. I went to M-Audio again to get their driver in case I'd installed the wrong one. It didn't make any difference. Their list of drivers comes down to only one I can use on Windows 10, 64 bit. This isn't ASIO.
 
The original CD is long gone by now but either contained or linked to Asio4all which is why I've been using it since I bought the device. It's never been an issue before.

With the Windows driver off M-Audio's site, Sonar Artist starts and runs reliably but with 30ms latency. Even with that it didn't feel underwater on vocals or guitar/bass parts. My cajon whacking seemed less accurate though that may just have been me. The trouble with latency is that you can't always tell if you've got it or have suddenly lost the ability to count to four with a metronome going.

Realising that I really needed the recommended Asio4all drivers I put them back and this is where I'm at: by raising the sampling rate a lot I got the reported latency down to under 6ms and a lead break didn't meander off into a lake on a five minute test track. There was no problem mixing to a .wav. 

I considered/am considering just getting an internal card for my PC again. My old Fatality (prior to this M-Track) wouldn't work under Windows 10 due to lack of interest on the drivers front. I do have the thing gathering dust and I see Creative did a driver a year ago so maybe I'll check it to see if they fixed it. They do describe it as 'end of life', though, which isn't encouraging. So, maybe a new one...

Or, I may try to live with the situation which is way cheaper. :) I've found that my setup will work reliably if I perform a ritual: on startup Sonar Artist is silent. If I go to Preferences/Driver settings and check and save the 64 bit box to 32 bit and then put it back as it was, when I go back to Sonar it works perfectly. Silly process but 100% reliable. It's like having to let a tyre down and pump it back up before your engine will start on your car.
 
Joakes, in his earlier post, seems to have had pretty much the same behaviour with his gear. I take comfort from learning that I'm not the only one!

Does anyone have any thoughts on alternative generic Asio drivers? 
 
Thanks for your suggestions - especially the one where you persuaded me to get the name of my interface right. 
 
Steve

So you saying the drivers posted by M Audio are not ASIO? That's very weird. But then, M Audio is entrenched with Mac, Core Audio and Pro Tools. I had a M Audio fast track pro that was a terrible interface and wasted over year fighting with it. I would never buy anything from that company as a result,, just me. 
 
No No and double No to anything  by Creative,,, I been down that road too. PCI interfaces are a thing of the past unless you spend $1,000 on a Lynx. The majority of us use a USB interfaces supported by a ASIO driver without issue. 
Do yourself a big Favour. Sell the M Track to a Mac user who will probably be happy. And buy a proper interface that is known on this forum to perform without issue in PC land. 
You can get something from Tascam, Stienberg, PreSonis or Focusrite for $150 that would be the same as yours. 

Thanks. I'll start looking at a new interface. I've found your suggestions very useful.
 
Steve

I've just been to the M-Audio site and there's a whole raft of drivers including both 32&64 bit drivers for Win 10.

They don't say what type they are but typically they would be ASIO and whatever else might be included in the driver package.

I just googled m audio driver for m track win 10.

mudgel
I've just been to the M-Audio site and there's a whole raft of drivers including both 32&64 bit drivers for Win 10.

They don't say what type they are but typically they would be ASIO and whatever else might be included in the driver package.

 
http://m-audio.com/kb/article/1665
Here they seem to imply that the ASIO driver is available but is not the default driver.

It does say that, you're right, but it isn't what happens for me. I've never seen an M-Track Quad ASIO Driver although they describe one. The only reason I knew Asio4all existed was because they suggested using it. 

The manual for my M-Track says, 'We recommend the free ASIO4ALL (Audio Stream Input/Output) driver for Windows.'
 
It's disconcerting that I have to do a dance in the Asio panel every time I use Sonar but the actual performance is now much better for having tinkered with the settings. I'm tempted by the Roland, Steinberg, Tascam, Focusrite alternatives. If it gets unstable or out of hand I'll pick one straight away. I've been looking at them on Amazon.
 
I was going to reinstall Windows 10 to see if I could clear the problem but that seemed harder than I expected. I started up with a USB to bring up the installation just fine but then I got some messages about how none of the drives were allowed. Something about OEM and GPT. No idea what the second one is or how to continue so I gave up on that. I would have liked to have tried it. I have a solid, tested Acronis backup of my current system so it isn't risky. It just wouldn't let me proceed. I expect if I read up on it via Google I'll see how to sort it out.
 
It's like trying to clean up a tiny paint drip and knocking the whole can over. You'd think that reinstalling Windows 10 - though a bit drastic and time-consuming - would, at least, be uneventful and simple. I bet it would work, though, as this is a very recent problem and the Asio4all drivers were doing a fine job for over a year. The M-Audio box looks nice and works for general sound: movies, YouTube, etc, perfectly. I'd be more than happy with it if Sonar came on with sound. My restore points don't go back far enough to help. Having cleaned installed Sonar/deleting .ini files, going through the registry and deleting references to ASIO and Cakewalk I felt sure this would go away.
 
What's annoying is that Sonar will work once I've changed an Asio setting and then changed it back again. As long as I do that it's all good. When I started this thread I didn't imagine it could be persuaded to run reliably but the workaround never misses. I'd have to say things aren't all bad. 'Worse things happen at sea!' as my mum said long ago, the night I got acute appendicitis.
 
As ever, thanks for giving my Sonar/Asio dilemma some thought and for all your sensible views and suggestions.
 
Is there a generic Asio driver anyone would recommend? That could be a simple fix, couldn't it? 
 
Steve
 
 

FlameDruid

The manual for my M-Track says, 'We recommend the free ASIO4ALL (Audio Stream Input/Output) driver for Windows.'
 

 
I find it astonishing that M-Audio would recommend ASIO4ALL. 

VinylJunkie
 I find it astonishing that M-Audio would recommend ASIO4ALL. 

Alesis does the same thing. that driver is like a cancer.
Years ago I thought it worked well with older OS' like windows 7 but for some reason with windows 8 and windows 10.  
I have seen more problems than productivity so I decided not to recommend it anymore.

Hi again,
My problem just got resolved by Cakewalk support. The device looks like M-Track but registering it revealed that it is, indeed, M-Track II and the driver for that is different. It didn't take properly before but has now and includes ASIO.

So, Asio4all is gone. The error message was caused by playing back a track recorded at a different sample rate. The M-Track II is okay. The driver is correct and the sample rate no longer produces an error. Latency is very low.

Best of all, Sonar now works perfectly as soon as it starts up. Thanks for your suggestions. This one had a happy ending. 

Steve