Recapture the gallery: axis fix, and two frames that were never deterministic - #71
Merged
Conversation
#70 moved the y-axis minimum off the time-axis row. The published screenshot still showed the old collision, since the gallery serves committed images rather than rendering live. "$0" now sits on the plot's bottom row and "08-10" has the time axis to itself. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017Df2FNu5DhinMV2soRz3cy
Regenerating the whole gallery showed these two changing on every run,
which I had claimed would not happen without checking. Both were real
defects in the fixtures rather than in the capture:
nixamp anoisesrc defaults to seed=-1, so the analyser was measuring
different noise each time. Seeded upstream.
tsbb the view renders ages through relative(), which compares
against Date.now(). Pinning the fixture timestamps to a fixed
date made the rendered labels drift by an hour every hour.
Anchored to capture time upstream instead.
Two consecutive captures now produce byte-identical files for all nine.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017Df2FNu5DhinMV2soRz3cy
ralyodio
changed the title
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
1 participant
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.
#70 moved the y-axis minimum off the time-axis row. The published screenshot still showed the old collision, because the gallery serves committed images rather than rendering live.
And two frames that were never reproducible
I first claimed the other eight would regenerate byte for byte. That was wrong, and checking it found two real defects — in the fixtures I wrote, not in the capture:
anoisesrcdefaults toseed=-1, so the analyser was measuring different pink noise on every run. The screenshot changed each time. Seeded in nixamp@8c12e52. It is still real audio through the real analyser, just the same real audio each time.relative(), which compares againstDate.now(). Pinning the fixture timestamps to a fixed date meant the rendered labels drifted an hour every hour. Anchored to capture time in tsbb@1ba17f7.Either would have churned the gallery on every regeneration, making a real change impossible to spot in a diff — which is precisely what these frames exist to prevent.
Verified rather than asserted this time
Two consecutive full captures now produce byte-identical files for all nine apps (
md5sumcompared across runs).🤖 Generated with Claude Code
https://claude.ai/code/session_017Df2FNu5DhinMV2soRz3cy