Hello, im just wondering, why is the speed effect implemented as a video processing effect, instead of a movie playing clip parameter?
It seems a lot easier to just increase the current frame pointer by a lower amount when fetching frames instead of doing some kind of magic when processing input frames? Is that the way its done? Btw, 90% of the stuff can be done with such simple parameters, for instance opacity, speed, scale, position and the possibility to keyframe them. Going back and forth between kdenlive and premiere, i really miss those parameters. Any architectural problems? Dan? Thank you. Slavko 2009/10/2 Mikko Rapeli <mikko.rapeli at iki.fi>: > Just tried reproducing other bugs and noticed that I can't move a clip > to the end of another clip, both using speed effect. > > Project is file attached. This show up in log: > > kdenlive(4577) Render::mltMoveClip: ////// ?LOOKING FOR CLIP TO MOVE, > INDEX: ?2 > kdenlive(4577) Render::mltMoveClip: // ERROR MOVING CLIP TO : ?222 > > -Mikko > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Kdenlive-devel mailing list > Kdenlive-devel at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/kdenlive-devel > >
