>> * Should we include "in" and "out" point properties for all services? Right >> now it is inconsistent (some include it, some don't). I expect that all >> services have in/out point properties (except possibly device based >> producers and consumers). >> > >Ya know, I have been wondering the same myself. These properties are >generic and already documented with Doxygen. I would really appreciate >a cleanup patch that removes from all existing yml: in, out, length, >resource, and aspect_ratio.
I committed a change here: g...@github.com:pez4brian/mlt.git as 44c52a3c2f2f62b43fcd Here is a link: https://github.com/pez4brian/mlt/commit/44c52a3c2f2f62b43fcdb9017a701ba7a4e692e5 Feel free to pull it at your convenience. ~Brian ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
