What is the recommended way to apply the same Time remapping to more than one clip. There appears to be no way of copying the settings.
I can achieve it by converting two clips to a Sequence, but previewing of the effect is barely playable, even with proxy clips. It did render OK though.
Iâd venture a guess that you might be the first person to have this need, itâs definitely not something Iâve seen others talk about or had a need for myself. Time remapping is usually very specific to the clip youâre applying it to, so I doubt this need has had a lot of thought at all.
Remapping a sequence is probably the best bet right now. Does that really penalise playback harder than playing a sequence with all the same clips individually remapped?
Remapping can be a relatively âexpensiveâ operation. And I suspect some of that might have to do with efficiently seeking through your source files and needing to decode everything from the nearest I-frame to get to the actual next frame to display. If you really need real-time playback with heavy remapping, it might be worth testing with proxies (or transcoded source files) that have no inter-frames, in containers that are optimised for random access. Theyâll be larger, but should be much faster to seek in.
Would you mind sharing a bit more about exactly what you are doing where it makes sense to be sharing a remapping with multiple clips. Thereâs probably the seed of a good feature request here if the whole problem is well understood. And there are other difficulties with remapping, for things like motion tracking, where effect keyframes are not remapped.
Thankyou for your reply
This is not critical for me, as I can achieve the desired result with a sequence, or just applying the same settings on each clip. As a new user of Kdenlive I was just not sure if there was another more efficient method.
My requirement was due to applying an overlayed clip onto a background clip, and requiring the same timing for both overlay and background. I can appreciate this may be one of the few situations where there might be such a need.
It is worth noting that playback is more efficient when the clips remain seperate with identical time remapping. It is therefore a shame the settings cannot be copied and pasted as is possible with rotoscoping keyframes.
Like I say, no big deal.
I had the same need. After complex gluing of overlaying clips with fragile motion tracking, I wanted to adapt the animation speed at various places. Time remap could not be applied to the default master âsequence 1â but could be applied to a sequence created from the selection (see timeline menu).
This was my first use of video editing SW and I was surprised by the smooth learning curve and planty of helpful tutorials.
1 Like
I found this to be a curious claim/problem - because there isnât really any sense of a âmasterâ sequence in kdenlive, âsequence 1â is just the first created, but it can be deleted and should be able to be used identically to any other sequence you later add.
And I donât recall seeing that problem in the brief testing I did to confirm remapping works on a nested sequence. But that said: today, with then 25.04.1 appimage, it doesnât appear to work on any nested sequence. Things just go badly and/or then lead to a crash.
What version of kdenlive are you using (and what build/platform)?
@berndmj can you reproduce this, or have I mucked something up locally / need more coffee?
I just tested it and it works fine - no crashes or anything (25.04.1 Flatpak and appimage on Pop!_OS 22.04). The sequence I used only had a few clips in it and no other sequences, so YMMV.
Oh, sorry - though now youâve made me wonder if Iâve also confused what @jbrezmorf was talking about too - what this thread was originally about, and what I thought Iâd tested successfully at the time of my first reply, but which isnât working for me now, is applying the remapping to a nested sequence.
It wfm with 25.04.1 with remapping ordinary clips. But trying to remap a nested sequence clip goes Very Badly.
âŚ
Oh, this is going to be fun - it appears to be broken, with much the same result, in every appimage back to 24.12.2. But it works as I remember it working if I test it in my -dev branch âŚ
So now I wonder if itâs some config difference between my main editing machine and dev VM - some change not yet pushed to a release branch - or something Iâve changed.
âŚ
And it looks like itâs something in my âmainâ config - because the 24.12.2 appimage works as expected in my dev VM, and indeed there is no difference I can see between doing it when nesting sequence 2 in sequence 1, or vice versa. But thereâs something strange going on which can upset this âŚ
So, you mean a sequence in a sequence in a sequence?
No, just a sequence in a sequence. But I see thatâs what you meant now by âno other sequencesâ 
We need better language for describing this unambiguously âŚ