Allow per-player delay configuration #67
Open
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.
Players report
static_delay_msinclient/state(always present, 0-5000ms range). Servers can adjust it viaset_static_delaycommand for players that list it insupported_commandsin the player rolesclient/stateobject.Clients subtract
static_delay_msfrom server timestamps before scheduling playback (a 300ms delay means external equipment has 300ms latency, so playback starts earlier). Servers factor it into buffer calculations to maintain headroom. Value persists locally across reboots.Example implementations
static_delay_msset_static_delaysupportedLimitations
buffer_capacityand compensate that themselves.