I must admit, I didn't expect to open this can of worms when I created the thread.
 
I'm running an Intel i7 3GHz CPU with 24GB RAM. SSD System drive, data drives are all 7200RPM. RME Fireface UCX. Minion plushy above left monitor.
 
Issues:
 
Delete Hole: Just. Doesn't. Work.
Any tracks with no content in the target area do not move. Tracks with content in the target area are moved. Project is all out of kilter with itself. The only work around is to delete the block and manually move the whole project after the area where the block is deleted. Annoying. Drove me bonkers and utterly messed up my 'user experience' until I came up with the work-around.
 
Attempting to copy an audio clip that has had Melodyne applied: As soon as I press CTRL+C (and I mean instantly, there is no hard drive activity or any kind of delay or anything), Sonar crashes to desktop with no warning, no attempt to elegantly exit. After this, I often have to go into the task manager and manually remove Sonar from running before I can run it again. This started occurring some patches ago when there had been no change to my system (other than Windows and AV updates of course). Frustrating as hell and a big smack in the face for my workflow. I use Melodyne a lot, not just for vocals, and this one thing causes me more workflow issues than any bug I've ever encountered.
 
All of these issues occurred on Win 8.1. After a completely clean Win 10 install they are still happening.
 
As of applying the July patch yesterday I have found all new bugs but I'm so sickened I haven't even bothered raising a ticket. Random glitching noises when I'm not playing a song. Omnisphere becoming unresponsive at random. To date Omnisphere has been the most unbreakable VST I've ever used so that's pretty damn impressive. I don't know if this issue is isolated to Omnisphere as I haven't heavily used any other of my VSTs yet to compare.
 
Although eligible for the lifetime updates, not responded yet. I'm afraid I'm deeply suspicious because to date I've seen no commitment to customer service since their transition to Gibson and I can't shake the feeling the lifetime updates is just to get an influx of cash then they create a new product with a different name that invalidates the offer. I'll ponder this some more.
 

As with other threads, I read them with amusement but mostly bemusement and rarely comment unless I think I can add something useful.  I am sure we have all read text be it in an email, letter or forum and applied our own perceived tone to the contents. It has a disadvantage over face to face communications where you have additional pointers to the underlying subtext or lack thereof. Still it seems that members apply their own subtext to posts often wrongly.
The current issues with support seem to have been acknowledged and evidence submitted that something is being done to alleviate the problem. Not great, but admission is the first sign to recovery (or so they tell me at GAS Anonymous) :)
I have lost count of the number of times I have seen threads started about bugs or something not working which is working for everyone else and it turns out to be down to the system environment, lack of understanding of the functionality or applying the functionality wrongly.  The only way to eliminate these causes is to explain in a logical order, the steps you have taken that cause the issue. If this can be replicated elsewhere and confirmed by other forum members chances are it is an issue with Sonar, if not it is more likely to be user specific. In either case people here are always willing to help.
If you take the delete hole issue mentioned, I have seen no massive outcry from the rest of the user population about this functionality not working (it has been there since X series) so it suggests it could be something closer to home.  What are the steps you take for this problem to occur?  I had to read the manual the first time I wanted to use it and even then I wasn't 100% sure I was using it the right way.
The Melodyne issue may be related to Melodyne, Sonar or both but a quick check of previous forum threads about Melodyne issues may point to a resolution or at least a common problem, once again a more logical run through of how you use it may help,given that it is fairly obviously not happening to everyone or there would be a massive outcry.

HatstandIf you take the delete hole issue mentioned, I have seen no massive outcry from the rest of the user population about this functionality not working (it has been there since X series) so it suggests it could be something closer to home.  What are the steps you take for this problem to occur?  I had to read the manual the first time I wanted to use it and even then I wasn't 100% sure I was using it the right way.
The Melodyne issue may be related to Melodyne, Sonar or both but a quick check of previous forum threads about Melodyne issues may point to a resolution or at least a common problem, once again a more logical run through of how you use it may help,given that it is fairly obviously not happening to everyone or there would be a massive outcry.

I love a good bit of condescension as much as the next person. Read the July update thread. Delete Hole has been acknowledged as a problem.
 
Read my actual post above properly. I say exactly what happens with Melodyne.

Roo Stercogburn
 
Delete Hole: Just. Doesn't. Work.

I'll start by saying that everything any Cakewalk staff has said here is true: right now it's a simple case of the demand outweighing the supply, and we're moving as quickly as possible to remedy the situation--I promise.
 
That said, I'll try to save you a little trouble here: The Delete Hole issue you're experiencing is a known issue, and this is most certainly not the first thread about it. Part of our Commitment to Awesomeness is to introduce a full-fledged Ripple Editing function in SONAR. This will not only fix the Delete Hole issue, but also enhance the audio editing in SONAR as a whole. But these things take time to rebuild, revamp, and test, so we appreciate the patience while we work out the kinks.
 
Regarding the suspicions of Lifetime Updates being a cash-grab... This is also not the first thread about that. I'm sorry to disappoint, but I assure you it has to do with nothing more than the fact that we are indeed listening and reacting to the feedback we receive.

Roo Stercogburn
 
I love a good bit of condescension as much as the next person.

And there you go. A good example of misinterpreted subtext.
:)
No condescension intended just pointing out that written text can be misinterpreted and that it is easier for others to help with problems if they know the logical steps and see if they can replicate them.
The Melodyne issue you mentioned does not have a great deal of detail. does this happen with Melodyne open, is it just a clip that had the effect applied, saved and then a copy attempted? 
I must admit I wasn't aware the delete hole issue was mentioned in the July update. It looks like an honest straightforward reply has been given on that one.