So-midi file with 10 tracks. I want to delete measures 25 thru 28 and have the space dleted and both sides come together.
So I select my 4 bars\all tracks. Now using delete special or cut special I check delete hole and shift by whole measures.
Events etc are deleted but the hole remains. So what does the delete hole box mean? nothing? I have not trie this in many years, but eveidently a. I am missing a step or B. Sonar cannot do it.
Thanks for any help

stratman70
So-midi file with 10 tracks. I want to delete measures 25 thru 28 and have the space dleted and both sides come together.
So I select my 4 bars\all tracks. Now using delete special or cut special I check delete hole and shift by whole measures.
Events etc are deleted but the hole remains. So what does the delete hole box mean? nothing? I have not trie this in many years, but eveidently a. I am missing a step or B. Sonar cannot do it.
Thanks for any help

I can reproduce the behavior you are seeing in Platinum "Manchester" and Sonar X3e on my system.
 
Test steps:
  1.  Create new project.
  2.  Insert new MIDI track.
  3.  Open PRV and enter 4 measures of quarter notes.
  4.  Clone MIDI track starting at track 2 with 2 repetitions.
  5.  Drag in Time line to select measures 2 through 3.
  6.  Select Tracks 1 through 3.
  7.  From the Edit menu, select Cut Special...
  8.  Check Events, Delete Hole, and Shift by Whole Measures.
 
Expected results:
  The MIDI data in measures 2 and 3 would be deleted and the data in measure 4 would move to the end of measure 1.
 
Actual results:
  The MIDI data in measures 2 and 3 were deleted and the data in measure 4 remained at measure 4 with a 2 measure blank hole.  [FAILED]
 
 
I executed the same procedure in Sonar X2a and found that the Delete Hole and Shift by Whole Measures functions matched the Expected results.
 
Workaround:
The only way Delete Hole works for me on MIDI tracks in Platinum and Sonar X3e is when I perform both of the following steps:
1.  Uncheck Non-destructive MIDI editing in Preferences > Customization > Editing. 
2.  Uncheck Shift by Whole Measures.
 
Conclusions:
The Delete Hole and the Shift by Whole Measures options changed on my system between Sonar X2a and Sonar X3e.
 
I don't know if the functional change between Sonar X2 and Sonar X3 was by design or whether it is a unintended regression bug that appeared in Sonar X3.
 
 
Hope this helps,
-- Ron

 
stratman70,
  Just a suggestion, but I would change your OP title to something like "Problem with Delete Hole function with MIDI tracks".  It might generate more interest from other members.
 
-- Ron

 
It sort of works for me (Delete Special, all boxed but one checked).
 
If the selection range in entirely within one or more audio tracks, it works as expected.  Following audio is moved back by the amount deleted.
 
If the selection range falls within a midi clip, only the midi notes are deleted leaving empty space behind.  The clip does not shrink in length.
 
If the selection range includes clips and spaces between clips that are wholly contained within the selection range, following clips and spaces will move back.  Sort of.  Sometimes moved back by the amount expected.  Often by some other amount that I can't quite figure out.
 
Combining the last two cases, if the selection includes entire clips and spaces, but also only a part of a longer [midi] clip in another track, then things are deleted, but nothing will move back into the hole, the longer clip preventing it from happening.
 
Surely this unpredictable and inconsistent behaviour has been reported.  Is there any news on improvements in the works?
 
Help isn't much help on this.  All it says is :
 
Delete Hole
If selected, the Delete Hole option removes the space in the track where the clip(s) had been. All clips after the deleted clip(s) are moved forward in time by the length of the deleted clip(s). Checking the Shift by Whole Measures option causes SONAR to move the following clips forward, but only as far as the nearest whole measure.
 
Forward ?
 
 

Paul P
Help isn't much help on this.  All it says is :
 
Delete Hole
If selected, the Delete Hole option removes the space in the track where the clip(s) had been. All clips after the deleted clip(s) are moved forward in time by the length of the deleted clip(s). Checking the Shift by Whole Measures option causes SONAR to move the following clips forward, but only as far as the nearest whole measure.
 
Forward ?
 

We once had lengthy discussions here about the meaning of "forward" on a DAW screen.
According to my logics forward means "away from the start point, advancing" (toward right on the screen), but according to some others it means "towards the front/beginning". I haven't bothered to do serious work to find out what is correct, as english isn't my native language.
Or, could "forward in time" mean something else as simply "forward"?
 
But then, according to some a clock running backwards would move its hands forward, right?
 
Anyway, I'm still at 8.5 and never had problems with delete hole-function.

EDIT:
OK-Tried Ron's workaround and it worked perfectly. Thanks very much
 
 
Just a rant by a guy upset....
When you say you never had problems with this, are you saying it works as I described originally?
And I know their was a lengthy discussion and nothing got done. 
So i guess this is just another bug that will again be forgotten about which I think truly "stinks" 
I am talking Midi only here. 
Imho this is really an example of who cares, enough folks aren't complaining about it I guess. 
Makes a guy really happy that he upgraded every year since the late 80's. 
 
Kind of like my profile always showing offline. Reported to CW in length and detail, more than once, no one cares enough to do anything about it. 
Oh well same ls same old

Yes, I can confirm that in X3, if you selected any audio and/or midi tracks that no data in the selected region, they would collapse as expected. Just upgraded to Platinum (working on first project with it) -- and the behavior has changed. It seems if a track in the selected region has no data, it does not collapse as expected, while those that have data do.
 
EDIT: I opened another project, and it works as expected sometimes. Don't know if it's the way the tracks/measures are being selected, etc...but it's definitely inconsistent.
 
 

 
Maybe we could trade the next New Thing for Delete Hole getting fixed.
I'd be happy with 12 installments of only bug fixes.
 

+1. I wasted 15 minutes yesterday only to find out that Delete Hole does not work in Manchester as before.

Rons advice did work, but it is a work around. I was able to delete the 4 bars and the hole and everything lined up. So the fix should be pretty easy. Of the 10 tracks in the project, 4 of them had no midi in those 4 bars but the work around still worked.
I use midi all the time...I have a bunch of old sequences from when O I toured as a one man band years ago (yes I know, one man whatever, $$ was good though)
Editing them is not the easiest thing in Sonar. I am just trying to update most of them for maybe a short run of playing some weddings, etc. 
I need to remember to note what I feel good be easier...so I can contribute to the midi update post of late.