Rename minBuffer to jitter

[kixelated]

No description provided.

[coderabbitai]

Walkthrough

This pull request refactors the audio and video configuration schemas across TypeScript and Rust codebases by replacing the minBuffer field with a new jitter field. The change systematically updates configuration structures in the catalog modules, type definitions in utility files, and all implementation sites including audio/video codec handlers and example code. The minBuffer field, representing minimum buffer duration, is replaced with jitter as an optional numeric parameter. Related calculations, documentation comments, and buffer computation logic are updated to reference the new jitter terminology throughout.

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 9.09% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Description check	❓ Inconclusive	No pull request description was provided by the author, making it impossible to verify whether the description relates to the changeset.	Add a description explaining the motivation and impact of renaming minBuffer to jitter, such as why jitter better represents the field's purpose in latency and buffering calculations.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Rename minBuffer to jitter' directly and accurately describes the primary change across the entire changeset—a systematic field rename from minBuffer to jitter throughout TypeScript and Rust files.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch jitter

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

rs/hang/src/import/fmp4.rs (1)

490-670: ⚠️ Potential issue | 🟠 Major

Track the maximum jitter, not the minimum.

Jitter is documented as the maximum time before the next frame is emitted, but the current logic stores the smallest observed jitter. This can underreport jitter when segments vary in length, leading to insufficient buffering and playback stutter.

✅ Suggested fix

-				if jitter < track.jitter.unwrap_or(Timestamp::MAX) {
+				if jitter > track.jitter.unwrap_or(Timestamp::ZERO) {
 					track.jitter = Some(jitter);

🤖 Fix all issues with AI agents

In `@rs/hang/src/import/fmp4.rs`:
- Around line 71-73: The field comment for jitter no longer matches its name:
update the doc comment above the jitter: Option<Timestamp> field in the relevant
struct (where jitter is declared) to describe jitter semantics instead of
"minimum buffer"—for example, explain that it represents timestamp jitter
allowance or variability used for track timing calculations so the comment
accurately documents the jitter behavior.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Minor doc mismatch: field renamed to jitter, comment still says “minimum buffer.”
Consider updating the comment to match the new jitter semantics.

✏️ Proposed doc tweak

-	// The minimum buffer required for the track.
+	// The maximum jitter before the next frame is emitted.

🤖 Prompt for AI Agents

In `@rs/hang/src/import/fmp4.rs` around lines 71 - 73, The field comment for
jitter no longer matches its name: update the doc comment above the jitter:
Option<Timestamp> field in the relevant struct (where jitter is declared) to
describe jitter semantics instead of "minimum buffer"—for example, explain that
it represents timestamp jitter allowance or variability used for track timing
calculations so the comment accurately documents the jitter behavior.