FastBikerBoy

I wonder why that's not working. It works okay here (assuming there's nothing I'm missing of course).
Is it all projects or perhaps older ones created in a different version?

This is a new project started in X2.  That being said, I have done a fair amount of editing with split clips, copied clips and so on.  Nothing too major, but I have found with previous versions of Sonar (and probably dating back to when it was called Cakewalk Pro Audio too) that the "delete hole" function can be unwieldy or even erratic.

I'm currently in "composition mode" where I am throwing a few ideas about within a project, and there are things I love about Sonar that allow me to mess with arrangements, but alas "delete hole" is not one of them.  It will work with the project up to a point, but I find that after a certain amount of editing the "delete hole" function is not able to do what it says accurately.

sharke


You're lucky you can even check the "delete hole" check box. Sometimes that option is greyed out for me even though I have a chunk of project selected that spans all tracks. 

I've noticed that too.  It's very picky about what you have already selected and one gray area is including tracks that are empty, or have no clips within the range you are attempting to delete, or if you don't select all tracks, or whatever.  


If project content is relatively straightforward (i.e. all the clips are the same length, or there are minimal number of clips that have been edited or copied or stretched) then it all works fine.  That's why I sometimes resort to just bouncing down all the clips periodically so that I can get past the roadblock.  But sometimes I don't want to lose those individual clips, especially when I'm working on arranging a new song.

Skyline_UK

jrmunday


Just write a little event somewhere in the 'hole'.
It will then delete without any issues.
This 'bug' has annoyed me for years and years!

Yes, me too!  It always legs me up.  Cakewalk please fix!
It shouldn't be necessary to insert dummy events to do such a simple task.

I agree.  It should really be a simple two-step process:  (1) select range (2) delete hole across all tracks


You shouldn't even need to select the tracks or anything else.  To me, the idea of selecting which tracks you want to apply the "delete hole" function to is an edge case.  I am much more likely to want the "delete hole" function to work at the song level, so I shouldn't have to be selecting all the tracks.  It's an unnecessary step that I'm willing to bet complicates the code behind it all.