I can confirm that delete hole is working on audio data. I just tried after reading this. I actually had to go to the manual and carefully read how to do it. I honestly thought the feature was MIA because I delete data by dragging, right clicking and selecting delete. There's no delete special option if you drag to highlight and right click to bring up the menu. Using the timeline and a higher level menu option are required. I'm feeling stupid again. 
 
In my defence, I think the bakers should tweak this so that I can swipe across the data and access delete special by right clicking. No?

I'm hoping that we can edit multiple tracks as if we were editing the stereo mix down file.

If I cut a section and paste insert it elsewhere in the stereo file, then what I hear played back should sound like when I edit the multitrack file (within reason, taking into account that effects or long MIDI notes that overlap the edit area might differ slightly).

Basically as I described here in the ideas forum:
http://bakery.cakewalk.co...ting-a-stereo-wav-file

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?

I will formulate my statement differently:
 
For those who think that changed in Lexington remove hole behavior in not a bug, everything is fine as before.
For those who think that the change is a bug, it is still there in 2017.1
 
peace

I've made a couple of videos to illustrate my dilemma more fully:
1) Sonar 2016.12 (Delete Hole Not working)
https://youtu.be/1kTh0CyS4PI
2) Sonar Kingston (Delete Hole Working)
https://youtu.be/93ZhJCX0wR8
Hopefully, this makes it clear as to exactly what I'm talking about.
Please refrain from posting workaround suggestions.
If there is a setting that will correct this in the most current version, then please post it.
 
(I tried to embed the videos, with no luck. Apologies.)

If delete hole works with audio then I am and a happy camper, I thought id didn't work any longer period.  I will check it out when I get back to the cave.
 
Thanks for the good news Craig

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.

wtreppler
I've made a couple of videos to illustrate my dilemma more fully:
1) Sonar 2016.12 (Delete Hole Not working)
https://youtu.be/1kTh0CyS4PI
2) Sonar Kingston (Delete Hole Working)
https://youtu.be/93ZhJCX0wR8
Hopefully, this makes it clear as to exactly what I'm talking about.
Please refrain from posting workaround suggestions.
If there is a setting that will correct this in the most current version, then please post it.
 
(I tried to embed the videos, with no luck. Apologies.)

As mentioned above, data being present in the "hole" for audio seems to be required. This is similar to the thread quoted in the OP with the comments about SONAR deselecting tracks which have no data in them prior to processing the delete hole algorithm. In the first video posted, you will notice that track 3 is deselected when you process delete hole. It seems to only make sense that the deselection occurs prior to the delete hole function.
 
In the second video, you will notice that Track 3 remains selected.

mettelus
It seems to only make sense that the deselection occurs prior to the delete hole function.

Certainly that is what is happening, but I don't think it makes much sense. It worked correctly (for audio at least) in the Kingston release. Hopefully it will again when ripple editing is introduced.

wtreppler
Please refrain from posting workaround suggestions.

I mean no dis respect but This ^^^^ is a quote I never like seeing.
If there is a work around wouldn't it be nice if it was posted. That way if someone (just like you) is having this problem and searching for help they stumble on this thread looking for a work around but cant find one because the OP simply doesn't want to hear it. As much as we want to believe this is "my" thread, it really belongs to cakewalk.
 
Also sometimes workarounds help us stumble on to other things which help create ideas and sometimes better ways of doing things.
Lets hope we see Ripple editing soon :-)

Thanks mettelus. Hopefully, this can help the programmers. Maybe all they have to do is move a line of code. Who knows?

mettelus
As mentioned above, data being present in the "hole" for audio seems to be required. This is similar to the thread quoted in the OP with the comments about SONAR deselecting tracks which have no data in them prior to processing the delete hole algorithm. In the first video posted, you will notice that track 3 is deselected when you process delete hole. It seems to only make sense that the deselection occurs prior to the delete hole function.
In the second video, you will notice that Track 3 remains selected.