Further progress on multistream Transmageddon

As mentioned in my previous blog entry I am working on multistream handling in Transmageddon. Not been a lot of changes, but I have been able to put in a little time here and there. The changes needed to accommodate this have also cleaned up the codebase quite a bit in my opinion, moving from a forest of variables to a list of python dictionaries. This change makes keeping track of whats happening in the codepath a lot easier as I can now just print the dictionary from the list to see what all relevant values are at a given point. Anyway a little screenshot below to show where I am at:

In-progress support for multiple audio streams.

Still quite a bit of work to do to clean up the codebase and decide how certain things are to be handled (or not handled), but it is getting there. Screenshot above actually demonstrates one thing I haven’t decided on yet, which is how to deal with combining a device preset with a multistream file.

The biggest blocker currently for finishing this work is that the GStreamer encodebin element does not have an API yet for dealing with selecting encoding settings for multiple streams as detailed in this bug report. If anyone got the inclination to cook up a patch for encodebin which adds support for this that would be much appreciated.

Anyway, once I have this completed I think my next step will be to try to add some kind of DVD ripping support to Transmageddon and some basic metadata checking/editing and move the video flipping support into a special menu and add support for enabling/disabling deinterlacing in that same special menu. I trying to figure out as I go along how I can keep the user interface simple and straightforward and add requested features. The question that I continuously ask myself is what features do belong in Transmageddon and what features are of a level where people should go to something like PiTiVi instead.

3 thoughts on “Further progress on multistream Transmageddon”

  1. Work on this is much required! Thank you so much. Maybe an URI would be gread for Input selection (e.g. gnomevfssrc can handle a lot). When introducing Multistream I think that adding multiple inputs would not be far away. So that we don’t depend on mkvmerge GUI anymore for proper muxing.
    Lately I was searching for a GStreamer-based tool which could handle a simple VIDEO_TS folder… but found none till now. Also dvdreadsrc seems to be working only with DVD-device/ISO.

    1. Kai, both dvdreadsrc and the DVD menu navigation plugin should be able to handle to handle VIDEO_TS folders just fine, e.g.:

      gst-launch-1.0 playbin uri=dvd:///path/to/VIDEO_TS/

      works fine for me with the resindvd plugin, and so does totem /path/to/VIDEO_TS/

      (going slightly offtopic, sorry)

  2. Keep up the great work, can’t wait to have Fedora 18 installed in my machine and using this very helpful application. I certainly can’t wait to have DVD ripping functionality implemented, the prospect of being able to rip my favorite DVD and then converting it to play on my PSP or Android phone is very enticing. Keep up the good work. :)

Comments are closed.