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.
Everyone uses cinelerra for different things obviously.
Personally my use for this tool would be in (stopmotion) animation
work. I anticipate retiming and smoothing segments of the animation.
This sort of work would require a gui and a compositor and as much
integration as possible.
Speed is not such an issue for me - many of Cinelerras effects are a
long way from real time. That's what the background renderer is for. I
use it all the time. I have a second networked computer running
cinelerra to make it more effective.
If this approach was as effective in reality as in my fantasies I might
even decide to change the way I animate. You could leave out setting up
and photographing simple intermediate frames when you think the
interpolator might do a good job.
I wonder if there would be any possibilty of this working smoothly or
whether it would make the animation 'shimmer' as the yuvmotionfps engine
cuts in and out... That would require some testing. At the very least
this approach could be used to fix mistakes in the animation (eg chop
out a frame where your hand is in shot and then interpolate it back in)...
and then after editing a whole scene I might increase the framerate
across the board from say 12fps to 24fps.
Graham
_______________________________________________
Cinelerra mailing list
[email protected]
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
