06-10-2024, 02:00 PM
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.
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.
