In the new version 19.04 on half of my clips the speed effect works, on the other half it doesn't (Kdenlive 19.04 on Linux mint 18.3 with MLT 6.13).

- It works on clips or parts of clips that I moved directly from the project bin to the timeline. These clips have in the timeline the same name as the actual movie-file (e.g. Cambodia.mp4)

- It doesn't work on clips that I moved from the Library to the project bin and from there to the timeline. These clips are named *.mlt in the timeline.

With other words: clip's that have been stored in the library are still un-speed-able for me (neither up nor down)

karlfee wrote:In the new version 19.04 on half of my clips the speed effect works, on the other half it doesn't (Kdenlive 19.04 on Linux mint 18.3 with MLT 6.13).

- It works on clips or parts of clips that I moved directly from the project bin to the timeline. These clips have in the timeline the same name as the actual movie-file (e.g. Cambodia.mp4)

- It doesn't work on clips that I moved from the Library to the project bin and from there to the timeline. These clips are named *.mlt in the timeline.

With other words: clip's that have been stored in the library are still un-speed-able for me (neither up nor down)

I reproduce. Will open issue.

Hi,

If I understand the original problem and circumstances correctly, think I've noticed the same.
But I think it is happening due to a different reason.

https://bugs.kde.org/show_bug.cgi?id=407439


It seems that Kdenlive has a generic problem with managing tags inside project file. It might be due to project file syntax.

When a project file gets over certain size (on my Dell Inspiron 15R SE 10 GB RAM, Manjaro Stable this is approx. 1.6/2.0 MB), Kdenlive struggles keeping up with updating tags when actual clips are moved.

I'm experiencing this problem for good few years of using consecutive versions of Kdenlive, this bug was reported at least 3 times, I think I've also seen it reported on forum(s) few times, and nobody seems to be doing anything about it. Solely for that reason I decided to assign higher severity (grave), please correct if that is wrong.

https://bugs.kde.org/show_bug.cgi?id=367984
https://bugs.kde.org/show_bug.cgi?id=386877
https://bugs.kde.org/show_bug.cgi?id=392670


I think the main if not only source of those problems is an action of moving clips on timeline. Depending on variation, different results occur:

======

STEPS TO REPRODUCE - SPEED FX DEFAULTS TO 100%
1. Put clip on timeline
2. Trim beginning
3. Apply speed fx and change value
4. Move that clip on timeline
5. Play or render

OBSERVED RESULT - SPEED FX DEFAULTS TO 100%
1. Speed fx setting remains at set value
2. Clip plays from beginning (ignoring trim) and at 100%

However, disabling and re-enabling Speed Fx for that clip usually brings back the trim point at the beginning of the clip (if applicable) and always restores the actual playing/rendering speed of the clip from the defaulted 100% to the value set by editor before the entire operation.

EXPECTED RESULT - SPEED FX DEFAULTS TO 100%
1. As above (speed fx setting remains at set value)
2. Clip plays from the trim point and at speed of set % value

======

STEPS TO REPRODUCE - CLIPS RANDOM SHORTENING OR DUPLICATION
1. Place many clips on timeline (can't determine whether it's the number of clips in project bin, number of clips on timeline, or project file size (i.e. by having very few clips but with lots of effects))
2. Mark a large number of clips on timeline (can't determine how many)
3. Move those clips
4. OPTIONALLY if project file is not large enough, continue working with project)
5. Attempt to do with clip anything that is related to it's position and length on timeline (i.e. add marker and then try to edit it, add effect with keyframes and setup some keyframes, try to re-trim the clip or move the clip on timeline)

OBSERVED RESULT 1 - CLIPS RANDOMLY SHORTENED
1. All moved clips are trimmed massively, sometimes to only few frames
2. All moved clips play from clip start not the trim set by editor

OBSERVED RESULT 1 - CLIPS DUPLICATED
1. All moved clips are duplicated and offset in a specific way: an original clip has it's clone stuck back-to-back to it's end on the same track. If one or more of those clips had speed fx added, there will be various errors related to that clip not found and content of these errors will be something like this: no such marker, clip not found, cannot complete this action, etc.

EXPECTED RESULT - CLIPS RANDOM SHORTENING OR DUPLICATION
1. All clips are only moved (they remain their trimming and are not duplicated)

======


SOFTWARE/OS VERSIONS
Windows: N/A
macOS: N/A
Linux/KDE Plasma: this problem seems to occur on various platforms. Mine is Manjaro Stable 18.0, Kdenlive 19.04.0, MLT 6.14.0-5.
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.57.0
Qt Version: 5.12.3