How do I avoid a strawman before-state?

Write one content object first and let both renderers consume the same data. Build the old renderer according to its real conventions, then ask an uninvolved viewer to assess the result. Equal data is necessary, but a deliberately incompetent renderer would still make the comparison unfair.

Why leave the wrong-format beat still?

For the guide’s web-to-time-based example, that inertia demonstrates the mismatch: the output may be correct as a page but do nothing useful over time. A hold lasting a few seconds, withheld spotlight and reduced music expose that issue. Adding animation merely to make the beat attractive can erase the comparison.

Can I name the source format?

Yes. Formats are named plainly, often as monospaced file labels, and their intended purpose is explained accurately. The workflow avoids naming a competing company because its argument is about medium fit rather than brand quality.

What should stay equal between the two outputs?

The words, numbers and brand values. Only the rendering conventions should differ. Do not give the “after” a better example, shorter copy or stronger data and attribute the whole improvement to a format change.

What if viewers only say the after-state is prettier?

The comparison is not yet proving the intended claim. Identify the functional medium difference they should see or choose another story structure. More labels asserting superiority do not fix an invisible mismatch.

Format-Shift Argument Film

Previews from the publisher

Show why a format designed for one medium can fail in another. Format-Shift builds its argument from the same content rendered twice, once under each format’s real conventions. The contrast should be visible without a caption telling viewers what to dislike, keeping the launch focused on fit between format and medium rather than a competitor attack.

What you get

A production method for a twenty-four-to-thirty-two-second, 1920×1080, 30 fps H.264/AAC film using a near-black canvas, one electric accent and monospaced format labels.
A controlled comparison structure: one content object containing the same strings, values and brand data feeds two independent renderers. Each renderer implements its own convention list without receiving better material than the other.
An eight-beat argument covering source format, its intended purpose, the old-format result, diagnosis, new format, new result, a parallel summary and lockup. The intentionally inert comparison beat withholds spotlight and drops the music to expose the medium mismatch.
Guide and blueprint references for authoring an editable HyperFrames project with per-beat compositions, shared input data, renderers, storyboard, cut ledger and stylesheet. Those production artifacts and the MP4 must be created; they are not included as a finished demo.

Before you choose

Choose this only after a fair same-input comparison produces an obvious medium-level difference. Prototype the two renderers first and ask what changed beyond appearance. If the answer is clear, the surrounding film can point to that evidence instead of carrying the entire argument in slogans.

Good fit

A product translating between formats where the source was designed for a genuinely different medium.
A comparison whose mismatch is directly visible rather than only marginal or dependent on explanatory labels.
A team willing to show the old format competently and acknowledge what it was designed to do well.

Not for

A capability addition with no format translation to compare.
A difference that is merely cosmetic or requires a caption to explain why the “before” is wrong.
A named-competitor attack. The documented argument addresses a format and its assumptions, not a company.

How to use

You say

/hyperframes-format-shift-launch People feed us their web design spec and the video comes out looking like a webpage. We convert it now — make the film.

Name the source format and target medium and write a fair account of the source’s original purpose. Gather one real content object and list the conventions each renderer should apply; keep the brand values and strings identical.
Prepare HyperFrames CLI, Node.js 22 or newer and FFmpeg and locate the referenced motion/audio guidance. Build both renderers before framing beats so the comparison itself can be reviewed without a persuasive soundtrack.
Check the old-format result as a competent implementation, not a deliberately poor one. Ask a viewer who did not build it what fails in the target medium. If the mismatch is not visible without prompting, reconsider the format rather than decorating the criticism.
Write the storyboard and cut ledger around the verified comparison. Preserve the short inert hold in the “before,” withholding spotlight and reducing music as the guide describes. Keep the two comparison beats when trimming; shorten the surrounding setup instead.
Inspect the two outputs side by side for equal content and genuinely different medium logic. Review the complete film at speed, run documented lint/check and output verification and record both convention lists and the shared input with the project. Check dimensions, duration, frame rate and audio as applicable.

Requirements and costs

You bring: The source format and the target medium, both named plainly · What the source format was actually designed for · One content object: real strings and brand values, used by both renderers · The conventions each format implies, as two lists · A near-black canvas colour and one electric accent
Dependencies: HyperFrames CLI — required · Node.js 22 or newer — required · FFmpeg — required
Outside costs: Not collected yet
Tools used: HyperFrames
Publisher testing: v1.0.0 — Claude Code / Claude Desktop / Cowork / Codex / ChatGPT