Audacious

Audacious is a free and advanced audio player. It is focused on audio quality and supports a wide variety of audio codecs, and is easily extensible through third-party plugins.

Installation

Install the audacious package.

Configuration

AMIDI-Plug (MIDI Player)

To play MIDI and RMI files, it is required to install the fluidsynth package, and also install the sound font files, both freepats-general-midi and soundfont-fluid. No further configuration is required on the fluidsynth package, but for additional functionality check the FluidSynth instructions.

Afterwards, the plugin will be enabled, and in the plugin configuration panel (File, Settings ..., Plugins pane, Input tab, select AMIDI-Plug (MIDI Player)) add the installed sound font files one at a time (Extension .sf2) to the SoundFont dialog, they are located at /usr/share/soundfonts/.

Tips and tricks

Audtool

Audacious is shipped with a powerful management tool called Audtool which could be used to retrieve information or to control the player.

For example, to retrieve the current song's title or artist, issue the following commands:

$ audtool current-song
$ audtool current-song-tuple-data artist

There are also functions to control playback, manipulate the playlist, equalizer and main window. See audtool(1) for the whole list of options.

Winamp

To add classic Winamp skins to Audacious, just copy them to either ~/.local/share/audacious/Skins/ (user only) or /usr/share/audacious/Skins/ (system wide), then select them from the Skinned Interface tab in Preferences. Alternatively drag the skin file directly into the list view of available skins.

Troubleshooting

Audacious starts instead of file manager

See File manager functionality#Directories are not opened in the file manager.

gollark: Tautology Public License: you are free to do whatever you are free to do with this code. If the author is attributed the author must be attributed.

gollark: Maybe I should adapt the potatOS privacy policy as a code license.

gollark: MPL?

gollark: There is also the "secondary processor exemption" thing, which caused the Librem people to waste a lot of time on having a spare processor on their SoC load a blob into the SoC memory controller from some not-user-accessible flash rather than just using the main CPU cores. This does not improve security because you still have the blob running with, you know, full control of RAM, yet RYF certification requires solutions like this.

gollark: It would be freer™, in my opinion, to have all the firmware distributed sanely via a package manager, and for the firmware to be controllable by users, than to have it entirely hidden away.