Ripple editing - just me or is this how it is?

 
Tried it out for the first time today (select all to move everything back to make room for a longer intro) which seemed to go ok, but I later discovered that it actually didn't move any of the midi clips that relate to frozen softsynths (instrument tracks) just the audio, so having moved everything to where I want it, once I had to unfreeze a synth for a tweak the clip was in the wrong (original) place. 

paulo
 
Tried it out for the first time today (select all to move everything back to make room for a longer intro) which seemed to go ok, but I later discovered that it actually didn't move any of the midi clips that relate to frozen softsynths (instrument tracks) just the audio, so having moved everything to where I want it, once I had to unfreeze a synth for a tweak the clip was in the wrong (original) place. 

Frozen synths might be the problem. Not that I think that's way it should be but I can "kind of" see how a programmer could overlook a situation like that.
 
I'd submit a bug report if I were you.

paulo

bapu

paulo
 
Tried it out for the first time today (select all to move everything back to make room for a longer intro) which seemed to go ok, but I later discovered that it actually didn't move any of the midi clips that relate to frozen softsynths (instrument tracks) just the audio, so having moved everything to where I want it, once I had to unfreeze a synth for a tweak the clip was in the wrong (original) place. 

Frozen synths might be the problem. Not that I think that's way it should be but I can "kind of" see how a programmer could overlook a situation like that.
 
I'd submit a bug report if I were you.

So you're saying that it's deffo not just me ?

I'm not at the DAW for another few hours. If I can remember I'll try that out.

I just did an experiment. Very simple project. 1 audio track and 1 instrument track (session drummer). I froze the instrument track and ripple edited in 4 measures at the beginning. Unfroze the instrument track and the clip had moved forward as expected.
 
Again this was about as simple as a project gets. So maybe a more complex project would create the problem.
 
My question is are you running the 2017.07 version? Cake did make some improvements to Ripple editing in the most recent version.
 
 

I always thought that was how it was supposed to work.  The frozen MIDI is "frozen" so therefore unaffected by any edits, including ripple edits.
Whenever I select "Ripple Edit All Tracks", I unfreeze everything, move the tracks and then re-freeze the tracks.
It's a bit of a hassle, but for me it's worth having Ripple Edit.  It still saves me a lot of time and work.

Nothing to see here . I stand corrected .
 
 
Kenny
 

paulo
So, in summary then.......
 
It's a bug, it's not a bug, it works fine, it's supposed to do that, why wouldn't it ? 
 
Well, I'm glad that's cleared up. 

Maybe its your approach, or the way you are using the tool/selecting data.
Have you tried Ripple editing selection only ? or are you using Ripple edit all ?
I selected groups of tracks using Ripple edit selection (not Ripple edit all tracks) and it worked perfectly moving frozen data and unfrozen data was there as expected.
 

Anderton
To add to what Chuck said, I just did "ripple edit all" with frozen instrument tracks.
 
The audio and MIDI both moved as they were supposed to. When unfrozen, both the MIDI and audio tracks remained in the place to which they had been moved from the ripple edit.
 
Paulo, see post #7, and then check your version of SONAR. If you're using 2017.07, post a recipe to reproduce. I can't get frozen tracks to move audio but not MIDI. You'll have to show me how to make it happen.

Well , I learn something new here new every day I haven't tried Ripple editing with frozen tracks yet ..
 
My post in this thread was based on the general behavior of frozen tracks that I had experienced over the years pre SONAR Ripple edit update ...
 
I had no idea that Cakewalk made it possible for frozen tracks to be edited and unfrozen placed exactly where the edits were done ..
That seems to be a game changer after all ..
 
I'm glad I saw your post
 
Kenny

chuckebaby

paulo
So, in summary then.......
 
It's a bug, it's not a bug, it works fine, it's supposed to do that, why wouldn't it ? 
 
Well, I'm glad that's cleared up. 

Maybe its your approach, or the way you are using the tool/selecting data.
Have you tried Ripple editing selection only ? or are you using Ripple edit all ?
I selected groups of tracks using Ripple edit selection (not Ripple edit all tracks) and it worked perfectly moving frozen data and unfrozen data was there as expected.
 

Anderton
To add to what Chuck said, I just did "ripple edit all" with frozen instrument tracks.
 
The audio and MIDI both moved as they were supposed to. When unfrozen, both the MIDI and audio tracks remained in the place to which they had been moved from the ripple edit.
 
Paulo, see post #7, and then check your version of SONAR. If you're using 2017.07, post a recipe to reproduce. I can't get frozen tracks to move audio but not MIDI. You'll have to show me how to make it happen.

2017.07
 
Might well be pilot error, hence the "is it just me?" part of the question.
 
What I did was Ctrl+A>options>Ripple edit all, then dragged the first clip back 4 bars to allow for longer intro. Maybe 12-15 tracks total, 5 audio only, the rest frozen synth instrument tracks. All seemed well until I later had to unfreeze one of the synths for a midi tweak and when I re-froze it went back to where it had been before the ripple edit. I didn't notice the position of the midi clip while I was doing the edit as I was in PRV by then toward the end of the clip and just deleting a couple of bum notes. Selected the freeze option again without really looking. Having seen what resulted, I did the same (minus the edits) with all the other frozen synths to see what happened and they all did the same thing. 
 
Tried exactly the same thing today with the same project and it worked as I would have expected. Well almost.....
 
A frozen clip that was 18:02:908 and whose corresponding unfrozen midi clip was now also 18:02:908 and event list showing first event at 18:02:908 became 18:02:927 once frozen again, but I already started another thread about his issue a while ago, so I'll leave that subject aside here.
 
Pilot error then ? Maybe, but I did exactly the same thing both times with different results, so go figure.......
 
Anyway, forewarned is forearmed and all that, so in future I'll be checking on the position of the related midi tracks before saving the project if I've used ripple edit, which in truth probably won't be that often anyway.
 
 
 
 

No nooo ... not playing the midi tracks ... recording the midi to audio ... instead of freezing.