Dan,
>> A couple of questions: >> * 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'll take care of it. And I'll exclude them from new yml. >> * Would you consider renaming " > /src/modules/gtk2/filter_rescale.c" to "filter_gtkrescale.c"? > Then it would match the name it is registered with in gtk2/factory.c. That > way, > when I create filter_gtkrescale.yml, the name will match the file it applies > to. > I can supply a patch if you want. >> > > I have kind of been intentionally avoiding metadata for normalization > filters since they are not intended to be used directly. See > src/modules/core/loader.ini for the list of normalization filters. > These get applied to each producer automatically. However, there are > some exceptions like crop that are used in two ways: one as the image > processor and another to simply apply properties (as an alternative to > using, e.g., set.crop.top on the producer). No problem. I'll skip normalization filters for now. Just be aware that some documentation may be "lost" when you finally eliminate services.txt if we don't move the documentation for those filters somewhere. Other than gtkrescale, I don't know how many normalization filters are documented in services.txt - it may be the only one. >> * Is there a release imminent that it would be worth getting these all done > before? If so, what's the deadline? > > Yes, there is. I want to make a release this Sunday. But don't sweat > it. There are no applications really dependent upon this at the moment > for its functionality. Ok. I definitely won't be done by Sunday. I'll let you know when my next patch is ready. ~BM ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
