https://bugs.kde.org/show_bug.cgi?id=411260
--- Comment #8 from Jonathan Gilbert <c6kargn...@liamekaens.com> --- I actually have a further update. It seems this is more properly a bug in MLT, because the XML standard says that attribute order should not be a semantic difference -- that's why Qt 5 feels it is okay to start using a hash for them -- and MLT is violating that by processing files differently for different attribute orders. Kdenlive may not need to make a change because MLT is going to make a change to eliminate the dependency on attribute order simply by first explicitly searching for and processing "properties" and then processing everything else. I don't know when that'll happen or what the release cadence is, but it may be sufficient simply to wait for the next MLT version and build the next Kdenlive release against that. If MLT might not get updated quickly enough then switching to an XML approach that is deterministic in its attribute order may still make sense, but there is a chance it might not be necessary. -- You are receiving this mail because: You are watching all bug changes.
