Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow to have separate idle & silence thresholds #1291

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

skeller
Copy link

@skeller skeller commented Oct 14, 2024

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.

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant