SUMMARY While working on a video project with a three-digit frame rate count (such as 120 or 144 fps), many aspects of Kdenlive's user interface fail to properly work, creating bugs at certain places which make it more difficult to use. The most affected areas are as follows: -If playback frame rate is enabled for the monitor, three-digit outputs will be displayed in scientific notation. Instead of showing 144fps, it will display 1.4e+02fps. This is the less serious one. -Seemingly all elements of the interface in which the user can input the time, including the frame (for example, the current timeline position, or an effect's keyframe) will only display two digits. When the relative frame is below 100, this works properly, otherwise, only the first two digits are shown. For example, at 125 frames, it will show xx:xx:xx:12. If the arrows for one-frame movement are used, it will jump to the displayed time. In this case, it means it will instantly jump to frame 12. It is also impossible to manually input a frame above 99. STEPS TO REPRODUCE 1. Create a new project and set the project's frame rate to any value above 100 (144 was tested) EXPECTED RESULT On projects with a three-digit frame rate, all frame inputs should be displayed in three digits across the entire user interface. This does not appear to be a problem where the frame rate is static, such as a clip length in the project bin or the timestamps in the timeline. The playback frame count should also not try to truncate values with more than two digits (or at all). SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.20 (available in About System) KDE Plasma Version: 5.20 KDE Frameworks Version: 5.75 Qt Version: 5.15
Please try with the Kdenlive_Nightly_Appimage https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/. Some high fps issues are fixed.
Can we have feedback on this issue?
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!