Skip navigation.

New releases of GStreamer and GStreamer-plugins

GStreamer
GStreamer

As many of you know Fluendo is paying Ronald Bultje to work fulltime on fixing GStreamer playback issues at the moment. The goal is to make Totem and GStreamer the best video player for Linux and Unix. Ronald have been fixing tons of bugs and Wim Taymans have also chipped in to fix a lot of playback bugs. These two releases, of GStreamer core and GStreamer plugins, contains all the bugfixes so far. Ronald will continue working on improving playback but we hope the community will help us by testing these releases and providing bugzilla reports with files attached of files still giving you issues. Of course patches never hurt either :)So check out the release notes and grab the tarballs and start testing.

Download instructions and release notes for GStreamer 0.8.7

Download instructions and release notes for GStreamer-plugins 0.8.5.

You need latest Totem version 0.99.17 to test as this contains some extremely important updates to its GStreamer backend.

With the fixes in this release and those who come as a result of testing done by the community based on these releases, the goal is to switch Totem over to using GStreamer as its default backend for one of its future releases.

P.S. For testing non-free formats you need a new release of gstreamer-ffmpeg package. This will be released on thursday (tommorow).

Re: New releases of GStreamer and GStreamer-plugins

No menubar or controls - but I don't need them or want them, I only want the video. Using the keyboard to navigate (space = pause, q = quit, f = fullscreen, arrow keys = fast forward/backwards) is much faster than using the mouse.

Well, I for one want them. How am I supposed to remember how to do anything if I have to type keys at an empty window, and every program is different? Is Quit ctrl-W or ctrl-Q in this app? Is fullscreen-mode F11, or alt-enter, or ctrl-F? (Surprise, none of the above!)

Using the keyboard is faster if you spend 8 hours a day using a program so you build up your muscle memory -- this is why Emacs geeks love Emacs, and why Final Cut Pro geeks buy FCP-specific keyboards. For the occasional use, it's not. Pressing 'f' is not faster than choosing View->Fullscreen, if I have to try 3 or 4 different key combinations before I guess which one this app uses. (Especially if one of the key combos I try has a different meaning in this program, so I have to undo it before I can try another one.)

(HIBT?)