Add SessionSnapshot: single-lock consistent session capture for RT hosts - #3
Merged
Merged
Conversation
Hosts driving a realtime audio thread cannot take the peer's internal lock per block, and a sequence of individual getters (tempo, then beat_at_time, then is_playing) can straddle a timeline or session change and disagree. capture_session() returns tempo, beat, phase, transport, membership, and session id from one lock acquisition; SessionSnapshot::beat_at/phase_at extrapolate with pure arithmetic — exact while the timeline is unchanged, superseded by the next poll after a change. Also: factor the num_peers dedup into count_peers() (shared with the snapshot path) and apply rustfmt to examples/rapid_tempo.rs, which was failing the fmt gate. Derived only from this repository's existing code and spec-permitted inputs, per PROVENANCE.md. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TfnHrUHAfe7RaWNfyggDPP
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
2 participants
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.
Hosts driving a realtime audio thread cannot take the peer's internal lock per block, and a sequence of individual getters (tempo, then beat_at_time, then is_playing) can straddle a timeline or session change and disagree. capture_session() returns tempo, beat, phase, transport, membership, and session id from one lock acquisition; SessionSnapshot::beat_at/phase_at extrapolate with pure arithmetic — exact while the timeline is unchanged, superseded by the next poll after a change.
Also: factor the num_peers dedup into count_peers() (shared with the snapshot path) and apply rustfmt to examples/rapid_tempo.rs, which was failing the fmt gate.
Derived only from this repository's existing code and spec-permitted inputs, per PROVENANCE.md.
Claude-Session: https://claude.ai/code/session_01TfnHrUHAfe7RaWNfyggDPP