On Sat, Jun 6, 2015 at 1:56 PM jb <j...@kdenlive.org> wrote:
> On Saturday 06 June 2015 20.22:27 Dan Dennedy wrote: > > Most animation things are done through the Properties API, and just as > > there is no Mlt::Property in C++ maybe same thing goes for animation. > > However, a quick analysis reveals a few things an app might want to do > not > > yet available through Properties. Maybe, it is better to expose these > > through properties: > > mlt_properties_anim_is_keyframe > > mlt_properties_anim_keyframe_type > > mlt_properties_anim_length > > mlt_properties_anim_remove > > mlt_properties_anim_next > > mlt_properties_anim_previous > > Properties::anim_is_keyframe > > Properties::anim_keyframe_type > > Properties::anim_length > > Properties::anim_remove > > Properties::anim_next > > Properties::anim_previous > > > > All of the above can just use simple, scalar types for parameters instead > > of making apps deal with new Animation and AnimationItem objects, > managing > > them, and properly interfacing them with properties. Next and previous > > would take and return a position. > > Thanks for the quick reply. > The first proposal seems easier on the app side, but will add some slight > overhead I think, because for each request / change to the animation we > must > search for the animated property through: > mlt_properties_find( self, name ); > > So it seems to me that the Mlt::Animation* would be slightly better, but > might > require slightly more work on the MLT side... > > Anyways, any of these solutions would be perfect for what we want to > achieve, > so if you have a preference, I am fine with it. > > Once a solution is decided, do you need help to implement it ? > > I will work on it this week, and then integrate it into Shotcut to verify it works sufficiently.
------------------------------------------------------------------------------
_______________________________________________ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
