Bug 407439 - Multiple errors about timeline clips' length and speed fx due to issues with tags management in project file
Summary: Multiple errors about timeline clips' length and speed fx due to issues with ...
Status: CONFIRMED
Alias: None
Product: kdenlive
Classification: Unclassified
Component: Effects & Transitions (show other bugs)
Version: 20.12.0
Platform: Other Linux
: NOR grave (vote)
Target Milestone: ---
Assignee: Vincent PINON
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-11 21:59 UTC by krewetki
Modified: 2021-03-03 23:07 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:
fritzibaby: Brainstorm+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description krewetki 2019-05-11 21:59:45 UTC
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 beginngin (ignoring trim) and at 100%

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
Comment 1 krewetki 2019-05-11 22:03:41 UTC
I forgot to add:

SPEED FX DEFAULTS TO 100%

When this happens, disabling Speed Fx for that clip and re-enabling it, 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.
Comment 2 alcinos 2019-05-13 00:19:28 UTC
I can't reproduce any of this.
As of 19.04, changing speed is achieved by right-clicking on the clip and choosing "change speed", can you confirm this is what you are doing?
Comment 3 krewetki 2019-05-17 21:41:17 UTC
When I have time, I can try to reproduce with 19.04 but it will be potentially long because this problem with tags management inside project file ONLY occurs when the whole project is big enough. Starting a blank project with 3 tracks and few clips will never reproduce this.

I have a huge project, started in ver 18x and had to downgrade from 19.04 otherwise couldn't even open project.

In 18x Speedup and slowdown works correctly only until a clip has been moved on timeline which makes me think it's the tags management issue rather than SpeedFx itself. Of course, I might be wrong.

Meanwhile, who can attempt to reproduce on ver 18x to see if my observations on tags management are correct?

Also, status is "needs info" and "waitig for info". Is this something I need to provide?
Comment 4 alcinos 2019-05-17 23:20:13 UTC
Ah, there was an error in your bug report, it was indicating kdenlive 19.04 as the version.

Please note that the speed management has been *completely* rewritten in 19.04, thus I don't expect any bugs to carry over to the new version (it doesn't mean that no new bugs appeared). We are aware that the speed effect was causing a lots of issues in 18.x.

We are not going to fix the old version, so I encourage you to try in the new version to see if it works better for you, and reopen a new issue if you encounter issues.

If you have issues opening your old projects, feel free to open an issue about that. A common source of bug is the GPU acceleration (Movit). Make sure it is disabled in the preference, especially when you save your project in the old version.
Comment 5 krewetki 2019-05-18 10:47:03 UTC
I just tried 19.04.
Apart from all other bugs, tags management is still wrong.

When I insert 2 markers to markup split points then split track into 3 parts and apply 300% speed in the middle, only the first tag remains (others do disappear) and the first marker is moved so it appears in an incorrect place.

I'm sure I'll notice further bugs stemming from tags management, and I'm sure nobody will do anything about them for another few years.

Also, 19.04 is not backward compatible - won't open any projects created in ver 18x
I have a huge project, that I can't afford re-doing from scratch - will take at least another 4-5 weeks that I don't have.
What do I do now? PLEASE ADVISE HOW TO OPEN OLDER PROJECTS IN 19.x

P.S. I've been reporting this tags issue for YEARS and Kdenlive team decided to focus on Fx's that hardly anyone uses anyway.
Comment 6 emohr 2019-05-19 19:04:31 UTC
Marker move when speed is changed.
Confirmed. I opened issue: https://invent.kde.org/kde/kdenlive/issues/193. 

