DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
GStreamer is a streaming media framework, based on graphs of filters
which operate on media data. Applications using this library can do
anything from real-time sound processing to playing videos, and just
about anything else media-related. Its plugin-based architecture means
that new data types or processing capabilities can be added simply by
installing new plug-ins.
gstreamer is a multimedia encoding and decoding framework. You generally don't use it directly (though there are tools available for that), it's mostly used as the backend for various media players such as totem. It has a plug-in based system for adding support for various codecs. It even has an ffmpeg plugin to provide you with libav support.
It's not absolutely necessary to have it, unless the player you want to use depends on it. If you have mplayer/mencoder, ffmpeg, and lame, you pretty much have everything you need for most media work. But you may find that certain media play better on one framework than another, or even only on one of them (usually the one you don't have installed ), so it's perfectly reasonable to have a variety of players and backends available. I personally have just about everything installed; mplayer, ffmpeg, xine, gstreamer, and vlc, along with several frontends and related tools. If something is playable at all on Linux, I'm probably going to be able to play it.
Last edited by David the H.; 05-02-2009 at 08:56 AM.
It's not absolutely necessary to have it, unless the player you want to use depends on it........... I personally have just about everything installed; mplayer, ffmpeg, xine, gstreamer, and vlc, along with several frontends and related tools. If something is playable at all on Linux, I'm probably going to be able to play it.
I use players like vlc and smplayer, so any idea what is the "default" packages that they depend on ?
IMO, it does not matter whether it is Totem or another. They are just front-end for GStreamer like what people said above.
What you need is plugins such as gst-plugins-bad, gst-plugins-ugly and gst-ffmpeg along with gst-plugins-good. Whether your media are playable depend on those plugins installed.
I use players like vlc and smplayer, so any idea what is the "default" packages that they depend on ?
You have to research individual programs to discover what systems they support or are based on. One good way to learn is to watch the dependency packages they want to install. If you see a lot of "gst" dependencies, for example, then you can be pretty sure it's based on gstreamer. And smplayer is obviously based on mplayer just from the name. A few players like totem can use multiple backends.
AIUI, mplayer, xine, and gstreamer are the three big frameworks that you'll see most frontends based around. vlc is kind of an independent project. But in fact, most of these frameworks are built around many of the same tools, having plugins for calling on each other or dependencies on external codecs and libraries such as faad (for aac decoding). Almost all of them depend on or can use libavformat/libavcodec, for example.
Wikipedia is a good source of information about all these tools.
AIUI, mplayer, xine, and gstreamer are the three big frameworks that you'll see most frontends based around. vlc is kind of an independent project. But in fact, most of these frameworks are built around many of the same tools, having plugins for calling on each other or dependencies on external codecs and libraries such as faad (for aac decoding). Almost all of them depend on or can use libavformat/libavcodec, for example.
Wikipedia is a good source of information about all these tools.
THANKS for the info.
Believe it or not , the section quoted above actually clears some confusion that I have.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.