On Sat, 2007-08-11 at 23:54 +0200, Herman Robak wrote: > On Sat, 11 Aug 2007 23:28:35 +0200, David McNab <[EMAIL PROTECTED]> > wrote: > > > On Sat, 2007-08-11 at 23:17 +0200, Herman Robak wrote: > ... > >> Please consider if the motion estimation software written from > >> scratch by Zachary Drew (http://www.tc.umn.edu/~drew0054/) is > >> better suited. It is probably faster. > > > > Might need a lot more work though. It appears (fwict) that it only > > calculates the motion, and doesn't generated re-timed video frames. > > It is limited to one format, thus making it incompatible with > Cinelerra's floating point colour. > > A lot of work will be required no matter what if the framerate > resampler is going to fullfill its potential. I'd rather have it > integrated with the timeline UI than have it as an effect plugin > only. Then dragging edit points could slip, slide _and_ stretch. > > A motion estimator is related to a motion tracker. They could > probably work together in interesting ways.
Personally, I'm quite happy to re-time video segments outside of Cin, then just import them into Cin. In fact, I've written a python front-end which gives a simple interface and takes care of all the details, so it can take a clip in any format at any fps, and convert it to a high-quality .mov/mpeg4 with the desired fps. Motion estimation is CPU intensive, far more so than even camera/projector zooms. It's questionable whether this belongs in Cin at all - whether on the Cin timeline or as a Cin effect. You'd never in your wildest dreams be able to re-time and play in realtime in the Cin viewer or compositor. Cheers David _______________________________________________ Cinelerra mailing list [email protected] https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
