ahayworth / snapcast-autoconfig Goto Github PK

os: Arch linux
snapclient: 0.25.0
snapserver: 0.25.0

First off, I realise this is a side-effect of how Snapcast works when removing clients from groups ;)

In this scenario:

• there are two clients c1 and c2
• each client has its own preferred stream (s1, s2)
• a "party" stream s0 is lower priority and plays to both s1 and s2

To repro:

• Play s0 such that c1 and c2 form a playing group g0.
• Pause s0 -> c1 and c2 remain in g0 which is Idle
• Play s1 -> the group splits

Result:

• c1 is in group g1 playing s1
• c2 is in group g2 playing s1 <-- DOH!

Expected:

• c2 remains in group g0 which is Idle

Config:

---
server: tcp://localhost:1705
streams:
  Canard:
    clients:
      - canard
  Kitchen:
    clients:
      - kitchen
  Party 1:
    clients:
      - canard
      - kitchen

The result is the same even with more clients in g0. All clients end up in individual groups playing s1.
log.txt

This actually works pretty well for me, but the README is snarky and not helpful. We should re-write it to actually better describe what this does and how to use it.

This script is highly specific to how I run my home audio system, but it could be a lot more flexible. The configuration file should express three concepts:

• Streams to watch
• Clients to care about
• Rules

That would allow us to build a more flexible system, and specify what to do for undefined situations (eg: if a group exists with a configured client but doesn't match a rule, what should be done? Leave it alone? Forcibly move it? To where? etc).

Add:

• Example systemd unit
• Docker image