-
Notifications
You must be signed in to change notification settings - Fork 98
fix(meet-bot): normalize reconnect-reset threshold to audio duration #26509
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚩 Pre-existing incorrect frame duration in comments (10ms, not 20ms)
Multiple pre-existing comments claim that 320 bytes at 16kHz s16le mono is a "20ms frame" (lines 12 and 44–46), but the actual duration is 10ms: 320 bytes / 2 bytes-per-sample = 160 samples, and 160 / 16000 Hz = 0.01s = 10ms. A true 20ms frame at 16kHz would be 640 bytes. This doesn't affect runtime behavior (the frame size in bytes is what matters, not the label), but the misleading comments were the source of the old
MIN_FRAMES_TO_RESET_BUDGET = 100being set to half the intended value — the author likely computed 100 frames × "20ms" = 2s, when it was actually 100 × 10ms = 1s. The new PR's formula sidesteps this confusion entirely by computing from first principles, which is a clear improvement.(Refers to lines 44-47)
Was this helpful? React with 👍 or 👎 to provide feedback.