2017 bugs part 3
In the PRV, on rare occasions changing focus from a drum track (diamond / percussion notes) to a standard MIDI track may continue to 
show percussion notes until the view refreshes. Workaround: Refresh the view.
Note On sometimes executes when adjusting Velocity in the PRV and may fail to shut off. Workaround: Click the MIDI Reset button.
When using Drum Maps, after opening the PRV the first click for adjusting Velocity may cause the value to unintentionally "jump" 
slightly. Workaround: Click again and adjust.
Improved redrawing of Controller Pane Velocity with Pen
Using Pen to adjust Velocity no longer causes notes to move unexpectedly
Preferences
"Share Devices with other programs" option is has been renamed to better convey what this setting does. It is now called “Suspend 
Audio Engine When SONAR is Not in Focus”
RU: Preferences > Project > MIDI > Frame Rate drop down had offset & overlapping text
3rd Party
VST2 and VST3 plug-ins that use sample position to playback data now stay in sync better with SONAR
Using Melodyne in the FX Rack will now recognize loop points in SONAR and stay in sync
Using Melodyne VST2 or VST3 in the FX Rack previously didn’t get the right sample position and could cause SONAR to not stay in sync
when adjusting the timeline position of the NowTime
Fixes and Enhancements
Artist, Professional, Platinum
Double-clicking a track could fail to maximize strip height in some situations
Track view no longer flickers when reordering tracks in large projects
Adjusting Take lanes height longer allows the Edit Filter to overlap other controls
Excluded synths no longer show in Instruments plug-in lists
SONAR no longer disappears behind other programs when switching Lenses 
Help will now correctly launch from Preferences | MIDI | Playback & Recording
Exporting as Raw Tracks - No Automation/FX now preserves the Comp on an audio track
New updates to SONAR no longer revert the theme to Tungsten after installing
Fixed a possible crash when dragging a MIDI clip to Matrix in localized versions of SONAR
The power indicator for a FX Bin will now stay in sync with the Frozen/Unfrozen state of a track
VST3 plug-ins now display correctly in the registered Plug-ins list in Plug-in Manager
Aim Assist now displays correctly when using the arrow keys to scroll in the PRV
The mouse position no longer displays only in the PRV when Aim Assist is turned off
Artist, Professional, Platinum
MIDI Port assignments are now saved with the project and will map to the same device on another machine
Resolved a possible crash when Auto-deleting synths via Track-delete
Auditioning with Note Chase plays notes from excluded clips
Custom names of VSTs not saved
Browser Notes do not allow to tab between fields
Loop recording in different sections resulted in many additional Take lanes
Muted takes are displayed in collapsed track
View Scrolls Away When Zooming or Enlarging Lanes
View wasn’t correctly scrolling when Maximizing Track or Bus Strips.
Artist, Professional, Platinum
Stability
Resolved a crash when opening the Staff View in a Normal project template 
Resolved a crash when re-assigning a send to a new Aux track
Resolved a crash when Exporting Audio
Resolved an issues for plug-ins with a sidechain could cause SONAR to hang on load
Resolved a crash on deleting tracks with project that contain hidden tracks
Resolved a crash after copying Step Sequencer clips
Resolved a crash using Aria Player
Audio Engine
Resolved a playback issue in WASAPI Driver Mode while Dynamic Arming is enabled
Patch Points were adding 6dB of gain in some situations
Export Clips > Follow Source now properly exports clips as Mono
The ProChannel now follows the The Global Bypass All Audio FX without disabling the individual modules
Editing
Splitting an audio clip could occasionally fail in SONAR Projects
Recording multiple passes of audio creates no longer creates overlaps
Resolved an issue where Slip-stretching the end of a clip could alter the clips start time
Updated an error in documentation for clip stretching Midi
Split tool now works as expected on step sequencer clips
Plug-in Support
Selecting MIDI In/Out in VST Soft Synths now works properly
Enable MIDI Output no longer displays in the Default Soft Synth Options. This depends on the synth and cannot be configured as a 
default but previously appeared as an option
Step Sequencer
Step Sequencer doesn't scroll as expected after expanding row
Step Sequencer frame is now fully themed
Step Sequencer clips copied to new tracks now link properly to the original
Expanded Step Sequencer rows are now themed as expected
Resolved an issue where bouncing Step Sequencer & MIDI clips together could result in data loss
Empty Step Sequencer cells in matrix do not update in duration
Matrix
No Undo for Delete of Empty Matrix Row
Resolved an issue where Matrix View cell could be delayed during playback
Stop All Cells now properly stops playback for cells edited during playback
Ctrl + click will toggle cell selection in the Matrix View
VST Scan & Plug-in Manager
Existing VST2 plugins in Plug-in Manager's folder tree look as if they are grayed out
If a VST3 plugin's name is changed in an update, VSTScan now no longer creates duplicate menu entries
VST2 plug-ins in existing custom plug-in layouts blank
Synth Rack
Synth Rack Collapses After Adding Synth with "Open These Windows: Synth Rack View" enabled
Synth Rack keyboard shortcut is now consistent with other views
Undocking the Synth Rack and disabling floating could cause the view to not reopen
Synth Rack related keyboard shortcuts now respond properly
Lenses
The Virtual Controller when deselected in the lens, will no longer appear as an optional input
Reduced the amount of UI flicker when switching lenses/screensets
Improved highlighted Text in Lens Manager's drop-down 
Control Surfaces
Adding a Marker from a Control Surface would fail
Multiple Control Surface plug-ins could cause the ACT mapping XML file to become corrupted
Project & File Handling
Track templates no longer expand / open Inspector
Add Track flyout would occasionally appear on Project Load
Track name in Properties Inspector now updates as expected
Instruments assigned to a Drum Map now open as expected from the track icon
Resolved an issue with .WRK files loading in SONAR
UI
Improved the displayed text in the Browser after searching and then clicking away

