Music Player Daemon

I wish somebody could improve the documentation in a way that users like this guy understand it. I don't know how - I cannot even remotely imagine why anybody would ever read "you need Meson" and then proceed without having Meson. From my point of view, it can't be any clearer than "you need Meson".

You didn't install Meson, and now you wonder why the "meson" command was not found?

The manual lists exactly those commands you are now asking for. https://www.musicpd.org/doc/html/user.h ... rom-source

You wrote "the user manual is losing me" and "gave me errors", but that's not something anybody can help you with, as long as you keep details of your problems secret.

Can you write a bug report on GitHub? Are you using the same MPD version on both machines?

If you use systemd, you can copy mpd.service to mpd2.service and add the path of your second configuration file as parameter to ExecStart. In the second configuration, specify a different port (e.g. 6601 instead of 6600).
Then in your client, you can run "ncmpc -p6601" to connect to the second MPD.

You can choose any directory structure you like. That is only a matter of taste.

MPD will play the same music on all outputs. MPD can have any number of clients, but they all control one shared state. If you want to play two different things at a time, launch MPD twice (on different control ports).

You can configure two audio outputs.

If you really want to stay with Ubuntu, the "disco" version has MPD 0.21.4. So either upgrade to "disco", or do a backport, or compile from source.

Thanks, nginx needed to be restarted. For an unknown reason, the ACME script doesn't do that automatically, sigh.

Just like skidoo, I can't reproduce this with MPD 0.21. This suggests it could be fixed by upgrading. MPD 0.20 isn't supported anymore, so there's no point in using that version.

Here's my patch submission for updating OpenEmbedded's MPD recipe to 0.21.3: https://patchwork.openembedded.org/series/14981/
It was however not merged because there were problems on the buildbot, but nobody was able to explain them to me.

Paste a verbose log of the start of playback

Your MPD version is very old and unsupported.

kiwi_ed wrote: ↑

January 22nd, 2019, 5:29 pm

However reverting the actual MPD executable for testing to 0.20.23 with these updates still MPD still behaved.

What does that mean?

My Pi3 doesn't have any HDMI options in /boot/config.txt, and I don't know what this option means. All I can say is that it works without any bootloader configuration.

Confusingly, both AAC and ALAC use the file name extension ".mp4".

I think neither AAC nor ALAC are worthwile. They are proprietary codecs which are not better than Vorbis/Opus and FLAC. Just stick with those free codecs.

I have: audio_output { type "alsa" name "My ALSA Device" device "hw:0,1" } It's "hw:0,1" because "aplay -l" shows: **** List of PLAYBACK Hardware Devices **** card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA] Subdevices: 7/7 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subd...