Cover art in MPoD and MPaD
I often get questions regarding (missing) cover art in MPoD and MPaD. In this post I will explain what you can expect.
The apps have 2 methods of retrieving cover art. First they attempt to load the cover art from a web server, that is, if you have specified on in the settings for that specific connection. In order to use this method, a web server like apache needs to be running on the server that is hosting mpd, and it needs to share your entire music folder. As an example, here’s an extract from my apache configuration file:
Alias /music/ "/home/music/"
<Directory "/home/music/">
Options FollowSymLinks Indexes MultiViews
AllowOverride None
Order deny,allow
Deny from all
Allow from 192.168.1
</Directory>
This shares the music folder at http://machine-ip/music, so that address must be added in the MPoD or MPaD connection settings. Then, if you place a file named ‘Folder.jpg’ in a directory, MPoD and MPaD will use that image for all tracks in that directory. So this works well if you have organized your music per album.
If the apps can’t find a cover through this first method, they revert back to retrieving cover art from Amazon through a lookup based on artist and album name. This works often, but when there are strange characters in a title, or extra text like ‘[live disc1]‘ at the end of an album title the lookup can fail. And off course it will also fail when the music is unknown at Amazon. This may happen especially for less well known or regional music (like from the Netherlands).
Cover art that is embedded in mp3 or flac files is not accessible by the apps, because the mpd protocol currently doesn’t provide a function that pushes embedded cover art to clients.
To my knowledge, the Bryston BDP-1 doesn’t have a built-in webserver, so when using MPoD or MPaD with that player, only the 2nd, amazon based method will be used to retrieve cover art.