https://bugs.kde.org/show_bug.cgi?id=368962
Bug ID: 368962 Summary: Git master:2016-09-17:Changing project FPS corrupts clip segments on timeline Product: kdenlive Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: evert.vors...@yandex.com This is totally related to bug 357780 - In fact, it is just a subset of the issue. I saw someone get a bug fixed on project FPS change, and thought I would start small. Sooo, what's needed to see the issue quite clearly is a special clip. Start a 25fps project, and make a generator that counts the frames. Use about 3000 frames to make the issue painfully obvious. Render this generator to get a clip at 25fps. Import that rendered clip into the project, and select a section from the clip, say from frame 1400 to frame 2000. Drag this segment into the timeline. Dragging your cursor over the timeline shows the frames 1400 - 2000 in the clip. Now, change the project framerate to 50fps. When dragging your cursor over the segment on the timeline, frames 700 - 1000 are now displayed, instead of frames 1400 - 2000, with each frame duplicated. Conceptually, if you select a segment from a clip, you are interested in something that happens in that range of frames. When changing the project's framerate, the range of frames should be preserved. The simplest formula for this is from Orig_Start/Orig_Fps*Dest_fps, rounded up to the nearest integer, until Orig_Stop/Orig_Fps*Dest_Fps, also rounded up to the nearest integer. There might be a frame or two extra or taken away from the clip on the timeline, however this is much better than displaying the completely wrong segment of the source video. Until this is fixed, changing the framerate on a project completely corrupts all the clips on the timeline. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.