Bug 349660 - Ripple delete doesn't work on last frame of a project
Summary: Ripple delete doesn't work on last frame of a project
Status: RESOLVED FIXED
Alias: None
Product: kdenlive
Classification: Applications
Component: Video Effects & Transitions (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: Vincent PINON
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-27 15:47 UTC by Sam Muirhead
Modified: 2016-08-08 16:12 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Three uneven length clips, after trying to delete from In to Out using 'Ripple Delete'. The last frame of the project cannot be deleted in with Ripple Delete. (97.24 KB, image/png)
2015-06-27 15:47 UTC, Sam Muirhead 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Sam Muirhead 2015-06-27 15:47:24 UTC 
Created attachment 93365 [details]
Three uneven length clips, after trying to delete from In to Out using 'Ripple Delete'. The last frame of the project cannot be deleted in with Ripple Delete.

The ripple delete function is working very well (I've mapped the shortcut to the 'U' key so that I can use JKL for transport and UIO for editing, without having to move my hand anywhere else on the keyboard).

The only minor trouble is that Ripple delete doesn't work properly when selecting the last frame of a project. On the track which includes the last frame, there's always one extra frame hanging around. An error occurs and the other tracks within the selected zone are completely ignored - see attached image.

Always reproducible.
Comment 1 Wegwerf 2016-07-29 07:12:19 UTC 
Sam, can you please try with a stable Kdenlive 16.04.2 to see whether your problem has been fixed or not? If the bug is fixed then I would like to ask you to close this report as RESOLVED. Thank you very much for your cooperation!
Comment 2 Wegwerf 2016-08-08 16:12:51 UTC 
I cannot reproduce this bug with the recent beta 16.07.90. So this seems to be properly fixed since some time. I'm thus closing this report as resolved/fixed. Please reopen in case you can reproduce it on recent beta or upcoming stable 16.08.0. Thanks!