17b6 Ripple Overwrite oddity
Posted: Tue Dec 29, 2020 8:27 pmI have a timeline in Edit with a series of clips in V1: let's call them Va, Vb, and Vc and they are all cuts with no space between them. On V2 I have three three short transitional clips: let's call them T1, T2, and T3. T1 straddles the Va/Vb cut, and T3 straddles the Vb/Vc cut, covering over them. T2 is in the middle of Vb. (I've attached a screenshot below.)
Now I pick a clip in the Media Pool that's shorter than Vb and do a Ripple Overwrite. What happens is that T1 gets cut in half at the Va/Vb cut point, while T2 and T3 are not cut. The shorter incoming clip replaces Vb, and T2 and T3 are moved left as appropriate since the clip is now shorter. T3 is still straddling the cut between the new clip and Vc.
But the half go T1 that was originally over top of Vb has now been moved left as far as T2 and T3 were moved left.
If the incoming clip is longer, T2 and T3 are moved right (correctly) such that T3 still straddles the new clip and Vc cut. But the right half of T1 is also moved right.
In other words clips that are wholly over Vb (in track V2) are moved right if the incoming clip is longer and left if the incoming clip is shorter than Vb, which is pretty much correct. But it doesn't quite know what to do with T1, which should be left in place. So it splits T1 and then treats the part of T1 as if it were just another clip over Vb -- like T2 and T3 -- and moves it with the end of the incoming clip.
I get why this is happening: clips over the overwritten clip move together maintaining the same number of frames between them. It's not proportional, which could lead to the collision of clips. But I would ask if an exception could be made: if an overlaying clip starts before the overwritten clip and if it remaining there would not collide with overlaying clips from the right that might be moving left (due to a shorter incoming clip), just leave that clip in place and don't split it.
Make sense? I've attached three images: one showing the situation before Ripple Overwrite, one showing what happens if a shorter clip comes in and one showing what happens if a longer clip comes in.
Now I pick a clip in the Media Pool that's shorter than Vb and do a Ripple Overwrite. What happens is that T1 gets cut in half at the Va/Vb cut point, while T2 and T3 are not cut. The shorter incoming clip replaces Vb, and T2 and T3 are moved left as appropriate since the clip is now shorter. T3 is still straddling the cut between the new clip and Vc.
But the half go T1 that was originally over top of Vb has now been moved left as far as T2 and T3 were moved left.
If the incoming clip is longer, T2 and T3 are moved right (correctly) such that T3 still straddles the new clip and Vc cut. But the right half of T1 is also moved right.
In other words clips that are wholly over Vb (in track V2) are moved right if the incoming clip is longer and left if the incoming clip is shorter than Vb, which is pretty much correct. But it doesn't quite know what to do with T1, which should be left in place. So it splits T1 and then treats the part of T1 as if it were just another clip over Vb -- like T2 and T3 -- and moves it with the end of the incoming clip.
I get why this is happening: clips over the overwritten clip move together maintaining the same number of frames between them. It's not proportional, which could lead to the collision of clips. But I would ask if an exception could be made: if an overlaying clip starts before the overwritten clip and if it remaining there would not collide with overlaying clips from the right that might be moving left (due to a shorter incoming clip), just leave that clip in place and don't split it.
Make sense? I've attached three images: one showing the situation before Ripple Overwrite, one showing what happens if a shorter clip comes in and one showing what happens if a longer clip comes in.