Speeding up deletes other tracks + Marker shifted by one frame

[ions]

Shotcut version 24.06.26
Windows 10

BUG 1: By speeding up one track, the others under and above disappear.

BUG 2: By setting a marker with “M” it comes shifted by one frame from the play head.

[brian]

@ions

BUG 1: By speeding up one track, the others under and above disappear.

You probably have Ripple All Tracks turned on.

@ions

By setting a marker with “M” it comes shifted by one frame from the play head.

I do not reproduce this. Maybe you are zoomed in on the timeline and they do not quite line up?

[ions]

BUG 1: Yes, Ripple is on! However, I didn’t have this behavior before updating. It was easier, when the other tracks just got cut by the length of the sped up track and not just deleted. I have a static image above all tracks, when the other track is sped up, the static one gets deleted. What’s the point of all that?
Otherwise, I have to untoggle and eventually toggle the Ripple delete button and split all overlapping thracks manually, so they remain synchronized. It means more work and has no sense.

Please, let me know, which last version didn’t have this behavior, so I can go back to it?

BUG 2: The marker comes shifted, when a track is splitted (“S”) and the play head is on the split, which I want to mark for a chapter.

[brian]

@ions

BUG 1: Yes, Ripple is on! However, I didn’t have this behavior before updating. It was easier, when the other tracks just got cut by the length of the sped up track and not just deleted. I have a static image above all tracks, when the other track is sped up, the static one gets deleted. What’s the point of all that?
Otherwise, I have to untoggle and eventually toggle the Ripple delete button and split all overlapping thracks manually, so they remain synchronized. It means more work and has no sense.

Related to these issues. Posting these so you can see some of the history:

Clip speed change + multiple tracks + ripple bug

Just had a look at the latest nightly and the change is a huge improvement over the previous behaviour. There is more “destruction” on the other tracks but it is very much intuitive and I can easily fill in the area if needed. Thank you.

Audio track change removes clip when ripple all tracks is on

What is your operating system? Windows 11 - Home (22H2) What is your Shotcut version (see Help > About Shotcut)? 24.04.28 Can you repeat the problem? If so, what are the steps? Create Video and Audio tracks on timeline Add suitable clip to video Add multi-track audio clip to audio track Open properties of clip on audio track and change audio track of clip If Ripple All Tracks is enabled then clips on other tracks will be removed. Apologies if this is intended behaviour but I don’t remembe…

@ions

Please, let me know, which last version didn’t have this behavior, so I can go back to it?

Any release prior to 24.06.26 would have the prior behavior.

@ions

BUG 2: The marker comes shifted, when a track is splitted (“S”) and the play head is on the split, which I want to mark for a chapter.

I do not reproduce that. What am I doing differently in my test?

[ions]

Many thanks for your suggestions. I’ll have to adapt to the new feature, I’m afraid.

As for the marker shift, I had this problem in the latest version. Now I downgraded it to 24.04.28 and it’s all fine now.

Thank you again!

[shotcut]

@ions

Otherwise, I have to untoggle and eventually toggle the Ripple delete button and split all overlapping thracks manually

You do not need to turn ripple mode on to use actions that inherently ripple such as Ripple Delete and Cut. However, you may need to toggle Ripple All Tracks.

Spilt now operates across multiple selections and groups as well as new Split All Tracks At Playhead action.

[ions]

@shotcut

Split All Tracks At Playhead

This is a helpful feature indeed! Thank you!

[daniel47]

I have also just experienced the marker off by on frame issue.
I believe it is related to the newly introduced time formats, as it only happens in non integer project framerates (ie: I can reproduce it in 29.97 but not 24 or 30)

• for 1080p29.97 i can see the issue starting exactly at the 34;00 second mark and ends at 59;21
• if changing the time format to “frames” it doesn’t happen anymore

here’s a demo with only a color clip in a new project