Bug 459012 - When time remapping, markers do not move
Summary: When time remapping, markers do not move
Status: REPORTED
Alias: None
Product: kdenlive
Classification: Applications
Component: Video Effects & Transitions (other bugs)
Version First Reported In: 22.08.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-11 23:09 UTC by Clive Galway
Modified: 2025-05-21 16:44 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Clive Galway 2022-09-11 23:09:21 UTC
SUMMARY
***
If you place two markers on a clip, then use time remapping to play the section of the clip between the new markers faster, then the markers do not move together
***


STEPS TO REPRODUCE
1. Place marker A at 1:00 of a clip on the timeline
2. Place marker B at 10:00 of a clip on the timeline
3. Use Time Remapping to make betwen 1:00 and 10:00 play 10x faster

OBSERVED RESULT
The bar for the clip on the timeline, gets shorter as expected, but the markers stay in the same Y position of the clip

EXPECTED RESULT
The markers should get 10x closer together, effectively moving marker B further to the left. You are marking a point that something happens in the clip, and as you sped up part of the middle of that clip, the thing the marker B marks now happens earlier in that clip. Marker A should remain at the same point in the clip

SOFTWARE/OS VERSIONS
Windows: 21H1
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Martin Bolding 2023-04-24 08:46:09 UTC
I agree with the original post.

It would be MASSIVELY helpful if, when the speed of a clip is adjusted either by **Time Remapping** or **Change Speed** that the timings of other keyframeable effects already applied were adjusted correspondingly (or that there was an option to do so).

Is this being considered for inclusion in a future release?