Totem is the official movie player of the GNOME
desktop environment based on xine-lib or
GStreamer. It features a
playlist, a full-screen mode, seek and volume controls, as well as keyboard
navigation.
It comes with added functionality such as:
If you are running a recent distribution, there is a high chance totem is already installed since it is the default movie player of the GNOME desktop environment. If this isn't the case, you can install it by using a online repository (if available for your distribution). You can choose between totem-gstreamer and totem-xine.
For deb-based distributions (like Debian, Ubuntu, …) this is:
For yum-based distributions (like Fedora Core, …) this is:
For portage-based distributions (like gentoo linux, …) this is:
Use the -xine USE flag to install the GStreamer version.
The way mentioned above is the preferred way, since your package manger will handle future updates of totem. You can however still install totem from a binary package file. These packages are created for a specific distribution. If you can't find a package for your distribution, you can try your luck on a package for a distribution that is related to yours, or you can compile totem from source (see "Installing from source").
You can also compile totem for source. The latest sourcecode of totem can be found at the GNOME ftp site.
If you want to play with the latest bleeding-edge features, you can try an SVN copy. Note that SVN versions can be unstable! Check out the documentation on how to do this. The module you have to check out is totem.
Totem can display a variety of formats, based on what backend you use. To see what backend you are using check the "About" dialog of Totem.
When using the GStreamer backend, you can install multiple plugin packages. You can install them the same way as you would install totem. Some information about the gstreamer-plugins packages can be found here.
Everything's included in this version, apart from some proprietary codecs that require Windows DLLs. Check the FAQ on xine-lib's website. That should sort most of you out.
Using Totem, you can watch TV on over-the-air and satellite digital television. You'll need a DVB-T or DVB-S card supported by Linux, and a channels.conf file containing the channel tuning information.
You will need gst-plugins-bad 0.10.6, as well as Fluendo's MPEG demuxer to have playback working. The channels.conf file should be named ~/.gstreamer-0.10/dvb-channels.conf.
The channels.conf file should be placed in ~/.xine/.
Work is on-going to have a scanner interface in Totem, so that the out-of-the-box experience is better, but you will have to use another application to generate the channels listing.
We recommend you use w_scan as it doesn't require any initial scanning data to scan for channels.
With the YouTube plugin you can browse YouTube and watch videos from it. You'll need gstreamer-plugins-bad 0.10.6 or a recent version of xine-lib. Even if videos play correctly, seeking may not yet work for them but work is ongoing to fix this.
Q: Why does seeking with the keyboard keys (Left and Right arrow) in Totem not seek the same amount of time in either direction?
A: This is on purpose. To find a particular point in a film, most people will seek forward and then realise that they've gone too far. Seeking back, if it used the same amount of time, would mean going back to where they last seeked from. You can experiment with pressing Ctrl or Shift along with the arrows to seek further, or closer (respectively).
Q: Why doesn't the space bar work to play/pause in windowed mode? It only works in fullscreen, and sometimes in windowed mode.
A: The space bar will work in fullscreen. But when in windowed mode, for accessibility reasons, we cannot use the space to play/pause (it is used to "push" buttons already). It will work sometimes, as the play/pause button, or the video widget might be the one with the keyboard focus. Try using "P" to play/pause instead.
Q: Why does the browser plugin advertise itself as handling some file/stream types it can't handle? (e.g. why does it say it supports MP3 in the about:plugins when it doesn't?)
A: The problem is that the Mozilla/Gecko/Firefox plugin system doesn't allow for fine-grained advertising of those features.
For example, the Totem GMP plugin advertises itself as a Windows Media Player compatible-plugin. There is unfortunately no way to check whether all the necessary plugins are available to the media framework to play the stream before we try. For example, the installed plugins might only be able to play back a specific version of Windows Media Video. There is no way to advertise that fact using the current plugin system. There is also no way to know what will be inside the stream before we start playing it back.
Before you want to file a bug, make sure you are running the latest version. After that, you must find out if the bug is caused by totem or by its backend (GStreamer or xine). If it is something visual in the video or something in the audio, it probably is a bug in the backend and has to be submitted to the right bugtracker. To see what backend you are using check the "About box" of totem.
If you are running the GStreamer backend, and you notice a problem with the sound or video (out of sync, garbled output, …), you can file a bug to GStreamer. As with all bugs, first check if it isn't already reported. If your bug isn't in that list, file new bug. You might want to include the output of this command to your bug report:
or if the problem seems to be with the file you're playing, include the output of:
First, check if your bug also happens in xine-ui, if this is the case, it is likely a bug in Xine. Check the bug section on the Xine homepage. When a crash occurs in xine-lib itself, please recompile xine-lib with debugging information (run make debug followed by make debug-install after having run the configure script) and provide a backtrace. You will also want to check the xine FAQ.
If you are convinced the problem is with Totem itself, you should first check the bug list if your
bug isn't already reported. If you can't find your bug, go ahead and file it on the
the totem bugtracker.
To have better debug-output, open a terminal and enter the following command.
Here you can find a collection of usefull links related to totem.
The nice sponsors: