Audio Player Comparison

Overview

Requirements

  • must be light on cpu and ram
  • small overall footprint
  • perform basic audio playing features (playlist management a plus)

Findings

AppTypeSizeCPURAMNotes
cmusncurses192,5063.7%8.096really like it, mutt of audio players
deadbeefGUI2,321,5545.0%22,496basic ui; it loads/plays my playlist!
vlcGUI1,211,81610.3%45,984A great 'plays anything' player but heavy on runtime resources
bansheeGUI192,506uses mono..., UTTER CRAP! will not play any of my music, GStreamer library error: Shutdown; do not like the interface (discover based)
rhythmboxGUI446,246does not work Jack error, do not like the interface (discover based)
musiqueGUI574,4589.3%53,992wants to scan for music...; very nice looking but doesn't seem to be able to save/load playlists, perhaps need a newer version
minirokGUI74,5246.7%81,052basic, doesn't seem to have a save/open playlists, does 'reload' last playlist, pulls in a LOT extra files (260+mb)
amarokGUI5,944,26621.9%122,224pulls in 226mb additional; way to much cruft
lxmusicGUI93,624basic, seems nice but it will not open any of my music, no errors/notices at all
jukGUI660,69610.3%55,992adds 163M of additional pkgs; I like the player, nice, simple, asks for search folder, and auto-imported playlist
guayadequeGUI1,632,51210.3%43,636nice l&f; imports playlists; a bit odd to get around in; has way to many features I'll never use (jamendo, etc.)
aqualungGUI800,8425.7%21,796mdi interface (bit oldschool looking; loads my playlist!;I like it!
bluemindoGUI168,876odd interface, difficult to find/do anything, would not play my music
exaileGUI1,056,13612.0%59,220not bad on install; somewhat intuitave; opens/plays my playlist!
mocncurses311,5524.0%9,260I like!; plays my playlist!; simple and straightforward!; very nice, maybe easier to use than cmus
yatmCLI14,258too basic, just a cli player like aplay; no playlist support
yauapCLI21,266simple cli player; no playlist support
qmmpGUI95,5148.3%35,156odd but basic/nice UI; opens/plays my playlist!
  • cpu % after 1min of play of 5 songs
  • ram (RES) XX after 1min of play of 5 songs
  • to find app size (in K): apt-cache show cmus | grep Size:

Test

  • install app
  • open app
  • create playlist with 5 songs
    • If it aint one thing, paramore-misery business, Hit it Again, Foo Fighters - Best of You, Foofighters everlong
  • close app
  • open app (with timer), open playlist, and play: appname & top -d 3.0 -n 21 -p $(pgrep -d',' -f appname) && fg
  • open app
  • get CPU/Memory stats from top

Results

cmus and moc are both good, need to run a larger (more songs and longer run) sample for memory/cpu comparisons.

Test #2

  • playlist has 37 songs (Advent Chamber Orchestra* & Various Artists (Dawn of*)
  • play for 45m
  • measure results
AppTypeSizeCPURAMNotes
cmusncurses192,5063.0%8,112
mocncurses311,5523.0%10756I noticed that often cpu utilization for moc was 0% during the run

Notes

  • cmus is a bit technical to learn but I do like it
  • moc/p is a bit more simple/straightforward
  • moc/p has a sort of front and back-end, you can close the ncurses ui and the backend (also mocp) will continue running, the above measurement for moc is with the front-end closed

Using cmus

  • man page
  • arch wiki
  • :a: ~/music - add files
  • v: stop play
  • c: pause play
  • b: next play
  • x: play
  • :clear - clear current view
  • y - add to playlist
  • 1 - library
  • 2 - sorted library
  • 3 - playlist
  • 4 - play queue
  • 5 - browser
  • 6 - filters
  • 7 - settings
  • :save -p FILE - saves playlist view to playlist file
  • :load -p FILE - load a playlist file to playlist view
  • s - toggle shuffle
  • r - toggle repeat
  • C - toggle continue

Using moc

  • install moc and moc-ffmpeg-plugin
  • start with mocp

Posts in this Series