Win32 codec for fedora

Provided by RealNetworks, Inc. MPlayer will play older and new Real formats and media if you have the codecs properly set up below. RealPlayer 10 will play all newer Real media including It should work on Fedora however I do not know about older RH releases.

Instructions to install RealPlayer While the older instructions for RealPlayer 8. Latest Release: Current Version: 1. Obtain the following files for installation. Please use an appropriate mirror location to download the files.

You need the MPlayer source and some additional codecs. You should have at least one skin. These additional codecs are to read formats that do not have an Open Source decoder available.

The binary codecs come in 2 packages: all and essential. Some codecs were previously only supported using binary, however many are now natively supported by MPlayer native support is typically faster. The essential package is recommended, however using the all package should not cause any problems. Applications like Xine use that directory for the same purpose. If you would like you can either keep both directories or make one linked to the other.

If both directories exist you cannot link them. Note: bit Users: Win32 codec DLLs are not supported and there may be a warning similar to the following:. MPlayer follows standard Linux application procedure of installing dependencies, configuring, compiling and installing. The above steps were to eliminate most common dependency problems. Most users will find the default configuration options adequate.

However I recommend the following options. The first option is required to install the GUI. The second option is to allow access to large files over 2GB. The last 2 options are to better match other MPlayer installations. With version 1. The GUI requires both gtk2 and glib2 installed as well as their devel libraries. Make sure you have the following RPMs or newer : gtk The old GUI is still usable if you run configure with: --enable-old-gtk not recommended. Once the configure script has been run a great deal of output is displayed on the console.

The following is a sample output from the end of the configure on my machine. Your output can and will differ based on what additional hardware or software you have installed. This step is optional.

If everything worked correctly the first time you configured then continue to compiling. However there is a chance you do not have something correctly installed on your computer. During configure there are tests done to check which software is already installed. Read over it carefully to see if there are any mistakes or if some library is not detected. For example : if the Lame libraries were detected, you would see:.

Not all the codecs should be detected. In fact most will not. However the many that you have should be an adequate starting point for using MPlayer to decode and encode.

Once carefully completing the configure step, you can compile MPlayer. This step usually takes the longest. If there is an error at this point you may have used an improper library or version of a dependency. Try to determine at which file the compile fails and post to help forums, newsgroups or mailing lists for assistance. Reading MPlayer documentions usually helps.

Sometimes trying a different library version helps. Another solution maybe to entirely disable that plugin. If you need to fix something, you will have to re-do the Configure step from above.

Otherwise continue:. MPlayer will be installed and the last few lines of output indicate where we should install the skins:. You should set this up regardless of whether or not you use the GUI. In FC5 and newer: xorg-xfonts-truetype. You need msttcorefonts package for the last option below. You must select this option at the 'Configure' step explained above.

Go to the MPlayer homepage and examine some screen shots to find one you like. I recommend: Blue , plastik and proton. To install a skin decompress it and copy or move it into the skins directory.

You can have as many as you like, but one must be default. Note: Prior to version 1. This should also work. Please look at the MPlayer skins page for the latest versions. To uninstall any other components listed above, the similar procedure works.

Change to you source directory where you installed MPlayer and run ' make uninstall '. If you did not install from source files and used binary rpms, you can use the rpm command or the Redhat Package Manager to uninstall rpms. Run ' man rpm ' for more help, look at the ' -e ' flag.

If you created a directory that no other program uses, you can also delete it. Note: Use caution when uninstalling and deleting, you can do serious damage to your system when you are root.

You may either upgrade dependencies or upgrade MPlayer itself. Both can potentially break some functionality of MPlayer. To upgrade a dependency repeat the steps listed above. Of course avoid upgrading a dependency unless completely necessary. By doing so you may break compatibility with other programs.

If everything works there is no need to upgrade unless either 1. This guide lists the latest dependencies and releases so as to stay up to date. In most cases using previous versions of software will work. Any exceptions are noted. MPlayer can be run by command line using mplayer or gui using gmplayer.

You should use your movie file or music file in the line. I strongly recommend you look there for help first. Comments, suggestions, questions or any feedback welcome for this page or any of my Resources.

Please use the contact link. Help Out: If you found this guide or any Resource helpful, please consider supporting this site by recommending this page to others or linking to this page.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. The Windows Media Audio and Video codecs are a collection of objects that you can use to compress and decompress digital media data.

Each codec consists of two objects, an encoder and a decoder. This part of the documentation describes how to use the features of the Windows Media Audio and Video codecs to produce and consume compressed data streams. The term codec is an amalgamation of the terms compressor and decompressor.

A codec is usually implemented as a pair of COM objects: one for encoding content, and another for decoding content. Not only are there different codecs for audio and for video, but also different codecs for different kinds of content that you might want to put into an audio or video file. The algorithms used to compress and decompress data for spoken words differ from the algorithms used to compress and decompress music data.

This documentation does not cover these legacy codecs; it covers only the current versions of codecs. For older codecs, use the same procedures as when using the current codecs; however, remember that not all features are supported in all codecs. Media Foundation Programming Guide. Media Technologies for Windows. Skip to main content.