Audacious Media Player
From Wikipedia, the free encyclopedia
| Audacious Media Player | |
 |
|
|---|---|
 Audacious Media Player with default skin |
|
| Maintainer: | Audacious Team |
| Stable release: | 1.3.2 (April 5, 2007) [+/-] |
| Preview release: | [1] () [+/-] |
| OS: | Linux, Unix |
| Use: | Media player |
| License: | GNU General Public License |
| Website: | audacious-media-player.org |
Audacious is a free software media player for POSIX standards compliant based systems. It is a fork of Beep Media Player 0.9.7.1. William "nenolod" Pitcock decided to fork BMP after the original development team announced that they were stopping development, in order to create a next-gen version, BMPx.
The reasons for the fork were purely technical. There were some quirks in Beep Media Player that had annoyed users, such as the ID3v2 tag handling, which had been reported as "buggy" 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 streaming, such as support for an XMMS-like "songchange plugin".
Audacious has full support for Winamp 2 skins, and as of version 1.2, some free-form skinning is possible, which is expected to be improved upon in the 1.3 release.
Contents |
[edit] Plugins
Current SVN versions of the Audacious core classify plugins as follows (some are lowlevel and not uservisible 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 AudioScrobbler)
- Output plugins, which provide the audio system backend of the player.
- Visualization plugins, which provide visualizations based on FFT fourier transforms 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.
It is also being discussed to implement service plugins, which will provide various components of functionality like General plugins, but be turned on by default instead of turned off.
[edit] Clients
Audacious supports the concept of other clients connecting to it, much like XMMS2, BMPx and MPD. The only known clients at this time however, are:
Connection to audacious for remote control is usually done over a unix socket, located in the temporary files directory. However, Audacious also supports control over the TCP protocol. The TCP control option, however, is not exposed in the preferences dialog at this time, but instead must be manually enabled in the configuration file or GConf database.
