Nick Steel

Agree. There's enough async footguns out there and no prizes for finding them. Use something off the shelf where possible.

I can't see anything going wrong in the log, it seems to be doing what it's been told to. I also can't reproduce this, but I don't have the macOS...

Isn't this an upstream alpine packaging issue? Something related to https://gitlab.alpinelinux.org/alpine/aports/-/commit/e6ca7ceb8bb15a8ae044f29bccd8bea3415755b3 ?

I think that's wise. The alpine Mopidy package only depends on a couple of gstreamer plugin packages. I've no idea if that's intentional or a mistake.

Surprised to hear this doesn't work. Are you sure Mopidy isn't getting this right? What's the output of the commands at https://docs.mopidy.com/stable/troubleshooting/#track-metadata for one of your files?

Does exposing settings fall under this? https://github.com/mopidy/mopidy/issues/502

If you're using an access token derived from Spotify's desktop client ID (or similar), it should keep working for now. Presumably you're doing that. I think there's a good chance...

There's already enough complexity supporting multiple gstreamer versions, the idea of more complexity here is unattractive to me. How many people have found themselves unable to use gstreamer over the...

That's one person in 15 years... I don't think that level of demand is worth the significant extra debug surface and maintenance burden. Although I appreciate the confirmation bias here....

> It's also possible that since GStreamer has been always(?) listed as a required dependency, no one has challenged that Yeh, that's what I meant by the confirmation bias. Most...