bitflipper


What did CW report to you when you sent them the crash dump?

When SONAR hangs like that, it is either a driver issue or a hardware failure (the audio interface, a firewire adapter, or in rare cases a power supply, disk drive or controller). SONARPDR.EXE is hung because it's waiting on some external event, e.g. waiting for a call to a driver to return, but the driver has either crashed or gone into an infinite loop waiting for hardware to respond. IOW, it's not something Cakewalk can fix.

Yup.
If it's an external device the user could turn it off and turn it back on and usually take care of the problem.  However, when it's and internal card there's not much they can do except check for different drivers, or repace the card.
 
This is one of the problems with troubleshooting.  A certain piece of software reveales a system problem, and the user naturally thinks it has to be a problem with the software.
 
And, they will rationalize it by "Nothing else on my system causes a problem!"
 
Sure wish they would visit video card manufactuerer and/or audio interface sites and read the faqs of how many problems their drivers cause with specific software.
 
"Resolved and issue where Sonar would freeze waiting for..."
 

In my situation it only happens when using one of my USB interfaces - Roland Quad Capture and Cakewalk UA-25EX.  It doesn't happen when using my Echo Audiofire 8Pre.

Do you see the same issue if you wrap your native drivers in asio for all? In other words, bypass the m-audio. I have an m-audio device, as well as others, and I can attest to all kinds of funkiness from it. It's dirt cheap and you get what you pay for.

It IS a driver issue but Sonar is the ONLY audio application I have seen be such an ungraceful piece of @$#% about it. I once read a post (I think from Noel) defending Cakewalk's grandiose position that it wasn't their fault even though other applications can deal with this reality without being an utter piece of crap. Why do things right when you can hide behind standards and blaming the other guy? This issue has pissed me off for a long time. Of course droves of folks around here will tell you Cakewalk can do no wrong and that its all your fault. Doesn't help Sonar get any better when valid criticism is drowned out.

Other applications can "deal" with a hung interface? I doubt that very much. All programs are bound by the constraints inherent in the basic architecture of the operating system.

I do agree, though, that CW could do more to prevent or mitigate such problems and make the program more bulletproof. I'm sure if Noel were running the company, that would happen. But as it is, the Marketing department calls the shots over there nowadays, and "Fewer Crashes!" isn't a very sexy marketing slogan.

Part of the confusion: The event viewer only shows what has been reported.

So, Sonar has stopped working. And it reported itself.

What stopped Sonar is the real question. Driver, plugin, OC, mem voltage,...

Get BlueScreenview
http://www.nirsoft.net/utils/blue_screen_view.html
And appcrashview
http://www.nirsoft.net/utils/app_crash_view.html

when sonar crashes, the process cannot be terminated because other PIDs have hooks into it.

what frees it up for me is to unplug MIDI USB hardware and plug it back in and the process dies.

Delta 1010...

Legacy item...

Emu...legacy item...

The OP has given very little real details...driver versions, hardware versions, etc...

I am actually surprised Delta even has Win 7 drivers for the 1010...

Its a little hard to take this post serious when we have so little serious information to go on...

I feel for the OP...but not a lot.

It's definitely related to the specific hardware/driver combo one uses, and yes some other applications seem to deal with it better; Cakewalk has admitted the situation, but insists that its code is correct and refuses to budge. All I know is, I used to have the problem only with Sonar, using my MOTU PCI424 based system, when one day MOTU released a new driver and now I don't have this problem anymore! R

Well - it seems to boil down to only one question then. Does Sonar have to take in account rotten drivers and make weird work-arounds, or do the hardware makers have make drivers that work good in the first place. I think I go for the last option. Oh - and by the way.. Korg also made some terrible drivers for their micro controller series. If this is still the case I don't know, because I do not have any Korg hardware anymore.