DTD for Kdenlive

alcinos french.ebook.lover at gmail.com
Sat May 26 23:04:14 UTC 2018

Well, the kdenlive's xml is being parsed by mlt at the core. So all the
structure must be MLT compliant enough for the parsing to be successful :)
Basically, kdenlive stores a lot of additional properties (usually prefixed
by "kdenlive"), that are parsed and ignored by MLT.
Besides, kdenlive abuses a bit the mlt structures to perform some "tricks":
for example, we need to have a fake timeline to store the bin clips,
otherwise the bin clips that are not used in the project wouldn't be saved.
What this means is that even though the file should be "valid" in the sense
that MLT knows how to parse it, there is a high probability that MLT is not
going to playback the project directly.

Hope this helps,

2018-05-26 20:15 GMT+02:00 Camille <camille.moulin at free.fr>:

> Le 24/05/2018 à 14:36, Narcis Garcia a écrit :
>> I think it's a good initiative.
> Thanks :-)
> There  is still a basic point that I haven't fully grasped yet: what
> is/should be the relation between kdenlive's xml format and MLT's xml
> format?
> Does it makes sense for Kdenlive  to have it's own dtd, or should
> kdenlive's files be conformant to MLT's DTD ? (which could mean either
> modify the app or ask for modifications of the DTD upstream)?
> Cheers,
> Camille
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdenlive/attachments/20180527/894badc2/attachment.html>

More information about the kdenlive mailing list