• SONAR
  • [Solved with 2017.01] Sonar Platinum 2016.12 Crashes when exporting project/audio
2016/12/21 19:31:01
Leee
I don't think I can ever recall having a repeatable crashing issue with Sonar.   I read all these posts from people who have problems with Sonar crashing, and I feel a bit bad for them, but also felt fortunate to have a stable working DAW.
Well, that changed with the latest update 2016.12.   It seems whenever I try to export my project into a wav or mp3 file, Sonar will automatically give me the Windows "this program had an unexpected..."  along with the crash report window from Cakewalk.

I tried this on new projects that were written in the latest version, as well as older projects from earlier versions.  They all crash when trying to export them.   I reverted back to 2016.11 and everything is working fine again.

I submitted a bug report.  Just wondering if anyone else has this particular issue?
2016/12/22 17:10:24
Leee
The latest December 2016 update failed to fix the issue I'm having of Sonar crashing whenever I attempt to export a project to an audio file (mix down and export).
Again, I've reported this using the Fault Reporter, but the original report has yet to get any kind of response.

Any suggested work-arounds, (besides reverting back to a previous version) would be appreciated.
2016/12/22 17:46:37
Sailor55
I have also just updated to 2016.12 and I don't seem to be having this problem. 
 
Or, let's put it this way, I am able to mix my projects down to a stereo track, and then export that track, as always. 
2016/12/22 19:44:07
Leee
Yeah, I know, I've been searching and haven't been able to find anyone else having this problem.
I have found a quick and easy work-around though, I just start Sonar in Administrator Mode and it works fine without crashing.  So, that's what I'll do from now on.  I'm guessing it might have something to do with Windows 10, I've noticed a lot of crash issues with Sonar and the latest update of Windows.
2016/12/22 20:50:10
bitman
Some projects with some plugins on some days will get fussy and cause this.
Can you export a different project or do they all do crash?
If you turn off Fast Bounce will it export? I like to turn on audible bounce when I do this btw.
2016/12/23 01:01:08
Leee
I tried to export a project that had just VST instrument, with no efx plugins.  Just one track.
I always have Fast Bounce off when exporting a song/project.  It crashed.
I also tried with a just an audio track too (again, no efx).  It crashed as soon as I pressed the start button to export.

And like I said, it all works fine from November's release.   But I'm able to make it work by running Sonar in Admin mode.  So, I'm able to continue to write and record songs without any issues.
 
2016/12/23 11:07:59
Anderton
Even though I suppose your original problem wasn't solved, you did find a solution so I marked this as "solved" for the benefit of people if they have the same problem and do a search.
 
FWIW I have SONAR set permanently to run in Admin mode. Both Windows and SONAR seem to like that best.
2016/12/23 11:20:43
pwalpwal
Anderton
FWIW I have SONAR set permanently to run in Admin mode. Both Windows and SONAR seem to like that best.




what is it that sonar needs admin mode for (that other hosts don't) - for the example above, just to export audio? this has been an on/off issue for years, and it's not generally considered best practice by ms (least-privilege etc)
2016/12/23 11:28:22
Roo Stercogburn
pwalpwal
Anderton
FWIW I have SONAR set permanently to run in Admin mode. Both Windows and SONAR seem to like that best.




what is it that sonar needs admin mode for (that other hosts don't) - for the example above, just to export audio? this has been an on/off issue for years, and it's not generally considered best practice by ms (least-privilege etc)


 
Agreed, permanent full admin is not good. From Win 7 onwards, the 64-bit Program Files folder required elevated privileges to do some operations. My guess is that if using default folders for the 64-bit installation some permissions were not set correctly at install time. I know in the past I've had to manually change some permissions to prevent hiccups but not done so in a while. It could be one of these types of issue cropping up again. I hate giving full admin permissions to something as ropey as Command Center which doesn't even register its installed applications properly in Windows.
2016/12/23 21:30:03
Leee
*I deleted this post since it is now irrelevant*
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account