Thomas Adamcik

Essentially #1100 as the other alternative/workaround then?

`ActorDeadError` is just telling us that something killed that thread previously. Do you happen to have any errors or the like earlier in the logs?

This is a bit tricky, as we don't currently have a way to do "bookmarks" into a file like we would need for the cues. I presume we should also...

I can't seem to easily reproduce this.

As long as any one calling core gets a new list. And not the one the backend gave us. I'm wondering what would happen if a backend passed a list...

Reviving this since it never got that much traction. I would be happy to accept this contribution and switch logo. @jodal @kingosticks thoughts?

Skimming over quickly the following issues come to mind: - #1100 which covers letting extensions expose APIs to other extensions. - #1123 for equalizer support. - #1118 for dynamic /...

Probably yes, but not yet. We have a separate bug for that #270. My rationale for this is just to have a way to flag things that a mpd-watchdog type...

Having a stream type might also be a way to have a backend indicate that something should be using `is-live`. The other toggle that might make sense for some backends...

Two points: 1. If we go with fixing this via a magic value it should be `AFTER_CURRENT = ...` or something like that. Not a bare magic value. Ideally this...