This is related to bug 350948, but spelling out this specific feature might get it fixed, as it is particularly annoying... A clip of the bug in action can be seen on: https://youtu.be/3tuxCnzEoz8 Reproducible: Always Steps to Reproduce: 1.Load a clip 2.Select a segment somewhere close to the end of the clip 3.Drag into timeline. Make a good notice of what is actually occurring in the clip. 4. Go to project settings, and double the framerate. 5. Look at the clip on the timeline again, it will now show frames from earlier in the clip Actual Results: The clip on the timeline starts and stops on a different time after a fps change. Expected Results: The in and out frame numbers to be translated to the new framerate so that the segment displayed appears the same. related to bug: 350948 Thought you had fixed this with commit: "Fix in / out points broken when rendering a zone with an fps change" It might still be related....
This is still an issue in most recent git.
Created attachment 97214 [details] Simple project at 25 fps. So, to get some more detail on this bug. I made an extremely simple project, with one clip on the timeline. The clip shows my drone doing a slow 360 degree rotation over my hometown.
Created attachment 97215 [details] Output from the simple project Attached is the render from the simple project. Scaled down horribly and at poor quality to make uploading the file easy
Created attachment 97216 [details] Same simple project, as 50fps. So, I just changed the project framerate to 50fps, and saved it again.
Created attachment 97217 [details] Output from 50fps project So, here is the render from the 50fps project. As you can clearly see, it's not the same nice 360 rotation of the drone as earlier. The output is from much earlier inthe clip when the drone was still climbing to altitude.
Created attachment 97218 [details] Diff between original project file and 50fps one So, I did a diff, and can see that many of the parameters have changed with the framerate change.
Created attachment 97219 [details] Block of text that was hend edited So, I edited the 50fps project by hand, and change the in and out frames in that block of text with the following formula: (in_keyframe/original_framerate)*new_framerate=new_in_keyframe
Created attachment 97220 [details] hand edited 50fps project file The new project file, hand customised
Created attachment 97221 [details] The output from the edited 50fps file Here is the output file from the hand-edited file, this time with a little higher bit of quality. As you can see, it's the same 360 rotation as in the 25fps one.
Created attachment 97222 [details] diff between the 50fps project, and the edited one So, here is the diff between the two files. It would be great to have the bugs taken out of the change fps of a project feature. There may be other little bugs, and I will report them in a similar manner, but let's get this fix in first, please? This fix should be quite an easy one, as while the project is loaded, all the variables are in memory and easy to modify.
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 set the bug status 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!
Dear Andrew, changing status to REPORTED as I am the last submitter on this bug, awaiting an answer from the developers. I can confirm the bug still exists, and is rather severe for anyone who mixes clips with different framerates. -Evert--
Fixed! Thanks, JBM...