openshot.developers team mailing list archive
-
openshot.developers team
-
Mailing list archive
-
Message #02507
[Bug 507284] Re: command-line interface
ok, now I'm rather sure that it is a MLT bug in parsing xml files:
If content of a property tag goes to a new line (as it is produced by xml.dom.minidom), melt segfaults, though it is perfectly valid XML.
I include two sample files, containing same XML, both valid, but one works with MLT, the other does not.
** Attachment added: "xml_test.zip"
http://launchpadlibrarian.net/39451115/xml_test.zip
--
command-line interface
https://bugs.launchpad.net/bugs/507284
You received this bug notification because you are a member of OpenShot
Developers, which is subscribed to OpenShot Video Editor.
Status in OpenShot Video Editor: Fix Committed
Bug description:
I've coded a command-line openshot renderer.
It takes an osp openshot project file as input and renders it according to options given in command.
(it defaults to mpeg4 avi video, 5 Mb/s, with libmp3lame as audio codec, 2 channels, 48000 as sample-rate and 128 kb/s as audio bitrate)
if no output file name or folder is given as option, then user openshot dir is used, and the default output file is called temp.
The command-line version can be very useful for batch-rendering of large or multiple project files, as it can be used in a bash script, or used in a remote server with no graphical interface.
The command-line part is self-contained, as it doesn't alter any existing openshot source files, and it doens't load any gtk.
An ascii progressbar is displayed to console while rendering, showing completed percentage.
I've tested it with several project files, and seems to work.
the branch is:
lp:~francesco-hermanitosverdes/openshot/hv_francesco
References