• SONAR
  • More crashes in the last few days than in the past 5 years! [Solved] (p.6)
2017/10/20 22:33:17
Leee
Keith Albright [Cakewalk]
Please send us the minidumps for any crashes.
I'll post how to find those if needed.


I used to send those, but they seemed to have been sent into a black hole.  Never receiving any follow-ups on them, I just figured they got sent to some file, never to be seen or heard from again. 

But if this happens again, I will make a point of sending the minidump report to Cakewalk.  However in this particular case, many times I just get the "Audio Engine has stopped", without Sonar actually crashing.  
2017/10/20 22:36:16
Seth Kellogg [Cakewalk]
Leee
Keith Albright [Cakewalk]
Please send us the minidumps for any crashes.
I'll post how to find those if needed.


I used to send those, but they seemed to have been sent into a black hole.  Never receiving any follow-ups on them, I just figured they got sent to some file, never to be seen or heard from again. 

But if this happens again, I will make a point of sending the minidump report to Cakewalk.  However in this particular case, many times I just get the "Audio Engine has stopped", without Sonar actually crashing.  




The automated fault reporter goes into an automatic parsing system. Unless someone points it out, it'll only be looked at via a machine. It's still super important to send them in when you can.
2017/10/20 22:44:28
LLyons
I am experiencing the dropout phenomena too.  Just the 'audio engine has stopped', no crashes.   Its happening with both MOTU and Presonus hardware,  
 
I've run the latency monitor - and it shows a fast system - even when the dropout occurred, latency monitor did not peak in any of the segments .. I turned off all other audio drivers..  I also shut down the wireless internet connection. Ive been watching the thread performance in the bar at the top of the screen.  At no time do any of the 8 segments go past 15% or so.   
 
I did update to 2017 9  a few days ago, but the error didn't pop up the entire evening after.  Only the following day.
 
I also started getting little pops in the recorded wave file about 5 weeks ago maybe.   If I reboot - it stops.  It seemed to be happening near a WUP sequence (get\test\post) and when I reboot, it goes away. 
 
Strange - last night I had at least 20 dropouts.  
2017/10/20 23:28:03
Cactus Music
Seth Kellogg [Cakewalk]
Leee
Keith Albright [Cakewalk]
Please send us the minidumps for any crashes.
I'll post how to find those if needed.

 
The automated fault reporter goes into an automatic parsing system. Unless someone points it out, it'll only be looked at via a machine. It's still super important to send them in when you can.




 
So your saying the automatic reporting will not be brought to anyones attention? Are we to e mail cakewalk ? this is now not clear to me,, I always leave my DAW offline, but because of the crashes I was leaving it on line just so the dumps would be sent in. But the few times it happened a busy wheel would just spin as it was submitting for about 10 minutes and I'd give up. So I've returned to being off line and just hoping it will all go away magical with the next update. 
2017/10/21 03:42:54
Seth Kellogg [Cakewalk]
Cactus Music
Seth Kellogg [Cakewalk]
Leee
Keith Albright [Cakewalk]
Please send us the minidumps for any crashes.
I'll post how to find those if needed.

 
The automated fault reporter goes into an automatic parsing system. Unless someone points it out, it'll only be looked at via a machine. It's still super important to send them in when you can.




 
So your saying the automatic reporting will not be brought to anyones attention? Are we to e mail cakewalk ? this is now not clear to me,, I always leave my DAW offline, but because of the crashes I was leaving it on line just so the dumps would be sent in. But the few times it happened a busy wheel would just spin as it was submitting for about 10 minutes and I'd give up. So I've returned to being off line and just hoping it will all go away magical with the next update. 


 


It would be humanly impossible to go through each and every automatic fault report that comes in. Instead our server parses the crash report data into a more manageable format. That way we can have a larger overall view of the products health and can focus development effectively. Please send the automatic reports when you can and have analytics on. We can't fix issues we don't know about. Crash dumps can be large, so upload times can impact responsiveness of the utility.

