On Fri, Oct 19, 2012 at 2:46 PM, j-b-m <[email protected]> wrote: > > Hi, > > Following a feature request in Kdenlive (1), I tried to make a few changes > to > the motion_est filter to allow the detection of scene changes in a clip. > > I made 2 changes to the filter: > > 1 - add a geometry property "bounding" allowing to process filter on a > part of the image only to speed up processing >
ok > 2 - Store the scene changes frame positions in a "_scene_cut" property > that can later be retrieved by the application Why hide the property with the leading underscore? If it is not hidden, the someone using melt can use this to serialize the result to XML for processing the results. Also, the name should perhaps be a bit more consistent with the existing "shot_change" Also, for the value, it looks like you are you are making a list of frame numbers using a colon delimiter. Hmm.. there might be a case to get these as time values (i.e. clock or timecode) in the future. Also, there might be a case for making the list format more consistent with geometry keyframing where semi-colon is the delimiter. You could then use mlt_geometry to construct this value instead of this ad hoc code. An app could use mlt_geometry to parse it as well. Then, when mlt_geometry is refactored into mlt_properties and a new mlt_rect type, it will gain support for time values. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Mlt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mlt-devel
