tenfoot

Anderton
Are you sure Delete Hole doesn't work for audio projects? I use it without problems...mostly soundtracks with lots of tracks, and narration with one or two tracks. Maybe I'm avoiding some use case that makes it not work?

In my experience delete hole does not work correctly with audio either. If there is no data on a particular track in a selected range, any clips after the deleted range on that track are not moved.

Yes, this is correct and I forgot to mention it because I just slip-edit whatever clip was before or after to create something in the hole.

Ditto.. Sonar has so many great NEW function's but so many bugs and issues with basic operations. Please please guys can we fix the editing and redo the automation asap. Its a mess and clunky. I still prefer 8.5 for this but there are so many cool new tools now it's not realistic going to 8.5 but the wk flow in 1/2017 is way slow now with so many more clicks needed to do simple tasks.

Bristol_Jonesey
What part of the automation needs redoing?
 
I use automation extensively and do not experience problems

same here. the only oddity I see in automation is with Zoom.
sometimes when you undo a zoom it will also undo a lane height. its aggravating but besides that.
Automation is almost flawless.

I use delete hole all the time in delete special when comping or rearranging projects and I use this mostly on entire projects at once (i.e all tracks) but have done it on specific tracks.  What is the issue? All this said,  I have experienced issues where in some cases, when I do this, audio sometimes fall out of sync and the project becomes a mess which fortunately gets fixed with undo.   I've since found  that if I bounce to clips before hand, the issue goes away and delete special (with delete hole) works fine.   And yes, it does nothing on tracks with no date in which case you need to cut special and paste to move the tracks around.   Markers become very important in these instances

stxx
I use delete hole all the time in delete special when comping or rearranging projects and I use this mostly on entire projects at once (i.e all tracks) but have done it on specific tracks.  What is the issue? All this said,  I have experienced issues where in some cases, when I do this, audio sometimes fall out of sync and the project becomes a mess which fortunately gets fixed with undo.   I've since found  that if I bounce to clips before hand, the issue goes away and delete special (with delete hole) works fine.   And yes, it does nothing on tracks with no date in which case you need to cut special and paste to move the tracks around.   Markers become very important in these instances

I made a couple of videos of the bug:
1) Sonar 2016.12 (Delete Hole Not working)
https://youtu.be/1kTh0CyS4PI

2) Sonar Kingston (Delete Hole Working)
https://youtu.be/93ZhJCX0wR8

ralf
I also agree that the "delete hole" problem should be fixed, no matter if and when ripple editing will provide an alternative for this feature.

I would assume (no insider knowledge) that ripple editing would replace the Delete Hole functionality, not provide an alternative. With true ripple editing, you have a choice whether opening up a space would close up or stay open. Similarly, when inserting you would have a choice whether to replace data or push it down the timeline.

ralf
I also agree that the "delete hole" problem should be fixed, no matter if and when ripple editing will provide an alternative for this feature.
 
After all, this is a regression bug (something that worked before), so to fix it, one only has to compare the working code and the no longer working code, and find the difference. (Sure, may be more complex depending on what was changed and if it was a side effect of some other change, but still regression bugs tend to be rather easy to fix.)

This is somewhat irrelevant as Software often has so many dependencies that you just can't make that assumption.  Also, If the Software team is working on a future implementation of something that fixes other bugs in a previous implementation, they will weigh the resources needed and if the issue is complicated to fix (which this must be as I'm sure take lane and comping changes have made this area very complex) often just wait to fix it in a future release under the new way.  This is common but only if the new implementation will be released in a reasonable time frame.   User report bugs, and the delete hole is a serious bug at times, needs to be fixed in some reasonable timeframe somehow.   
 
WORKAROUND to the delete hole of tracks with no data.   Knowing this is an issue, you need to make sure the clips in the delete range all have data.   You can temporarily slip edit the clips into the space, you can bounce to clips and include clips on both sides of the space, or create silient clip to take up the space.   I tend to bound the clips if the space is large and encompasses many tracks or slip edit if the space is small.

Fix please.