Nick Steel

The error is in the log, it's related to pulseaudio. You also said in your other issue (which you could have just reopened?) that the difference between this non-working setup...

You want ``` default-server = 127.0.0.1 ``` Also, when running things as a system service they often run as a different user compared to when you run them normally in...

> pi@raspberrypi:/etc/pulse $ systemctl --user status pulseaudio.service That's a *user* service.... Not sure that is interesting. > So calling 'sudo -u pi' should do no difference, shouldn't it? When using...

Alsa dmix plugin allows multiple sources at the same time. It just works

It would also be better if you just post in one place. Cross posting all this different info in two places is really confusing.

Pulseaudio have kindly documented what's wrong with running it in system mode: https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/ ------------------------- Anyway, I had a go with the latest RPi OS and found the same: 1. Fresh...

Raspberry Pi OS desktop image is exactly a desktop system. The lite image you can get away with pretending it's an embedded system but that's not even using pulseaudio so...

We've actually hit a very [similar problem](https://github.com/mopidy/mopidy-mpd/pull/49#issuecomment-1013359408) in Mopidy-MPD and didn't yet resolve it. We should probably "fix" Mopidy-Local to provide absolute image URLs but it's not as simple as...

This looks a lot like a Docker permission problem rather than something wrong with snapcast.

Sounds fine, providing you follow instructions for [running in a terminal](https://docs.mopidy.com/en/latest/running/terminal/) in terms of config file location etc and don't use `mopidyctl`. This bug tracker is not for questions, use...