Ampache has the ability to remote control an MPD instance over the network. MPD or Music Player Daemon is designed for integrating a computer into a stereo system that provides control for music playback over a local network. this document will walk you through the steps on how to setup localplay with MPD. It is assumed that you have
Admin rights on your Ampache instance.
In all new installs of Ampache the MPD module is, by default, enabled. To verify that it is currently enabled click on Modules and then look under Localplay Modules
When you activate the MPD module Ampache automatically enables Localplay globally, sets your play type to Localplay, sets your Localplay Access to Admin and sets your Localplay type to MPD. You must do the same for any other user you would like to be able to use MPD.
Once you have that setup you will need to add an Instance of MPD. Ampache works on the principle of distinct Localplay Instances which each have their own settings, an owner and an access level. This allows a single user to control a very large number of MPD instances with a click of a button.
Localplay --> Add instance
You will be given several options when creating an instance, such as instance name and hostname and port. Name is how Ampache will represent the instance on the sidebar. The Hostname is the IP or DNS name of your MPD instance. If MPD is non-local make sure that it is listening on the correct IP. Port is by default 6600 only change if you have modified your mpd.conf.
Once you created an instance you the name of the instance should show up under Active instance. All that you have to do to start using it is click on its name. It should turn blue to indicate that the change was successful. At any time you can switch back to Streaming by clicking None or start managing a different MPD instance by clicking on its name.