Skip to content

Allow one adjacent final-size retry measurement - #490

Merged
cbusillo merged 2 commits into
mainfrom
code/439-second-bounded-probe
Aug 19, 2026
Merged

Allow one adjacent final-size retry measurement#490
cbusillo merged 2 commits into
mainfrom
code/439-second-bounded-probe

Conversation

@cbusillo

Copy link
Copy Markdown
Owner

Summary

  • allow one adjacent second measured sample only when the first bounded retry sample remains outside the final band on the same side as the completed output
  • preserve real measured quality, source-cap, CRF-window, monotonicity, and final-band gates
  • keep the replacement full-output retry budget at one
  • retain both sample outcomes in the target-size trace

Live evidence

The first post-merge Bluey verification exercised PR #489 safely:

  • CRF 34 full output: 53,800,650 bytes
  • target: 48,673,111 bytes; upper bound: 51,106,767 bytes
  • measured CRF 35: VMAF 97.33049; calibrated total 51,409,920 bytes
  • CRF 35 remained 303,153 bytes / 0.593% over the upper bound, so the planner correctly rejected it without a replacement full encode
  • no staged artifact or promotion; source remained unchanged

This follow-up permits the adjacent CRF 36 measurement before failing closed.

Validation

  • bash scripts/pre-commit-check.sh — 1,649 passed, 2 skipped; CLI, frontend checks/lint/tests/build, and web-route smoke passed
  • focused target-size tests — 64 passed, 18 subtests
  • scoped Ruff and git diff --check passed

Runtime scope

No output promotion is included. A second controlled exact-item verification remains post-merge.

Refs #439
Refs #256
Refs #273

@cbusillo
cbusillo merged commit f8c41cb into main Aug 19, 2026
6 checks passed
@cbusillo
cbusillo deleted the code/439-second-bounded-probe branch August 19, 2026 15:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants