Bug 354940 - Corrupted project after Video Profile change e.g. 1080p50 > 1080p25
Summary: Corrupted project after Video Profile change e.g. 1080p50 > 1080p25
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR critical
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-06 10:24 UTC by cstark
Modified: 2016-08-05 17:42 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description cstark 2015-11-06 10:24:22 UTC
After change of Video Profile e.g. from 1080p50 to 1080p25 the project file gets useless.
All clips have double length, all in and out points are wrong.

I need this to render a p50 project to p25, because when I set r=25 in the rendering options using an p50 project, the video is ok but the container has a doubled time lenght which confuses some players.


Reproducible: Always



Expected Results:  
When a project changes then there should be a correct recalculation of all time/frame related content.

It would be great to implement this feature too:
The original/initial timings should be saved back in the project file and every recalculation should be based on that. Changes between 25 and 50 fps are easy and without rounding errors possible but not the 23 24 59 fps stuff.
Comment 1 George 2015-11-19 15:14:47 UTC
A similar issue happens to me as well:
Arch Linux 32-bit, kdenlive version 15.08.3-1.  

Additional information:
If the project resolution (under project settings) is changed from 1080p to 720p all the timings for the video is messed up.  Any videos that have been cut now have the cuts occurring in the wrong place.
Comment 2 qubodup 2015-12-13 20:50:29 UTC
Changing to a profile with a different FPS while already having clips in the timeline appears to have multiple side effects. Here is one in detail:

Fade effects' durations are changed to nonsense values.

Steps to reproduce:
1. Start kdenlive with a 1080p 30fps video default
2. Import 30 fps video
3. Drag video to timeline, cut it on left and right, remove all but the center part
4. Add fade in and out effects to video
5. Change profile to 1080p 25fps
6. Refresh the clip's properties view (click in timeline, then on clip)

Expected result:
1a. The duration values remain the same OR
1b. The duration values are approximately scaled to have about the same duration notwithstanding the change in frames per second

Actual result:
1. Both duration values are nonsensical (one is way too long, the other is 0)

Video:
https://youtu.be/pMNCAV9Q9Zg
Comment 3 qubodup 2015-12-13 20:57:56 UTC
One more issue:

Clips' starting position in the video file is changed to nonsense value while duration remains the same.

Steps to reproduce:
1. Start kdenlive with a 1080p 30fps video default
2. Import 30 fps video
3. Drag video to timeline, cut it on left and right, remember what happens in the scene, in particular how exactly it starts.
4. Move the clip to the left of the timeline.
5. Change profile to 1080p 25fps
6. Play back the project

Expected result:
1. The clip has approximately the duration and same start and end position relative to its video file (depending on whether the positions/durations can be divided evenly)

Actual result:
1. The duration appears to remain the same but the start position of the clip relative to the video file's length appears to be different

Video:
https://youtu.be/9ZXmKGAG2l8
Comment 4 Jean-Baptiste Mardelle 2016-01-01 01:42:27 UTC
Git commit 66eea0af8b418c42ac1768e9ab90537404010367 by Jean-Baptiste Mardelle.
Committed on 01/01/2016 at 01:10.
Pushed by mardelle into branch 'master'.

Fix various error corrupting project when changing profile's framerate

M  +1    -0    src/doc/kdenlivedoc.cpp
M  +2    -0    src/doc/kdenlivedoc.h
M  +1    -0    src/mainwindow.cpp
M  +2    -2    src/monitor/monitor.cpp
M  +2    -2    src/renderer.cpp
M  +1    -1    src/renderer.h
M  +1    -0    src/timeline/customruler.cpp
M  +4    -1    src/timeline/timeline.cpp
M  +1    -1    src/timeline/timeline.h
M  +21   -27   src/timeline/track.cpp
M  +1    -3    src/timeline/track.h

http://commits.kde.org/kdenlive/66eea0af8b418c42ac1768e9ab90537404010367
Comment 5 Wegwerf 2016-07-31 09:12:12 UTC
cstark, can you please test using the recent stable Kdenlive 16.04.2 version, with MLT 6.2.0+ at least? Does the bug still persists? If not, I would like to ask you to be so kind as to close this bug report. Thank you very much for your cooperation!