Added data savings estimates to Compare Quality tab - #18
Open
CodyCBakerPhD wants to merge 2 commits into
Open
Conversation
Compare Quality reported only the encoded snippet's byte count, which says nothing about what the settings do to the file. It now projects the whole file: the snippet against what the same seconds cost in the source, that ratio applied to the source's real size, with a headline figure and two bars above the panes and an Estimate Detail block, its method and its limits, below the comparison. Where the container has a sample table the source's cost for the sampled stretch is summed straight out of it, so a snippet from a busy stretch divides by an equally busy original rather than pricing the file at its worst moment; otherwise the file's size is spread evenly over its running time and the copy says so. The projection carries a range drawn from how far the file's own equal-length windows sit from one another, narrowing as more of the file is sampled and dropping away once all of it has been encoded. The Full Analysis document reports the same numbers, so a saved report carries the estimate and its caveats too. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KDzwviXNsjYHnSVDGCdrxZ
|
Important UI Tests need review – Review now🟡 UI Tests: encoding-helper-storybook: 4 changes must be accepted as baselines |
|
|
Tip All tests passed and all changes approved!🟢 UI Tests: encoding-helper-playwright: 2 tests unchanged |
Codecov Report❌ Patch coverage is
... and 1 file with indirect coverage changes 🚀 New features to boost your workflow:
|
The Estimate Detail block explained how the projection was arrived at and where it can be wrong in a teach box under the figures. The ⓘ on Original Segment Size, Projected Full File and Sampled already carry that, on the figures it bears on, so the prose was a second telling in the one place the reader is reading numbers. The Full Analysis document keeps writing it out, since nobody can hover a saved file. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KDzwviXNsjYHnSVDGCdrxZ
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.
The Compare Quality tab now projects the full file size based on the encoded snippet, showing users how much data the chosen settings would save across the entire video.
Key changes:
sizeEstimate.tswith projection logic that applies the snippet's compression ratio to the source file's total size, accounting for both video sample data (when available) and non-video overheadsavingsPanel.tsUI components: a headline strip showing the direction and magnitude of change, two bars on a shared scale comparing original vs. projected file size, and a detail block with the underlying numbersThe projection uses a ratio (encoded snippet ÷ same stretch of source) rather than simple multiplication, so a snippet from a busy scene is automatically corrected by dividing by an equally busy original, making the estimate more representative of the file's average compression.
https://claude.ai/code/session_01KDzwviXNsjYHnSVDGCdrxZ