On Sun, Aug 15, 2021 at 1:02 PM amindfv--- via Mlt-devel <
mlt-devel@lists.sourceforge.net> wrote:

> More recent versions of Kdenlive are putting properties in entries. For
> example:
>
>     <entry producer="producer1" in="00:00:00.000" out="00:05:12.804">
>      <property name="kdenlive:id">2</property>
>     </entry>
>
>
> and:
>
>     <entry producer="producer3" in="00:05:12.846" out="01:34:03.420">
>      <property name="kdenlive:id">2</property>
>      <property name="kdenlive:activeeffect">1</property>
>      <filter id="filter6">
>      ...
>
> This technically isn't part of the spec (at least according to
> src/modules/xml/mlt-xml.dtd). Would there be any downside to changing the
> MLT XML DTD from...:
>
>     <!ELEMENT entry (producer | playlist | tractor | multitrack | filter |
> transition | chain)* >
>
> ...to:
>
>     <!ELEMENT entry (property*,(producer | playlist | tractor | multitrack
> | filter | transition | chain)*) >
>
>
>
I do not see any downside, but I have not tested that property as a child
of entry works. Assuming it works because it is working in a
Kdenlve release (and not simply a bug in development code), please go ahead
and submit a pull request. Thanks
_______________________________________________
Mlt-devel mailing list
Mlt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlt-devel

Reply via email to