xmms bmp audacious

Audacious is a -based for systems, such as .

Audacious
Audacious Media Player with default skin

It is a fork of 0.9.7.1, which is a fork of . William "nenolod" Pitcock decided to fork Beep Media Player after the original development team announced that they were stopping development, in order to create a next-generation version, .

The reasons for the fork were purely technical. There were some quirks in Beep Media Player that had annoyed users, such as the handling, which had been reported as by some users. The developers also had their own ideas about how a player should be designed, which they wanted to try in a production environment. Besides, Beep Media Player allegedly lacked functionalities that were considered useful for people who did , such as support for an -like "songchange plugin".

XMMS "successor" controversy

Many distributions have replaced with Audacious. This has resulted in many people claiming that Audacious is the successor to XMMS, and that it's featureset should be similar. Many developers involved in the project have found the demands from this particular segment of the user community to be ridiculous, and have commented on the fact that Audacious was never meant to be a successor to .

The reason why many distributions have replaced with Audacious is because of the similar UI design. This has lead to the decision to drop Winamp2 skin support in the 2.x branch of Audacious (but there's a plugin planned to enable use of the skins if wanted). A simpler player based on Audacious and GStreamer is intended to satisfy the demand created for another XMMS-like player.

Features

Plugins

Audacious owes a large portion of its features to , including all . On most systems, a useful set of plugins is installed by default. This includes, for instance, the ability to play , and files.

Current versions of the Audacious core classify plugins as follows (some are low level and not user-visible at this time):

• Decoder plugins, which contain the actual codecs used for decoding content.
• Transport plugins, which are lowlevel and implemented by the VFS layer.
• General plugins, which provide user-added services to the player (such as sending tracks with )
• Output plugins, which provide the audio system backend of the player.
• Visualization plugins, which provide visualizations based on of the wave data.
• Effect plugins, which provide various sound processing on the decoded audio stream
• Container plugins, which provide support for playlists and other similar structures.
• Lowlevel plugins, which provide miscellaneous services to the player core and are not categorized into any of the other plugins.

Skins

Audacious had full support for 2 skins, and as of version 1.2, some free-form skinning is possible.

Audacious 2.x will have a non-skinned UI which will better emphasize on many of the player's features which are poorly exposed in the UI.

Clients

Audacious is intended to be a media player and not a client (), though it supports the concept of other clients connecting to it, such as .

Connection to audacious for remote control can be done over plain , by using MPRIS, or using the official audtool utility created just for this purpose.