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. 

I haven't tried to move frozen clips, but I've moved midi clips and audio clips together and it worked the cats meow.

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.

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 ?

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.

bapu

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.

Okey dokey matey blokey.
 
TIA
 
 

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've done it quite a few times with 100+ frozen midi tracks/soft synth tracks and ripple editing worked perfectly for me, audio & midi.
Now, for a visual ripple editing indicator...

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.

Leee
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.

I don't think the intent behind freezing a synth is to freeze everything in position on the timeline. It's to "freeze" the synth's output into an audio clip - a temporary bounce to save on the CPU, and to allow you to start playback in the middle of long sustained notes without having to backtrack to the start of the note (although we have MIDI chase for that now). By freezing a synth, you're not making any final decisions on the timeline location of a synth part. Therefore I believe ripple editing should include both frozen MIDI clips as well as the resulting audio clip. I can't think of any reason why you'd want the audio to move with the ripple edit, but not the underlying MIDI. Paulo definitely has a bug worth reporting.