"Ripple Markers" bugs

[brian]

@DRM

@brian

Both of the examples being shown are resulting in clips being reordered.

I don’t think that behavior makes any sense to begin with. When a clip is moved beyond the group of clips it precedes with the Ripple buttons on, the expectation is that the rest of the clips will follow accordingly. This behavior of the group of clips not following the moved clip when it goes beyond the groups of clips is nothing more than the function breaking. If that can be fixed then the issue with the markers is easily solved.

I think this discussion relates to the one going on here:

Ripple All Tracks bug

I think the difference is that he is moving a clip backwards between two other clips - which ends up being an “insert” operation rather than a move operation. I think the ripple behavior for insert might be different than for move. I am kind of guessing here since I am not very familiar with all the ripple behaviors.

As Dan stated, some behaviors depend on whether the clip remains on the same track or moves to another track.

@shotcut

@brian

I am not sure what should happen to markers if clips are reordered with ripple markers on.

You can try to make it not move any markers in this case.

I could look into that. I think the marker ripple code does not know about other clips - but that is an implementation specific detail.