Open erahhal opened 1 month ago
For my very similar setup, I am using a different solution: Piping the output from a snapclient connected to the 2nd snapserver into a pipe provided by the central snapserver.
snapserver.conf of the central snapserver:
source = pipe:///tmp/cd?name=CD&mode=create&dryout_ms=2000&sampleformat=44100:16:2&send_silence=false&idle_threshold=5000&silence_threshold_percent=1.0
Running on the same host as the central snapserver:
snapclient --logsink null -i 4 -h <ip_of_2nd_snapserver> --player file > /tmp/cd
Hope this helps!
Ah, I wasn't aware of the --logsink
option, thank you! I assume you can run multiple snapclients simultaneously? Anyway I will try this out!.
-i
It's working great, thanks again!
I'm going to leave this open as the issue still persists with direct TCP connections, just to keep track.
Describe the bug I've got three nodes around the house, and wanted to be able to serve audio from any of them, while clients are all connected to a single central node. What I did is have the central node add two TCP client streams pointing at the other two nodes, which are configured to serve PCM data. When a snapclient is connected to the central node and listens to one of these streams, it is audible but has a high frequency clicking noise on top. Is the PCM data served by snapserver true standard raw PCM?
Steps to Reproduce
Environment details
Attach logfile if applicable