Mike Brady

> It is my unclean development branch. It may take me a few more days before I can try to start fresh again off your code. Okay, thanks 😊!

Thanks for the post. On the `development` branch, the list of libraries needed has changed from before — please refer to the [BUILD.md](https://github.com/mikebrady/shairport-sync/blob/development/BUILD.md) guide on the `development` branch.

Thanks for the post. The pipewire backend is the one called `pw`. The `pipe` backend is for outputting to a UNIX pipe.

You’d need to check the package makers about support for `pw`. Yeah, the default is probably `alsa`.

Thanks for the comments. There are a few moving parts here, so it's difficult to figure out what's happening. It might be useful to get the settings and configuration strings...

Okay, thanks for that comprehensive report! #### 4.3.5-1 The package does not have pipewire support built in -- when you look at the version string: ``` 4.3.5-OpenSSL-Avahi-dns_sd-ALSA-jack-pa-stdout-pipe-soxr-metadata-mqtt-sysconfdir:/etc ``` ...it does...

Thanks for the post. Could you post the docker command(s) you are using to invoke the player, please? Is it possible you are not mapping a configuration file into the...

I think I see the problem — you have nested the `mqtt` and the `metadata` stanzas inside the `general` one. They should not be nested.

Thanks for the report. The configuration file output looks a little odd. The entry: ``` output_device = "hw:1"; ``` must be within the `alsa` section. If it was, it would...

Thanks for the post. The core idea is that an image tagged with any kind of version number -- possibly including a minor revision number and a bug fix number...