multiroom as server

[Tim Curtis]

No not latency, trx receiver when running on the sender could not receive multicast packets. It could be that some sort of special network config is require, I don't know.

I ask in the bark repo a long time ago but no response from the maintainer so this project is a non-starter for me.

I've never tried your usage scenario but for sure you can't run two senders using the same multicast address on the network. I suppose you could try using a different multicast address for the second sender and receivers and see what happens.

I'm not sure what type of networking Snapcast uses, or any of its other capabilities. My interest in it has to do with its capability to maintain clock sync between sender and receivers which improves the to-the-ear sync.

@lifeform, I did a quick test this morning running two senders and distributing different streams to their respective receivers and no problems.

Sender-1 and Receiver-1 at 238.0.0.1 
Sender-2 and Receiver-2 at 238.0.0.2

The multicast address is not exposed in the config UI but here are the commands to update the address. Restart the sender and receiver after updating.

Code:

# Sender Pi
moodeutl -q "update cfg_multiroom set value='239.0.0.2' where param='tx_host'"

# Receiver Pi
moodeutl -q "update cfg_multiroom set value='239.0.0.2' where param='rx_host'"

Currently in the UI there is no address filter on the Receiver and Discovery lists so both senders will see the same list of receivers even though they will only be able to send to receivers configured with their multicast address. I could add that filter and also add the address field to Receiver Config > Advanced.

What do you think?