Conversation
In VMs, wall clock timers (Stopwatch/QPC) can jump erratically due to hypervisor scheduling, causing fake sync errors and unnecessary audio corrections. This adds a MonotonicTimer wrapper that: - Enforces monotonicity (never returns decreasing values) - Clamps forward jumps to 50ms max per callback - Filters timer noise while preserving real DAC drift detection The wrapper is enabled by default in AudioPipeline, making all SDK consumers automatically VM-resilient without code changes. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
MonotonicTimerwrapper that filters erratic timer behavior in VMsAudioPipeline- all SDK consumers automatically benefitProblem
In VMs, the wall clock timer (
Stopwatch.GetTimestamp()/ QueryPerformanceCounter) can jump erratically due to hypervisor scheduling quirks. This causes:The audio device continues playing normally - it's only the timer measurement that goes wonky.
Solution
MonotonicTimerwraps anyIHighPrecisionTimerand:Real DAC drift accumulates slowly (~50ppm = 3ms/minute), so clamping per-callback deltas to 50ms doesn't hide actual sync issues.
Files Changed
src/Sendspin.SDK/Synchronization/MonotonicTimer.cssrc/Sendspin.SDK/Audio/AudioPipeline.csuseMonotonicTimerparam (default: true)Test plan