Bug 385542 - Clips with Speed effect reset when moved back with other clips
Summary: Clips with Speed effect reset when moved back with other clips
Status: RESOLVED FIXED
Alias: None
Product: kdenlive
Classification: Applications
Component: Effects & Transitions (show other bugs)
Version: 17.04.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Vincent PINON
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-10 04:22 UTC by MJ Vilches
Modified: 2020-02-13 20:50 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
fritzibaby: timeline_corruption+


Attachments
A video showing the bug (1.63 MB, video/mp4)
2017-10-10 04:22 UTC, MJ Vilches
Details

Note You need to log in before you can comment on or make changes to this bug.
Description MJ Vilches 2017-10-10 04:22:47 UTC
Created attachment 108262 [details]
A video showing the bug

I was editing a timelapse video. I each clips in the video a Speed Effect. One of the clips was cut in many portions, and I added more clips after it with speed effect as well. Later, I saw a portion of the previous clip that I want to remove, so I trimmed it and deleted it, leaving a space. I selected all the clips after the space through Shift+drag mouse over the clips to  move them, all at once, back to fill in the space. But after doing that, the first clip from the selected clips(after the removed portion) along with every clip after it, resets to it's normal speed, removing the speed effect and making every clips start from the beginning of the raw clip.

A workaround that I did to prevent this is, instead of moving the clips all at once, I move them one by one. But I do hope this bug get's fixed on future updates.

Anyways. Thanks to the Kdenlive dev team for providing a nice free video editing software!
Comment 1 Marcus 2018-02-04 00:40:38 UTC
Might be similar to bug 385780 - I am affected by this bug, too.
Comment 2 farid 2020-02-13 20:50:55 UTC
Hi

Ever since version 19.04 the speed effect has been rewritten. Can you please test if this is happening in the latest version (19.12.2)? Do try the AppImage since it'll guarantee that all dependencies are met. 

Closing, but please reopen if it is not fixed.

Thanks