There were not many pot holes were there ^ 
I dread to think what the outstanding list looked like.
 
I'd love to post a screenshot of all the bugs I logged, I assume that database has been taken down.

Wow, you guys spending all this time arguing over a dead program?
 

rscain
Wow, you guys spending all this time arguing over a dead program?

 
Discussions/debates/the search for "truth" or differing views does not have to be boxed up and categorized as "arguments".

Anyway I think it's part of the mourning process. It will pass and I am past it.
I have nothing to publicize, peddle or sell (nor have I ever) so I'm done.

Arguments are Alex's speciality. Now that all the bakers are gone he's come back for his victory lap. He didn't have the stones to try it before. I guess the mods don't have banning authority, or they may just be sitting back enjoying the show.

I'm not arguing with anybody- I'm just pointing out that SONAR bugs exist, and one user's experience may be very different from another's.
 
Just as a hypothetical example, before this bug was fixed:
 
Resolved a possible crash when using two-finger scrolling on the track pad
 
If somebody was always two-finger scrolling they might have had a different impression of SONAR from someone who used a mouse scroll wheel. 
 
Likely things like this in other DAWs too, but I personally would not argue with anyone who said they were experiencing SONAR bugs, I've seen and continue to see them.

Well, I do not understand why the people that are trashing Sonar are here at all? Is it to convince folks like me and many others that we should MOVE away from Sonar. We shouldn't care about the DAW we like and use everyday because YOU have issues?  Why should that matter to me?
It doesn't because I DO NOT HAVE ISSUES WITH SONAR. 
 
There are so many here ( the majority by far) bummed that Sonar will no longer be developed and more importantly will they really have a way to reinstall the programs THEY WANT TO USE. See the key is they (being me and many others) want to use. 
 
