Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Music Player Daemon vs MPlayer, the Slant community recommends Music Player Daemon for most people. In the question“What are the best audio players for UNIX-like systems?” Music Player Daemon is ranked 16th while MPlayer is ranked 43rd. The most important reason people chose Music Player Daemon is:
MPD is a music player server that requires a separate client for user interaction. There are many frontends available, with the most popular being ncmpcpp.
Specs
Question Ranking
Pros
Pro Multiple frontends available
MPD is a music player server that requires a separate client for user interaction. There are many frontends available, with the most popular being ncmpcpp.
Pro Features provide a good music experience
While mostly bare-bones, Music Player Daemon does include a few features which help make it perform well. Buffer support ensures that your music continues to play without interruption even when your system is under an extremely heavy (but temporary) load, gapless playback starts loading a song just before it's needed so that it's ready to play the instant the last song ends. Meanwhile, crossfading allows your songs to blend into one another for continuous playback.
Pro Easy to use with various outputs
Pro Needs no additional codecs
Everything MPlayer needs to play media files is contained within which means no outside codecs are needed.
Pro Easy shortcut keys
Quick skip ahead buttons and other shortcut keys.
Pro No bugs , no lag in the video display
Pro Works via CLI and has multiple frontends to choose from
Some of the more popular frontends include Deepin Media Player, GNOME MPlayer, KPlayer, KMPlayer, Rosa Media Player, SMPlayer and Xt7-Player.
Pro Nice theme available to choose from
Also, the video window is separate from the main window making it less cluttered while playing audio
Cons
Con Not a music player, only a music server
You know how you need your browser (Firefox, Chrome, etc.) to access web pages? The browser is what YOU touch, see, and interface with, but in order for it to give you anything it must connect to a server that "serves" appropriate content. mpd is the server in this analogy, NOT the thing you actually use. The front-ends that are available for mpd, now those are music players.
Con May not conform to how you organise your library
MPD expects you to have all your music in a single folder (music_directory) and use symbolic links to retrieve other resources.
Con Poor tagging support
Does not support enough tag types.
Con Requires a refresh every time you add music
MPD won't automatically refresh it's library - if you add music to your music folder, you will have to manually tell MPD to refresh or else it won't add the new music.
Con Not much documentation on the use and configuration
Con Contrary to review, some media that play well in vlc does not play in mplayer
Con Doesn't support directory playback
Con Lacks a built-in visualizer
