I tell ya, if they implemented this, Sonar would go up in leaps in bounds in my estimation. I would feel so much happier about using it and my whole workflow (and hence creativity) would soar. This along with patch points and aux tracks would end up being my favorite ever Sonar enhancements. It's not a glamorous feature to tout (especially since it should have been done years ago) but by golly is it needed.

I can't imagine what it must feel like for a pro sat in front of Sonar with a client who wants a section deleted from a song and having them just not understand why a simple one click ripple delete can't be done.

+1

A big +1 to the original post (and probably the following posts as well). I remember feeling quite shocked when I contacted tech support more than a decade ago and was told that I had to use a workaround for this. And I never thought it would last until 2016...

Yes, I vote for Craig's "meat cleaver" approach. I would find it easier to just deal with a few leftover split MIDI notes than manually shifting things around like we need to do currently.

Have you submitted a support ticket using the example you used here? I would suggest doing that if you haven't already...

There's a bunch of everyday things which, when I return to Sonar, I have to think "now, how does this work again" and often I have to ask the veterans here.
 
Some are there since Sonar 4, my first version.

sharke
[...] It's not a glamorous feature to tout [...]

I disagree with this, since I feel this is the foundation required for elegant arrangement. Being able to chop and drag "chunks" all over a project without concerns for markers/automation/takes/etc. would make sandboxing go at lightning speed and not distract the user from composition. If it is a "completely vertical" section, markers, tempos, and automations should all go with it, and snap to sections they but up against. From the same reasoning, being able to hit Ctrl-A and drag that vertical section would allow the entire project to be slid left/right (or even grab the timeline and just move it - keeping all else "relative"). As alluded to, most video software has these features baked in (ripple delete, clip snapping, etc.) solely because people hate to watch "black screens" during a video.
 
As Craig mentioned, I too sandbox audio (even for what will eventually become MIDI parts) only because I can drag/drop those all over without little worry. When a "what just happened" snags me, I am often done for the night.

I'd like to propose my workflow to Cakewalk, but would be interested if anyone has improvements to the suggested workflow before I do.
 
The one thing I would want to avoid is getting bogged down with something like "Well, we really need check boxes for what we want to remove," or "it should automatically move any time signature it finds to the beginning of the hole," etc. I think of the odds of implementation are greatest if a really simple change covers 90% of what people need, as opposed to a complex change covering what 95% of what people want.

mettelus

sharke
[...] It's not a glamorous feature to tout [...]

I disagree with this, since I feel this is the foundation required for elegant arrangement. Being able to chop and drag "chunks" all over a project without concerns for markers/automation/takes/etc. would make sandboxing go at lightning speed and not distract the user from composition. If it is a "completely vertical" section, markers, tempos, and automations should all go with it, and snap to sections they but up against. From the same reasoning, being able to hit Ctrl-A and drag that vertical section would allow the entire project to be slid left/right (or even grab the timeline and just move it - keeping all else "relative"). As alluded to, most video software has these features baked in (ripple delete, clip snapping, etc.) solely because people hate to watch "black screens" during a video.
 
As Craig mentioned, I too sandbox audio (even for what will eventually become MIDI parts) only because I can drag/drop those all over without little worry. When a "what just happened" snags me, I am often done for the night.

What I meant by it not being a glamorous feature to market was, I would imagine most people would just assume that a professional DAW could do that anyway. Frankly like most people I was shocked that it didn't, but muddled along anyway.

sharke
What I meant by it not being a glamorous feature to market was...

It may not be glamorous, but a big part of what Cakewalk is doing these days involves optimizations and other improvements. While these may not matter to new users, as the response in this forum indicates, it's very important to existing users and that is part of marketing...the more an existing user likes SONAR, the more they'll talk about it and the happier they'll feel about using the program.
 
I just hope that something like this could be implemented easily, without having to rip the program apart and put it back together again as that is always a candidate for the Law of Unintended Consequences.