https://bugs.kde.org/show_bug.cgi?id=364428
--- Comment #1 from Evert Vorster <evert.vors...@yandex.com> --- Hmm.... I did a bit more searching on this. Take a long clip, and just stick the second half of it on the timeline. Apply freeze effect stopping the action about halfway through. This all works as expected. Remove freeze effect, and apply speed effect, 2x speedup should do it. Apply freeze effect again. Now, when scrolling over the clip, you see frames from the first half of the input clip, if not just the first frame on it's own. These are frames that were never put on the timeline, so it would appear that the freeze effect is confused by the speed effect, and then refers to the first frame of the source clip, rather than the frames exported by the speed effect. I hope this helps you in tracking down the bug. Not sure on how we will fix it, though. Looks like the motion effects operate at a lower level, and might need to produce a "virtual clip" that the effects lower in the stack it operate on, with fake starting and ending frames, numbered from 1 - end.. Kind regards, Evert -- You are receiving this mail because: You are watching all bug changes.
