https://bugs.kde.org/show_bug.cgi?id=417076
Bug ID: 417076 Summary: Timeline time scale is not correctly modified when loading or creating project with non-default frame rate Product: kdenlive Version: git-master Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: alridd...@googlemail.com Target Milestone: --- Created attachment 125629 --> https://bugs.kde.org/attachment.cgi?id=125629&action=edit Screenshot showing a 25fps project, but the timeline scale has 50fps. SUMMARY The default project profile for my kdenlive config has 50fps. When I create a New project with a profile of 25fps, or load a 25fps project from disc, the time scale at the top of the timeline is not correctly updated for the new project, and still shows 50fps. By binary search of the recent commits, I have found this this issue was introduced in the following commit: f9491a9e397777830ff02f1da94d80f09c015fc3 "Attempt to fix crash after profile change" STEPS TO REPRODUCE 1. Load kdenlive with its default configuration. (e.g. 50fps) 2. Create a new empty project with a different fps (e.g. 25fps) 3. Manually set the timeline cursor to a non-zero position on the timeline. OBSERVED RESULT The numerical cursor position below the monitor does not match the position on the timeline scale, and the numbers on the timeline scale have the incorrect number of frames per second. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 31, Linux 5.4.12 (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION The attached screenshot is a new empty 25fps project created after kdenlive was started with 50fps in the default profile. The highlighted title shows the correct project profile fps, and the indicator below the project monitor shows the correct position for the cursor of 00:05:00. The highlighted cursor position on the timeline scale shows it is incorrectly at 00:02:25, and also that the scale has 50 frames per second. i.e. The position of the cursor is the correct number of frames from the start, but the wrong number of seconds. -- You are receiving this mail because: You are watching all bug changes.