Repository navigation
Improve multi-device sync continuity and recording-overlap retention - #8
Merged
zifangzhao merged 3 commits intoSep 24, 2026
Merged
Conversation
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
Stable recordings could lose usable data when temporarily weak correlations or small, unlocalized lag changes were treated as synchronization failures. Retention rates also penalized differences in recording length.
This change:
The existing 1 ms tolerance, missing/repeated-data handling, and independently localized discontinuity boundaries are preserved. Versions advance to pipeline v24, sync v16, and manifest schema 20.
Validation
Reprocessed three complete recordings with synchronization, merge, duplication scanning, and post-merge QC: