When a MLT property is serialized, if there is a string representation, then it is used: *https://github.com/mltframework/mlt/blob/master/src/framework/mlt_property.c#L675 <https://github.com/mltframework/mlt/blob/master/src/framework/mlt_property.c#L675>*
Therefore, when the property is set by string, as long as nothing changes it, it will serialize as then input string. Some property operations clear this string (such as any non-anim mlt_properties_set*) or rebuild it including mlt_properties_anim_get() (animated string): https://github.com/mltframework/mlt/blob/master/src/framework/mlt_property.c#L1286 Details are fuzzy for me right now, but it looks like if you manipulate an animation, you need to explicitly serialize it back to a property. Also, negative time values are not fully managed and do not serialize back as a negative value. On Thu, Sep 29, 2016 at 10:08 AM Harald Albrecht <harald.albre...@gmx.net> wrote: > Hi, > > as far as I understand, the textual representation of animated > properties allows to specify the position of a keyframe as negative, > that is, relative to the end of the effect or transition. > > I've also seen that MLT, when encounting such a negative keyframe, it > adds the length of the transition/effect to it, so it's now an absolute > positive frame position. > > Now, when I serialize such an MLT network, what will end up in the XML > output? The original animation string? Or are all negative keyframes lost? > > Best regards, > Harald > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Mlt-devel mailing list > Mlt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mlt-devel >
------------------------------------------------------------------------------
_______________________________________________ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
