Created attachment 103986 [details] Project at 30 FPS I created a 30FPS project using containing titles, clipped audio files, and a clipped 30FPS video. I re-used the same project to create an introduction that uses exactly the same assets, but a 60FPS video. Since the project was first created in 30FPS, it renders as 30FPS just fine. Since kdenlive keeps track of frames, not durations, if I change the framerate of the entire project to 60FPS, the timing of everything gets thrown off. Aside from the entire project being half as long, everything looks just fine in the timeline (it's all lines up correctly). However, the "begin" and "end" timings for the audio and video clips are off. I have uploaded sample renders as examples of the result: * Original project, 30 FPS: https://youtu.be/lXyIRzt4Fsg * Changing the settings to 60 FPS: https://youtu.be/oWvjQbdvuo0 * Changing the settings to 59FPS: https://youtu.be/Fn7EisV6Dco Is it possible to change the framerate of the project while keeping all the timings the same?
I'm tempted to just manually open the text file and edit all the 'in="2387" out="2484"' values to double (or halve?) them to fix this problem. Is there a standards document that lists all the attributes, so I can find which ones are tied to the framerate?
@me...: All MLT frame positions are, erm, in (project) frames and thus tied to the framerate. @OR: can you please attach a simple minimized project example? Does this trigger on any kind of clip, even on image, color, and title clips? Can you simply create a short video clip, just one or two seconds, then a project for this with 30fps, and finally attach that? Thank you very much for your cooperation!
This report is related to very old unmaintained version. A lot changed since then, especially the timeline got a complete rewrite. Please try with the current Kdenlive AppImage version 20.12.2 https://download.kde.org/stable/kdenlive/20.12/linux/
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!