v0.8.2 released
Aug 28, 2012
This is a bugfix and minor enhancement release.
- Overhaul of A/V sync with libavformat-based inputs.
- Fix a major memory leak introduced in previous release.
- Fixes to problems revealed by Coverity Scan static analysis.
- Improved encoding presets.
- melt can now be built without SDL with define MELT_NOSDL, which is handy
for running it as a child process on Windows and OS X.
- melt can now be signaled to quit, which also makes it more useful as a
child process.
Special thanks to Mikko Rapeli who provided many of the Coverity fixes.
Shotcut now available!
Jun 26, 2012
Shotcut is a new application from the lead developer of MLT. It will eventually become a full video editor, but currently it is just a media player. The emphasis of the work thus far has been to develop a solid foundation - both code and project - upon which to build and iterate. To learn more, head on over to its
website.
v0.8.0 released
Jun 1, 2012
The minor version is increased due to the addition of time properties! The soname version increased in the process because some mlt_property functions changed; however, very few if any apps actually directly use mlt_property preferring to use mlt_properties instead. In addition:
- improve seek speed on AVCHD when using FFmpeg v0.9.1+ (sorry, not Libav!)
- composite and dissolve speed improvements on x86-64
- improve performance of caching in image producers
- add device enumeration to decklink producer and consumer
Announcing Flowblade Movie Editor
Jun 1, 2012
Janne Liljeblad recently announced the availability of
Flowblade - a new video editor using MLT that he has quietly been working on since 2009!
It is written in Python and GTK+ and is released under the GPLv3 license. Flowblade employs a "film style" or "insert editing" paradigm, maybe best known from Avid products. Therefore, its UI and workflow is quite a bit different than OpenShot.
You can see a screencast video of it in action on Vimeo:
http://vimeo.com/40929683
server reorganization
Apr 25, 2012
The MLT web/wiki and git server has moved out of the garage and into the cloud to offer better uptime, responsiveness, and collaboration. Turnkey Linux has a TWiki appliance, so we moved the web site to its hub service, which provides cloud-computing for its appliance images. This greatly simplifies management partly because it has many things related to security and backup already setup.
Then, we had to decide what to do about the git daemon and gitweb service - whether to migrate that to the hub instance as well or whether to use a popular git hosting service. GitHub has really become a great collaboration service with code reviewing, pull requests, and issue tracking, giving it an edge over others. Not to mention, so many developers are already registered and ready to fork. So, effective immediately the authoritative git repositories are now at
https://github.com/mltframework/.
Not done yet. A new contributor has setup an automated build server that uses the
build scripts, which are now being maintained in git instead of the wiki. The build server is primarily for quality assurance purposes at this point, but there are plans to offer nightly builds of popular MLT applications from this service. We have a little more work to expose that properly.
