BenMMusTech
Wow some of these are really odd. I've experienced a cople, but the resetting of plugins (touchwood) seems to have been fixed. And it was fixed, when I got a new beefy computer. Perhaps there's a link? It would be an odd one, for sure. Memory perhaps memory leaks and plugins resetting?

It probably depends on which plugins you use. For example I had major issues with Native Instruments synths resetting in Sonar for ages, and then a fix was rolled out for that. Then the Quadcurve EQ had a huge problem with it (I'd open a project and every instance would have this random 16dB boost or cut in the same frequency), others reported that one, and then it stopped happening. I don't recall an "official" fix being rolled out for it, and I talked about it on the beta team. And then this almighty problem with Waves and Fabfilter EQ's. Waves Q10, Waves SSL Channel, Waves V-EQ, Fabfilter Pro-Q 2. They're all being reset at random times. I doubt whether it has anything to do with hardware issues - my machine is reasonably powerful, all up to date and runs everything else perfectly. I haven't seen any Fabfilter EQ's reset themselves in Reaper, and I've also used the plugin a lot in Mixbus without any issues. It's just been Sonar. 

The most annoying problem I run into is that if you export a mono file that's close to the maximum headroom as a mono file, you'll think you're saving it but the saved version will be clipped destructively. The only way to solve this is to save the mono file as stereo. The same thing happens if you drag a mono file whose console channel is set to stereo interleave into the browser. When you drag it back from the browser, it will be clipped.
 

Anderton
The most annoying problem I run into is that if you export a mono file that's close to the maximum headroom as a mono file, you'll think you're saving it but the saved version will be clipped destructively. The only way to solve this is to save the mono file as stereo. The same thing happens if you drag a mono file whose console channel is set to stereo interleave into the browser. When you drag it back from the browser, it will be clipped.

As I do work a lot with export audio in my work flow (I always do mixing with audio only, synths are rendered to audio) I had struggled also a long time with this stuff. But once I found out that an export of a stereo track to a mono file is always +3dB, I managed to find the solution. So if I want that the target of my export file is mono, then I always ensure that I force the audio track in Sonar to be mono. Unfortunately this is not so easy when you use a (not split) synth track, because you have to split the instrument track first, set the audio track to mono and then use "Make Instrument Track" to recreate a single track for the synth (if you want just 1 track). But like that I have never had the problem with the +3dB (clipping) on mono export again!

I can find no way to sidechain anything without a crash. I insert the plug, switch on sidechaining, set up the send from wherever, ctrl S (because clicking on save crashes the program), press spacebar (or anything whatsoever), wait for the crash, reopen Sonar, reopen the project, and all is good again, until the next sidechain insert. Matters not the size or complexity of the project, the plug being used. It can be a single audio track with nothing on it. Always the same. Not sure which version this started from so I havn't bothered to backtrack. I just accept it now as part of the workflow. It's pretty much my only issue accept for continual crashes when dragging in audio clips compiling songs ideas from sample library's. That's a drag, save, drag, save, drag, save, or pay the price...........
 
PITA
 
BIBTPTACB,BTWW
(but I've been to PT and come back, because that was worse). So I'm still happy

Biggy for me
Midi Edit crashing

igiwigi
Biggy for me
Midi Edit crashing

 
As I said yes that's my biggy too, Solution is Save, save save. or use Home Studio for all editing and return to Splat for audio etc. Did you get your free version of HS? 
http://forum.cakewalk.com/Free-copy-of-Home-Studio-m3718860.aspx
 
 

sharke
There has been more than one occasion when I've requested a simple design improvement or reported a seemingly trivial bug only to be told that it couldn't be done or that fixing it would break another part of the program.

 
Yes that is a fairly strong sign of fragile code.
 

sharke
One example was when I reported that automating a ProChannel's FX Chain on/off button would not work unless the ProChannel in question was open in the console (same thing with the arpeggiator on/off button). I was told they were aware of it but had no intention of fixing it because doing so would break other things. Another example is the fact that hitting the "show automation lanes" button when no envelopes already exist automatically creates a volume envelope which takes control of the volume fader whether you want one or not,. When I suggested that hitting this button should result in an empty automation lane in this scenario, I was told that it was not possible for an automation lane to have nothing in it. These things suggest to me that the Bakers were restricted in some ways by legacy code dependencies and/or internal architecture which wasn't future proof and would require extensive rewrites to correct. If being able to automation the FX Chain on/off button would require a huge rewrite of a part of the program, it wouldn't be considered cost effective. Especially given that only a minority of users would ever want to actually do that. 

 
Wow, interesting issue cases there. It appears that they were already hitting the wall of decision on whether to patch-up or re-architect.
 

sharke
I'm sure much of this legacy code goes back a couple of decades, and that a lot of it is rock solid. But there must be aspects of it which weren't designed with 2018 software design in mind and replacing it would be a huge task, much like upgrading the NYC subway's ancient signal system (some of which is pre-war!). Things would have to be taken apart and put back together again, and who knows what kind of problems would ensue.

Wow yes, ground-up rearchitecting requires down time, which does not translate well to the release treadmill demanded by market pressures. Nevermind something the magnitude of upgrading the NYC signal system! There is a glimmer of hope that this transition to BandLab will offer an opportunity to rethink and retool. That's really why I'm hanging on right now - I have a feeling that Noel will get to finally scratch some itches that have been bothering him for a while now (heh - I almost said "bugging him").

losguy

sharke
There has been more than one occasion when I've requested a simple design improvement or reported a seemingly trivial bug only to be told that it couldn't be done or that fixing it would break another part of the program.

 
Yes that is a fairly strong sign of fragile code.
 

sharke
One example was when I reported that automating a ProChannel's FX Chain on/off button would not work unless the ProChannel in question was open in the console (same thing with the arpeggiator on/off button). I was told they were aware of it but had no intention of fixing it because doing so would break other things. Another example is the fact that hitting the "show automation lanes" button when no envelopes already exist automatically creates a volume envelope which takes control of the volume fader whether you want one or not,. When I suggested that hitting this button should result in an empty automation lane in this scenario, I was told that it was not possible for an automation lane to have nothing in it. These things suggest to me that the Bakers were restricted in some ways by legacy code dependencies and/or internal architecture which wasn't future proof and would require extensive rewrites to correct. If being able to automation the FX Chain on/off button would require a huge rewrite of a part of the program, it wouldn't be considered cost effective. Especially given that only a minority of users would ever want to actually do that. 

 
Wow, interesting issue cases there. It appears that they were already hitting the wall of decision on whether to patch-up or re-architect.
 

sharke
I'm sure much of this legacy code goes back a couple of decades, and that a lot of it is rock solid. But there must be aspects of it which weren't designed with 2018 software design in mind and replacing it would be a huge task, much like upgrading the NYC subway's ancient signal system (some of which is pre-war!). Things would have to be taken apart and put back together again, and who knows what kind of problems would ensue.

Wow yes, ground-up rearchitecting requires down time, which does not translate well to the release treadmill demanded by market pressures. Nevermind something the magnitude of upgrading the NYC signal system! There is a glimmer of hope that this transition to BandLab will offer an opportunity to rethink and retool. That's really why I'm hanging on right now - I have a feeling that Noel will get to finally scratch some itches that have been bothering him for a while now (heh - I almost said "bugging him").

Well all I can say is that I hope they take their time and don't feel pressured by the market or the Cakewalk community or anyone else to resurrect Sonar ASAP. I'd love to see them start something from scratch, helped along the way by the inclusion of Sonar's good parts. 

My issues are:
 
*Something not right with aux tracks. A few issues listed in the topics below, and sometimes aux tracks just go completely silent. I stopped using using Aux tracks and went back to normal buses and the problems went away.
http://forum.cakewalk.com/Soft-Synth-Bleed-Between-Tracks-m3687247.aspx 
http://forum.cakewalk.com/Where-is-that-phantom-audio-m3708038.aspx
http://forum.cakewalk.com/FindPost/3722493
 
*The audio engine often randomly stops, even when opening a project and press play, have to repeatedly keep hitting the reset audio icon.
 
*Some plugins, from my experience mainly waves don`t keep their settings open opening a project.
 
*Soft synths go out of time, especially where looping is concerned.
 
*Crashes on play after deleting information in the event list view.
 
*Automation sometimes doesn't work.
 
*Normalize bug: Video to reproduce here https://www.youtube.com/watch?v=f5tQxFQdXF4
forum thread http://forum.cakewalk.com/FindPost/3658242 
 

Adobe Audition got a complete overhaul between versions 3 & 4, but some modules came back as they were. If torn into its piece parts, it would be interesting to see what SONAR would look like if it could be "built to 2018."