search

badaix / snapcast

Synchronous multiroom audio player
GNU General Public License v3.0
6.19k stars 457 forks source link

Snapserver pipe source not switching to idle #1123

Closed isolatedvirus closed 4 months ago

isolatedvirus commented 1 year ago

Snapserver configured to accept fifo output from snapclient will not change the source to idle when nothing is playing. This results in silence being played, and will also block audio from lower priority sources when configured in a meta source. Current workaround is to list the source as lower priority in the meta source config to avoid blocking audio, but this does not address the constant output of silence.

Setup Central snapcast server is being used to stream audio to various phones, raspi devices, laptops, etc. This server is not physically located where i want to capture audio. The audio flow is: alsa capture device --> snapserver --> snapclient (output to named pipe /tmp/vinyl) --> snapserver (read from named pipe /tmp/vinyl) --> snapclients

I've included a diagram to hopefully make this more clear:

Steps to Reproduce 1.Configure downstream snapcast server to send audio 2.Configure upstream snapcast client to pipe audio to fifo file using "--player file:/tmp/filename" 3.Configure snapcast server on upstream client to utilize the same fifo pipe. 4.Configure meta source on upstream server and set higher priority for the new fifo pipe 5.Play audio to lower priority source. This source will be blocked as the higher priority "snapclient fifo source" will begin blocking. This source will not be marked idle regardless of any dryout_ms setting.

Environment details

Debug log output Logs from Fedora snapclient

2023-04-12 18-42-57.351 [Debug] (Stream) Failed to get chunk, returning silence
2023-04-12 18-42-58.001 [Info] (Stream) No chunks available
2023-04-12 18-42-58.401 [Debug] (Stream) Failed to get chunk, returning silence
2023-04-12 18-42-59.001 [Info] (Stream) No chunks available
2023-04-12 18-42-59.451 [Debug] (Stream) Failed to get chunk, returning silence
2023-04-12 18-43-00.001 [Info] (Stream) No chunks available
2023-04-12 18-43-00.501 [Debug] (Stream) Failed to get chunk, returning silence
2023-04-12 18-43-01.001 [Info] (Stream) No chunks available

Logs from Fedora snapserver

2023-04-12 18-42-57.168 [Debug] (StreamSessionTCP) getNextMessage: Time, size: 8, id: 0, refers: 0
2023-04-12 18-42-57.168 [Debug] (Server) onMessageReceived: Time, size: 8, id: 0, refers: 0, sent: 1681339377,162046, recv: 338311,674028
2023-04-12 18-42-57.716 [Debug] (StreamSessionTCP) getNextMessage: Time, size: 8, id: 2745, refers: 0
2023-04-12 18-42-57.716 [Debug] (Server) onMessageReceived: Time, size: 8, id: 2745, refers: 0, sent: 334073,144231, recv: 338312,222243
2023-04-12 18-42-58.168 [Debug] (StreamSessionTCP) getNextMessage: Time, size: 8, id: 0, refers: 0
2023-04-12 18-42-58.168 [Debug] (Server) onMessageReceived: Time, size: 8, id: 0, refers: 0, sent: 1681339378,162102, recv: 338312,674180
2023-04-12 18-42-58.716 [Debug] (StreamSessionTCP) getNextMessage: Time, size: 8, id: 2746, refers: 0
2023-04-12 18-42-58.717 [Debug] (Server) onMessageReceived: Time, size: 8, id: 2746, refers: 0, sent: 334074,145025, recv: 338313,222892
2023-04-12 18-42-59.168 [Debug] (StreamSessionTCP) getNextMessage: Time, size: 8, id: 0, refers: 0
2023-04-12 18-42-59.168 [Debug] (Server) onMessageReceived: Time, size: 8, id: 0, refers: 0, sent: 1681339379,162320, recv: 338313,674332
2023-04-12 18-42-59.717 [Debug] (StreamSessionTCP) getNextMessage: Time, size: 8, id: 2747, refers: 0
2023-04-12 18-42-59.717 [Debug] (Server) onMessageReceived: Time, size: 8, id: 2747, refers: 0, sent: 334075,145543, recv: 338314,223560
2023-04-12 18-43-00.187 [Debug] (StreamSessionTCP) getNextMessage: Time, size: 8, id: 0, refers: 0
2023-04-12 18-43-00.187 [Debug] (Server) onMessageReceived: Time, size: 8, id: 0, refers: 0, sent: 1681339380,181895, recv: 338314,693795
2023-04-12 18-43-00.718 [Debug] (StreamSessionTCP) getNextMessage: Time, size: 8, id: 2748, refers: 0
2023-04-12 18-43-00.718 [Debug] (Server) onMessageReceived: Time, size: 8, id: 2748, refers: 0, sent: 334076,146332, recv: 338315,224249
2023-04-12 18-43-01.188 [Debug] (StreamSessionTCP) getNextMessage: Time, size: 8, id: 0, refers: 0
giantorth commented 1 year ago

I am encountering the same issue with squeezelite clients connected via stdout or fifo to snapcast 0.27. I've verified that the squeezelite client sends no data when idle but snapserver will not actually mark the source as such.

patrex0304 commented 11 months ago

I have a same problem. I have a pulse audio source that is written into a pipe. Snapserver reads that pipe. I have a metastream that changes between that pipe and other inputs. The pipe has the highest priority. After a certain runtime the snapserver does not change the the source of the metastream anymore. It just keeps switched on the pipe even if nothing writes to the pipe.

badaix commented 6 months ago

When using alsa capturing, you will always have some noise floor, you can configure a threshold for this with the silence_threshold_percent parameter