Music Player Daemon

Not possible currently. See related feature request: https://github.com/MusicPlayerDaemon/MPD/issues/1010

@Ameisenwespe, https://www.musicpd.org/help/

Don't mess with those settings. It will not improve quality - I mean, how could it possibly? MPD plays back digital audio, and changing buffer settings does not change the bits which are sent to the sound hardware. It will not be any more efficient - quite the contrary! It is less efficient, because...

play_song is: "addid FILE" (which returns the song id) and then "playid ID". For "playtime_remaining", call "status" and you'll get the elapsed time in the current song, and the total song time. "play_song_next" is "addid" and "moveid" (move the new song to the position after the current song, deter...

I have never heard of such a tag, and therefore MPD does not support it. If you want MPD to support it, submit a feature request with a link to the formal specification for each codec.

Your bug report was very confusing. I thought this was about listing the source file twice. Since you did not upload your CUE file, there was nothing else I could do. "enable" has to be set to "yes", otherwise the file is ignored. Not true. "yes" is the default value - you don't need to specify this...

Only one thing is sure: MPD is more efficient than Mopidy, because MPD is written in C++, and Mopidy is written in Python. For the same task, Python is usually slower than C++ by orders of magnitude. More reliable, more stable? - I have no idea, I have never used Mopidy, so I can't compare. If you h...

This is not the right place to report bugs. https://github.com/MusicPlayerDaemon/MPD/issues/ is.

If "mpc update" doesn't make those entries with Genre "149" disappear, then the files listed below that genre "149" exist and have this "Genre" tag.

The database cannot be edited. You can only update it (e.g. "mpc update").
What does "crufty old obsolete data" mean, really? Data of files which have been deleted meanwhile? Data of files which have been modified meanwhile? "mpc update" will take care of both.

Fix for the garbage filter name in the error message: https://github.com/MusicPlayerDaemon/MPD/commit/b0002e3b73e2d09a9eb0d815f86342dc96918ef5 Fix for the filter format error: https://github.com/MusicPlayerDaemon/MPD/commit/2da3cff1e8a5e1558d47a8493eaa9503b2d56b9e MPD 0.22.3 will be released soon wi...

This is a bug in the filter plugin - I'm just about to fix it. Expect a fix soon in version 0.22.3.
If you encounter bugs or behavior that looks like a bug - write a bug report on GitHub. There, it's easier to track it.

1. Because nobody spent time on making libshout available in the MPD Windows build.

2. Only with the "shout" output plugin. Your option is to build MPD for Windows manually, after porting libshout to Windows. It's open source! Power to everybody!

Now that's the proper error message! And true, the "shout" plugin is not enabled in the official MPD binary for Windows.
The "httpd" output can be used instead of Shoutcast. It cannot talk to Shoutcast, it replaces Shoutcast.

Your latest output shows that MPD starts succesfully, and is now running, but you never tried to connect with a client. You never tried to play something. You wrote: "MPD is not connecting to the shoutcast server" Of course it's not. You did not tell it to. Your configuration shows you configured an...

https://www.musicpd.org/help/
You did not post your log.
The messages you posted are not relevant for your problem, as I already said.

None of what you wrote has anything to do with the FFmpeg input plugin.
But I don't understand your problem - you need to post more information about what you did and what exactly did not work (and what you saw instead).

That's okay, you can use it, but I don't want to get any bug reports from users of your package.