This latest big commit was the merging of my "autoprofile" branch:
- Profile information is serialized and deserialized to/from XML. It
includes support for Kdenlive's "profileinfo" in addition to its own
"profile" element. For convenience with authoring/generating XML, one
can add profile="name" to the root mlt element.
- If a profile is not supplied to melt, then it will try to build one
dynamically from the file's media attributes (or deserialized
property).
- If you supply a profile, but load a MLT XML with conflicting profile
information, then the loader will automatically insert the consumer
producer to take care of aspect ratio and resolution differences. The
only thing an application needs to do to take advantage of this is to
set the profile explicit after creating it:
Index: src/renderer.cpp
===================================================================
--- src/renderer.cpp (revision 4974)
+++ src/renderer.cpp (working copy)
@@ -182,6 +182,7 @@
//TODO: uncomment following line when everything is clean
//if (m_mltProfile) delete m_mltProfile;
m_mltProfile = new Mlt::Profile(tmp);
+ m_mltProfile->get_profile()->is_explicit = 1;
delete[] tmp;
QString videoDriver = KdenliveSettings::videodrivername();
--
+-DRD-+
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Mlt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mlt-devel