If you have a repeatable and consistent crash recipe, please post it in the problem reports subforum. QA can then verify and get it into the roadmap.
2017/10/21 04:21:28
jonnewyork
LLyons
I am experiencing the dropout phenomena too.  Just the 'audio engine has stopped', no crashes.   Its happening with both MOTU and Presonus hardware,  
 
I've run the latency monitor - and it shows a fast system - even when the dropout occurred, latency monitor did not peak in any of the segments .. I turned off all other audio drivers..  I also shut down the wireless internet connection. Ive been watching the thread performance in the bar at the top of the screen.  At no time do any of the 8 segments go past 15% or so.   
 
I did update to 2017 9  a few days ago, but the error didn't pop up the entire evening after.  Only the following day.
 
I also started getting little pops in the recorded wave file about 5 weeks ago maybe.   If I reboot - it stops.  It seemed to be happening near a WUP sequence (get\test\post) and when I reboot, it goes away. 
 
Strange - last night I had at least 20 dropouts.  




The OP has clients coming in.
 
Dropouts are unacceptable, as are crashes. A stable platform is of fundamental importance.
 
The last few times I tried to send crash dump info to Cakewalk, the send tool failed mid-send.
When that happens, the recommendation is that you have to go into DOS and enter a string of command code...
 
Please can we not go there? Can you boffins fix that? We in production are usually wearing one hat too many as it is, and I don't want to find out the hard way where a typo in a command line argument leads.
 
 
2017/10/30 17:52:52
drummaman
Seth - " Kontakt Issues and Sonar Platinum Engine Issues " was submitted.
There are at least a half dozen dump files included.

Leee -
I'm convinced it's Windows 10. And it's been getting worse.
...and I also have clients watching the system crash during mix sessions. Not pretty.

My question for those of you recommending turning off your network adapter -
I have an iLok that needs to check-in with the Pace mothership...
What's the work-around for that??!

And how do you stop apps and Windows from banging on the down network connection?
...even though your adapter is off, there is still software that will look for it. (Windows 10 being the biggest culprit, no doubt.)

Sign me "Feeling Your Pain".
2017/10/31 01:08:18
lgmab
LLyons
I am experiencing the dropout phenomena too.  Just the 'audio engine has stopped', no crashes.   Its happening with both MOTU and Presonus hardware,  
 
I've run the latency monitor - and it shows a fast system - even when the dropout occurred, latency monitor did not peak in any of the segments .. I turned off all other audio drivers..  I also shut down the wireless internet connection. Ive been watching the thread performance in the bar at the top of the screen.  At no time do any of the 8 segments go past 15% or so.   
 
I did update to 2017 9  a few days ago, but the error didn't pop up the entire evening after.  Only the following day.
 
I also started getting little pops in the recorded wave file about 5 weeks ago maybe.   If I reboot - it stops.  It seemed to be happening near a WUP sequence (get\test\post) and when I reboot, it goes away. 
 
Strange - last night I had at least 20 dropouts.  
2017/10/31 01:12:57
lgmab
I am experiencing the exact same problem! It has been most frustrating. I have been in touch with MOTU thinking that my 16a is the problem. It was only after I reinstalled all motu hardware an des then even tried a roland sound card that I began to point a finger at Sonar....it has been ultra frustrating and like others, I am sure that my many CS request are lost in the void.
If anyone has any idea as to how we can work around this, please let us know. I also thoroughly spec'd the configure files , thinking that perhaps some magical single parameter mod would bring me back to drop out free performance...no such luck. I was even thinking of a re I stall for sonar buy stopped short of this as it's always a problem. Since others are experiencing frequent and unprovoked dropouts, I would suggest that Cakewalk look into this as a priority...we can't work. :(
2017/10/31 01:15:17
lgmab
Hello Lyons, I too ran the latency monitor, I get yellow bars with an average of 1000micro seconds, I occasionally get a green stream as well. I have an ho laptop with i7 2.5ghz 16gb ram. What are your specs?
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account