Allow to have separate idle & silence thresholds #1291
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For asio (e.g. pipe) there is a difference between idle (no data being written to) and silence.
Silence also happens on normal music (silent periods or fade out). Too short a silence timeout messes up playback with meta streams. The active stream would switch on fade-out / silence and immediately switch back on next track / non-silence, causing clients to resync and stutter.
This patch allows you to configure ilde_timeout independently from silence_timeout. Both options were undocumented for asio streams (pipe, pcm, ...). It also allows you to disable silence detection, getting back older snapcast behavior.