If I had all the issues with Sonar that some keep on harping about and had already moved on to another daw I would NOT be here posting. 
Whats your point? Is it to tell us we are stupid or amateurs because we use this program but do not find it unbearable and cumbersome? 
We are idiots for not moving on to a new daw now or even before?
I see NO other reason for you folks to be here in this conversation. Oh wait, you spent $$$ and time on Sonar. Your entitled. Entitled to What?  To what? Most of us are worried about what is happening. You are just here to trash it. So?

ampfixer
Arguments are Alex's speciality. Now that all the bakers are gone he's come back for his victory lap. He didn't have the stones to try it before. I guess the mods don't have banning authority, or they may just be sitting back enjoying the show.

Let me refer to what you actually wrote yesterday, people can see the full thread here:
http://forum.cakewalk.com/FindPost/3717199
 

ampfixer
Alex, why did you come back? Nobody has missed you and yet here you are, back at your old haunt, doing the same things that got you turfed out. It's really sad that you couldn't just move on and have decided to come back here and have one last kick at Sonar. Pathetic man, really sad.

 
And let me refer you to my response to that.
 

CakeAlexS
Actually what got me turfed out is responding to these sort of confrontations and letting myself get wound up by it, so forgive me if I don't engage any further. Happy New year Amp.

 
So ditto copy and paste.
Sorry Amp it's not working this time, stick and stones and all that.

The bug thing is a red herring. Cakewalk did not fail because of bugs. The list of bugs for most programs is likely to be as long. The fact that people most likely to have compiled such bug lists are paying customers kinda negates such a concept. My friends and associates that did not bother with Sonar were completely unaware of most of that list because they were uninterested.

marled
To me that sounds too simple what you guys are saying. I don't want to negate what you say, there are surely bugs, but I doubt that all of them are Sonar bugs. So a developer must first find out what is the cause for what a bug report says. And first you must isolate the problem and in many cases that is fairly difficult. You can not simply say if a plugin runs in one DAW and not in another that it's the 2nd DAWS failure, it is not that simple!
And also concerning priorities in a software product: You really can imagine if you have read different threads in a forum how different the wishes and priorities of DAW users are, because they all use it in other contexts and with other workflows.

What we're saying is not "too simple" at all. Sonar really does have a lot of bugs, quirks and fatal problems that have nothing to do with hardware or 3rd party plugins. For instance, you'd be hard pressed to find hardware reasons for any of the myriad of weird problems which affect things like clip and automation editing, or the GUI. And while comparing whether a plugin works fine in DAW A versus DAW B might not be conclusive, the fact that a plugin seems to have no problem in any DAW except Sonar would seem to suggest very strongly that the fault was with Sonar.
 
And the fact that a bug might be hard to isolate or create a recipe for does not mean that the responsibility of fixing the bug isn't still with Cakewalk. I identified a ton of bugs which never got formally reported primarily because it was impossible to come up with a set of steps to reproduce the bug reliably. These are the hardest bugs to fix, and Sonar has a lot of them. People regularly experienced crashes and hangs with "delete hole," for instance, but it was impossible to work out what combination of factors had to be present for it to happen. This doesn't mean that the fault didn't lie with Sonar's code, however. I reported that crash almost 4 years ago as a beta tester, attaching to it a project in which it was happening. Got a reply back that they could reproduce the assert. Great, right? You'd think this assert would be a good clue as to why the operation was crashing Sonar - after all, that's the whole point of asserts. 4 years later, the bug is still showing as "open" in my testing account. It was never fixed. Looking through my beta account I see loads of weird problems that really should have been fixed but weren't - for example, deleting a synth with MIDI-output enabled screws up the MIDI inputs of other tracks. Despite providing clear steps to reproduce, that bug is still "open" as well, after almost 2 years. 
 
Problems like this affect the core operation and basic functionality of the program and they should have been prioritized, yes. Editing the time in a project and using MIDI tracks are core functionality of any DAW. They're not niche features and they should be absolutely rock solid before diverting resources to things like new features.