Developers never, ever, ever look at this page. This is ranting grounds. If you don't have enough energy to sign up for a proper feature request, then why should any developer have enough energy to grant one?

• support for the tunein api. http://dementsov.com/2011/07/08/analysis-of-tunein-radio-stations/
• Just a thought.. If MPD ran on a cheap platform, i.e. Raspberry Pi ($25 PC ARM runs Debian), you could add a couple of cheap amp modules, and you've practically got yourself a sonos amp for under $100. If this seems like a good idea, then something I think is missing from the MPD is the ability to run a multi room system, all playing the same thing in sync (probably more difficult to do than it sounds...)
  • I've been building myself something along these lines on my own network that works quite well, by outputting audio via HTTP stream & picking it up with other client devices
  • I am using Pulseaudio RTP to perfectly sync a couple of Raspberry Pi. Works great!
• make it possible to connect to a specific port within Jack on startup (e.g. an equalizer or mixer application)
• Album Covers - plans for how MPD should support fetching/storing/displaying album covers.
  • As MPD is a Daemon this should be done by the client.
• Queue - plan for how MPD should/would/might implement queuing
• Add cue sheet (.cue) support (with FLAC+WV embedded cue support, see patch)
• Rotation and scheduled Playlists for Internet Radio (compare http://www.centova.com/docs/cast/centovacast_user_guide.php)
• Executable Songs - plans to make it possible to add scripts to the database and let them play like a normal track.
• dynamic playlists that allow pre-selection of certain criteria such as genre, rating, randomization, limiting of the playlist length and so on:
  • examples: 60 minutes of random music of genres "Pop" and "Rock", your favourite 100 songs or serious music, i.e. everything excepting your huge collection of B. Spears :)
  • see here and here for some ideas
    • Check the MPDC client
  • I think that this should be implemented in MPD and not in clients, so it needs only be done once and properly
    • I disagree. After all one can have many clients connected to the server. One of the clients may be the one doing scheduling of songs. No other client need to implement that feature.
• Simple way to keep MPD from resuming playback on boot. (http://wiki.archlinux.org/index.php/Mpd#Never_play_on_start)
  • Available in git: b57330cf... and 2fb40fe...
  • I'm using “sed -i -e 's/^state: .*$/state: pause/' mpd.state”.
• handling more audio-outputs at once, playing different music/audio on every output
• allow the user/client to set tags (flags) and be able to order by them.
• give MPD the optional ability to play a single file from some location on the filesystem outside of the music database.
• support and input plugins for .SID, .AHX, and hivelytracker filetypes.
  • SID should work with the sidplay decoder.
• support and input plugin for UADE
• support .pls-playlists (or others) so it's possible to use playlists of radio-streams with titles
• support for metadata such as tracking play count, ratings for tracks
  • Also the last play date for the track, as well as the date of adding to the library
• music-based representation instead of file-based, ie. if there's the same album in FLAC and MP3 it's only shown once
  • Also, always choose the best quality.
• MPD should auto-discover pulseaudio output/sinks
• identify multiple concatenated vorbis tracks within an OGG and present as an album of tracks. (similar to cue-sheet support? alternatively, can cue sheets be embedded in OGG (or vorbis metadata?), and is there any precedent for that?
• Support for Microsoft Windows
  • Is available.
• Make it possible to auto-pause playing, when httpd is the only enabled output device type and no client is connected to the stream.
• give MPD the optional ability to remove blank at end of tracks (without crossfade)
• No password for localhost connects, when password set otherwise
• Option to stop playback after the current track has finished
  • Use "single" mode.
• Have mpd call a callback script when a particular even happens (e.g On next track, on pause, on stop)
  • Clients can do that, e.g. mpc.
• Queue some songs in MPD current playlist which would play one song after another
• Echo Nest Client to generate playlists http://developer.echonest.com/docs/v4/playlist.html
• setting cue points in Id3 tags for fade in and fade out markers (radio style mixes)
• automatic beatmatching and timestretching (probably taken from mixxx)
• auto-level based on compressor/limiter (not just replay gain)
• text to speech plugin to "play" and pipe textes (such as announcing tracks etc.)
• microphone input
• sub-integer/millisecond seek functionality, so that MPD can be used as the player back-end to DJ mixing apps
• report to clients if wake-on-LAN is supported for auto-configuration by client, also ability to power down when idle for a defined duration and even have clients power down if enabled.
• mpdignore should be more like gitignore where only one file is needed for entire music collection
• server defined (user) functions that can appear as options/buttons on clients, I.e. turn on 12v trigger to amp, send IR code to amp, turn on lava lamp. Label, command, image, where label and image is provided to client, client can send label pushed when pushed
• slow ramp of volume on restart/power on, or restart at defined level
• Use mpd as DLNA/uPNP MediaRenderer to stream music to it.