Transmageddon and WebM

So after a long hiatus I finally managed to push out a new Transmageddon release, 0.16. In addition to a lot of new translations (big thanks to all members of the GNOME translation team) there are a few bugfixes in there, but most importantly this release adds support for the new WebM format, enabling you to quickly and easily make such files. Thanks to the work Sebastian and David did this was very easy for me.

Mandatory screenshot:

Transmageddon encoding a WebM file

Transmageddon encoding a WebM file

To make this work however you will need a lot of bleeding edge software, including todays git master of gst-plugins-good and gst-plugins-bad and libvpx installed (libvpx adds VP8 support).

This release also lets you put the On VP8 codec into other container formats, such as Ogg, Quicktime and AVI.

For Fedora users I recommend grabbing the latest libvpx SRPM created by Tom "spot" Callaway from Red Hat bugzilla. It should work perfectly with the GStreamer configure scripts.

For Ubuntu users I recommend the GStreamer PPA repository for getting latest libvpx. You probably need a newer gst-plugins-good than you find there right now though, but hopefully we will get that PPA updated today.

I also think libvpx has been packaged into Debian.

Totem playing WebM file

Totem playing WebM file

So I think that with this release Transmageddon is the first free software encoding GUI tool supporting the WebM format. At minimum the first I care about ;)

You can download Transmageddon 0.16 from the usual location on the Transmageddon homepage.

Note: Some long standing bugs, like trouble identifying some input files and no deinterlacing support, are still not fixed. I am waiting for Gst-conveniece to be ready with Python bindings, in order to fix those two bugs.


#1 Danny Piccirillo on 05.21.10 at 07:51

Final Fantasy IX!!!!! Nice xD

#2 Edward Hervey on 05.22.10 at 07:46

Yes, Christian, I know, I need to finish those damn bindings :( Kuddos on Transmaggedon work though :)

#3 Dan Dennedy on 05.27.10 at 17:15

Good work on supporting WebM, but I do wonder why one would put VP8 into Ogg, AVI, or MOV? We have a chance to simplify and standardize on a format that we hope will become popular. This will be convenient and less stressful for all. Are we multimedia software developers that make user interfaces doing a dis-service by providing flexibility and thereby introducing the (easy) potential for someone to output in these non-standard (WebM) formats?