Help!
 
Sonar Artist was fine. It always worked on my machine (4.0Ghz Vishera. 16GB Ram. Windows 10. M-Track 2 USB sound interface, Asio4all drivers) running Sonar Artist. Only now it makes no sound unless I fiddle about with settings when it first starts up. 

If I go into preferences and do almost anything with the ASIO drivers... i.e. change any setting, (and even if I change it back as it was...) the track will play fine. But I have to do it every time I crank up Sonar. Sometimes getting into preferences takes a while. Sometimes 'Sonar is not responding' comes up.

I've done a clean install of Sonar. I've reinstalled M-Track. I've reinstalled Asio4all. I've gone to previous restored versions of my system as Sonar stopped finding M-Track. I've tried most variations of possible settings many times. I rolled back to previous versions of the software. The audio engine initialisation button doesn't. I've plugged M-Track 2 into various USBs in case I'd got in a USB 3.0 by mistake. No difference. I changed the lead with my printer's to no avail.
 
Acid Music 8.0, I notice, is working with the Asio4all drives just fine still. All my normal Windows sound, YouTube, etc, works normally through the M-Track. MME drives work normally if I can live with 30ms latency.
 
My attempts to pin this down have failed. Without a real person in Cakewalk support to ask I don't know where to turn. It's too weird a problem to find in a forum as an existing problem, I suspect, so if anyone can think of how this irritating behaviour might be fixed I'd be very grateful.
 
Steve

Hi,

First of all uninstall Asio4All. There are, AFAIA Windows 10 drivers here :

http://m-audio.com/support/drivers

Download and install them. Re boot, fire up Sonar and in Preferences make sure the drivers you installed are selected, and you should have sound !

Cheers,
Jerry

A driver update may indeed help. Or not.
 
I see this occasional weird scenario: if I forget to turn the interface (Focusrite) on before booting, and then bring up any audio program (WMP, YouTube, SONAR) there'll be no sound until I make some change to the interface settings. Usually, I pull up the ASIO panel and alter the buffer size. Audio returns immediately. My previous interface (Motu) did the same thing, but it was worse because nothing brought audio back short of a reboot. Why does my current interface recover more easily? I believe it's thanks to a better driver.
 
It certainly won't hurt anything to use a proper ASIO driver as Jerry suggests, rather than ASIO4All. You might experience lower latency as a bonus.
 
 

bitflipper
A driver update may indeed help. Or not.
 
I see this occasional weird scenario: if I forget to turn the interface (Focusrite) on before booting, and then bring up any audio program (WMP, YouTube, SONAR) there'll be no sound until I make some change to the interface settings. Usually, I pull up the ASIO panel and alter the buffer size. Audio returns immediately. My previous interface (Motu) did the same thing, but it was worse because nothing brought audio back short of a reboot. Why does my current interface recover more easily? I believe it's thanks to a better driver.
 
It certainly won't hurt anything to use a proper ASIO driver as Jerry suggests, rather than ASIO4All. You might experience lower latency as a bonus.
 
 

Totally agree re Focusrite - happens to me with my LS 56.

Cheers,
J

Why did you end up with asio4 all when there is a proper driver available? Asio4all is a last ditch effort if you cannot find a proper driver. Sonar is a bit picky about drivers which is not a bad thing, it's just how things are in PC land. 
  asio4all is NOT an asio driver even though the name implies it is. It is a wrapper for WDM mode. 
And it is also not that easy to totally un install. It is known to conflict with proper ASIO drivers. We now have WASAPI driver that is said to make asio4all obsolete for those unfortunate enough to own an audio interface without proper asio drivers. 

Thanks for your suggestions and perspectives. With the drivers you suggested my sound works fine albeit with a reported lag of 30ms. At least it comes on. These are M-Track's drivers rather than ASIO ones. Asio4all used to work okay with lower latency and still do work in Acid Music Studio 8. They were the ones recommended by M-Track but I'd be happy to try others if someone knows of better ones. 
 
I had no idea which element was broken before but as Sonar is now back up with no issues on M-Track, I suppose Asio4all has had a hissy fit at something in a Win 10 update. It must have been recent as it was fine up to Christmas. Movies and YouTube, etc, are all fine though that wouldn't be ASIO of course.


WASAPI doesn't like this M-Track, USB box.
 
Thanks again for taking the time to respond. So far I'm just using MME drivers yet it feels surprisingly co-ordinated. If I am going to wallow in latency it hasn't been evident so far though I could be getting too old to notice. 
 
Steve


 

Sonar has a problem initializing ASIO4ALL (or ASIO4ALL has a problem knowing that Sonar has opened).  It has been that way since X1.  I fought this problem for quite a while until I changed interfaces to one with a proper driver.  Drivers load when hardware is detected.  ASIO4ALL is not a real driver and loads when your DAW runs.

Nobody should have to suffer MME mode. That's terrible. 
Is not the M audio interface a newer model?? 
You mean they have not writen ASIO drivers for W10?? 
 
Which exact model is yours? There seems to be no such thing as a M track 2.. but there are many other models. And most look like they have W 10 64 bit drivers. 
You should really figure this out as it not just latency that suffers with bad drivers, There can be other issues like track overdub offset being way off. 
 

I think that describes the Asio4all very well, Mr Colbert, although it worked for me without issue until just recently.

Cactus:  This is the one. It comes with drivers but I think it pushed Asio4all. Having said that I just found a text file list of drivers and it does have this: "MAudioMTrack_Asio64.dll    1.0.1.* (x64)". I can't see that in Sonar as an option. Maybe if I can find out how to get at it that might be the droid I'm looking for. There's a 'track device settings' menu but it won't open. I think this looks promising though. 
 
Steve

I saw nothing about using ASIO4 all All I saw was a lot of different models that are called M Track. None are called M track 2. There is a M Track Mark II.  Each has a list of drivers for both MAC and PC. the MAC list is real long but the PC list is much shorter. Seems they have a driver for every possible OS and 32 or 64 bit. 
So make sure you download the correct driver as it would seem its easy on their site to grab the wrong driver. .