Hello! About effects and transitions:
Effect and translations are written in the mlt framework. Kdenlive is "only" a gui for mlt framework. So, i have some ideas: 1, In the mlt framework as i see every effect is linked together, so, they are not dinamic. The problem with this approach is that if i write a new effect, it is only available after mlt recompile. It is not a very good thing. 2, Another problem is, after i created that damn effect, kdenlive has to be extended, too, and recompiled. So, if somebody adds a new effect, both the mlt AND the kdenlive source has to be recompiled. It is a major problem, because users (who can write code) are not able to write their own effects, and share with the others. What i propose: - Modify the mlt framework that it can use effects and transitions in .so format. - Create an xml schema that can describe an effect (and one for a transition). It should contain a link to the so file, the parameters, the function names bound to the parameters, and so on. - Every effect should be downloadable in a zip format. (with so, with the xml, perhaps with additional files). In kdenlive there should be a menu item: add new effect (transition) If the user downloads his neweffect.zip, he will select the neweffect.zip using the menu item, then kdenlive will install it. Perhaps a restart is necessary. Kdenlive will build up the corresponding gui to the effect using the xml file. What do you think? Regards: Zsolti
