Repository navigation
prep: export a Framesheet Studio frame template with multi-frame zips - #34
Merged
Merged
Conversation
A frame-sequence export laid out on pages, plotted and photographed can be turned back into a looping animation by Framesheet Studio — but only if it is handed a template SVG that says where each frame sits on the page. The multi-frame zip now carries one: `<base>_frame-template.svg`, page 1 of the export plus a `frame-template` layer holding one `frame-N` rectangle per grid cell, numbered row by row so the numbering is the animation order. Framesheet Studio hides those rectangles and anchors on the surrounding plotted ink, which is why the template is a full page rather than a bare grid: a rectangles-only file leaves the registration search too little to lock onto, and it mis-registered by ~4 mm in testing where the full page lands within 0.2 mm. Off the same code path as the page SVGs, so the geometry cannot drift; the page SVGs themselves are unchanged byte for byte. Toggleable under output layers (multi-frame only, on by default). The shared paper-outline / calibration / page-boundary tail of buildPageSvg moves into registrationLayers along the way. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012nrE3nUsJJQeXnvnxhhCHz
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
2 participants
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.
A frame-sequence export laid out on pages, plotted and photographed can be turned back into a looping animation by Framesheet Studio — but only if it is handed a template SVG that says where each frame sits on the page.
The multi-frame zip now carries one:
<base>_frame-template.svg, page 1 of the export plus aframe-templatelayer holding oneframe-Nrectangle per grid cell, numbered row by row so the numbering is the animation order. Framesheet Studio hides those rectangles and anchors on the surrounding plotted ink, which is why the template is a full page rather than a bare grid: a rectangles-only file leaves the registration search too little to lock onto, and it mis-registered by ~4 mm in testing where the full page lands within 0.2 mm. Off the same code path as the page SVGs, so the geometry cannot drift; the page SVGs themselves are unchanged byte for byte.Toggleable under output layers (multi-frame only, on by default). The shared paper-outline / calibration / page-boundary tail of buildPageSvg moves into registrationLayers along the way.
Claude-Session: https://claude.ai/code/session_012nrE3nUsJJQeXnvnxhhCHz