Load old project. 
Please try with the current Kdenlive AppImage version 19.04.1b to see if there are any packaging issues https://files.kde.org/kdenlive/release/. 
If the problem still occur please upload your .kdenlive project file that we can test.
Comment 7 rafamar.mm.ig 2019-05-19 20:58:20 UTC
(In reply to alcinos from comment #2)
> I can't reproduce any of this.
> As of 19.04, changing speed is achieved by right-clicking on the clip and
> choosing "change speed", can you confirm this is what you are doing?

One of the things that do not like the new version. Before with the effect was perfect, now it is very impractical. The idea is not bad, but the effect was better, although like everything in kdenlive it gave many errors. I would not have removed.
Comment 8 rafamar.mm.ig 2019-05-19 21:34:14 UTC
(In reply to krewetki from comment #5)
> I just tried 19.04.
> Apart from all other bugs, tags management is still wrong.
> 
> When I insert 2 markers to markup split points then split track into 3 parts
> and apply 300% speed in the middle, only the first tag remains (others do
> disappear) and the first marker is moved so it appears in an incorrect place.
> 
> I'm sure I'll notice further bugs stemming from tags management, and I'm
> sure nobody will do anything about them for another few years.
> 
> Also, 19.04 is not backward compatible - won't open any projects created in
> ver 18x
> I have a huge project, that I can't afford re-doing from scratch - will take
> at least another 4-5 weeks that I don't have.
> What do I do now? PLEASE ADVISE HOW TO OPEN OLDER PROJECTS IN 19.x
> 
> P.S. I've been reporting this tags issue for YEARS and Kdenlive team decided
> to focus on Fx's that hardly anyone uses anyway.

Still giving many errors, accelerates or slows down, but does not respect the content of the clip, I do not mean that change the duration, that this is obvious, I mean that parts of the video are lost or it remains frozen. I would like to know from the kdenlive team what system, distribution and version I can try to use version 19.04 so that when I report a bug, I am not told that it is because I do not use the appropriate version, both the appimage and the flatpak version they give the same mistakes.
Comment 9 alcinos 2019-05-20 14:24:12 UTC
RafaMar: does it happen with any video sample? If not, there is probably something special with your video file, please post a sample somewhere so that we can have a look
Comment 10 rafamar.mm.ig 2019-05-22 19:49:17 UTC
(In reply to alcinos from comment #9)
> RafaMar: does it happen with any video sample? If not, there is probably
> something special with your video file, please post a sample somewhere so
> that we can have a look

Alcinos: Sorry, it happened with an .mlt file. I exported it as video and it worked well. I made some video tutorials and sometimes I adjust the speed of the clip in relation to the speech and with the effect it was very easy for me because it accelerated or slowed down and saw in real time the duration of the clip with respect to the audio.

I think both effects could coexist in kdenlive, the only thing I would do is limit the effect to positive values, since it was in the negatives where I gave the errors. For more defined adjustments or investments the new one is fine.

And finally, you would be so kind to recommend me an appropriate distribution and version to be able to work well with kdenlive where there are no errors for library issues. Of all the systems in which I have made use of kdenlive 19.04 ... the one that has given me the best result with the latest version of Deepin
Comment 11 rafamar.mm.ig 2019-05-28 17:22:29 UTC
I asked for a recommendation of which distribution and version was recommended to me to be able to test the new version ... and there is no answer ... if on the part of the team there is so little interest perhaps I should be unconcerned and look for other alternatives.
Comment 12 emohr 2019-05-28 17:46:28 UTC
Recommendation is the AppImage. Either the version 19.04.1c https://files.kde.org/kdenlive/release/ 

or Kdenlive_Nightly_Appimage
https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/

As I'm on Windows I don't know the best Linux distro. I test with current Lubuntu in a VM and it runs smooth.
Comment 13 rafamar.mm.ig 2019-05-28 17:52:14 UTC
(In reply to emohr from comment #12)
> Recommendation is the AppImage. Either the version 19.04.1c
> https://files.kde.org/kdenlive/release/ 
> 
> or Kdenlive_Nightly_Appimage
> https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/
> lastSuccessfulBuild/artifact/
> 
> As I'm on Windows I don't know the best Linux distro. I test with current
> Lubuntu in a VM and it runs smooth.

Thank you so much emohr. It is a pity that this new version of so many errors, those who use windows have many more alternatives, but in Gnu / Linux there is a problem in having a video editor that works well.
Comment 14 emohr 2019-05-28 18:17:38 UTC
At the moment use the AppImage 19.04.1c to avoid any packaging issues. It's the most stable version. Make sure your Linux is up to date.
Dev working on the Flatpak.
Comment 15 rafamar.mm.ig 2019-05-28 18:41:04 UTC
I just tried it in deepin, which is rolling release, and it gives too many errors to be able to work with it. Anyway thank you very much. I'm a little tired of the kdenlive errors, it's also true that the type of montages I do are advanced, but if you put some options or tools are for them to work. The composition of tracks does not work, the first keyframe of the effects can not be moved ... well there are so many errors that it is best to stop wasting time with this application and start looking for other alternatives, I had many illusions with the 19.04, had very good press and now I take a very big disappointment. Editions that could be done perfectly in past versions now in this new version are not possible. No doubt a step back, more would have agreed to continue in the line of 18.12 and solve some small things that failed. Well I said, thank you very much for the interest.
Comment 16 smihael 2021-01-18 20:00:56 UTC
I still have this issue with Kdenlive 20.12.0 and MLT 6.20.0. This bug appears each time I insert one big video recording file, then cut it into multiple parts using the razor tool and try to change the speed of one or more of these parts. 
Changing speed of such a part from 100% to 200% seems fine when previewing the video in the Project Monitor, but when I render the video the resulting part will play with 100% speed but only first half of the part will be shown.
Comment 17 TG 2021-01-22 07:34:00 UTC
I can confirm also the issue on speed change. 
I don't use the razor tool, so not sure it come from here.
with one video in the bin, if I use 3 parts of this video in the timeline and changed the speed with ctrl+click.
somme part are speed up, other or not.1sd
I''m searching the step to reproduce 100%
Comment 18 Julius Künzel 2021-03-03 23:07:45 UTC
Do you use the appimage?