SUMMARY Extracting a frame from a clip in the clip monitor -- either "Extract Frame..." or "Extract Frame to Project..." -- extracts the wrong frame. Especially towards the end of long clips. STEPS TO REPRODUCE 1. Create a project (test project was 1280x720, 30 fps) 2. Add clip (test clip was 20:00:00 or so; 30.038 fps) 3. Select clip. 4. In clip monitor, navigate near end of clip. Note frame image. 5. Extract frame OBSERVED RESULT Extracted frame is *not* the frame pictured in the clip monitor. EXPECTED RESULT Extracted frame is the frame pictured in the clip monitor. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: applimage KDE Frameworks Version: appimage Qt Version: appimage ADDITIONAL INFORMATION This *may* be related to the difference in frame rate between the project and the source clip. Or it may not: transcoding the source clip to 30 fps still exhibits this behavior -- but not as severely (the extracted frame is "closer" to the frame pictured in the clip monitor; but still wrong). This is *not* the same as bug 384538. This is not using a proxy clip.
I found the same issue and waiting the correction. The workaround is to put the clip in the timeline and extract the frame from the project monitor.
Git commit dc3340cc67dfdc300a7177525fd3b808ad6c8fbc by Jean-Baptiste Mardelle. Committed on 31/07/2019 at 06:59. Pushed by mardelle into branch 'Applications/19.08'. Fix extract frame retrieving wrong frame when clip fps != project fps M +2 -2 src/monitor/monitor.cpp M +7 -1 src/monitor/monitorproxy.cpp https://invent.kde.org/kde/kdenlive/commit/dc3340cc67dfdc300a7177525fd3b808ad6c8fbc
Seems this issue still exists in 20.04.1b from Appimage. Possible regression ?