CreatorMotion · Pipeline to Packaged Result

Prepare stages, outputs, system and outcome. The scene shows the first three stages and first three outputs. Distinguish intermediate outputs from the external outcome so the enclosing boundary explains something useful rather than simply repeating the same promise.

Reuse the bundled source-N images for an illustrative example or replace active slots through --images MAP.json. Relative paths resolve beside the map; unnamed defaults remain. Every active stage paper requires a raster. Follow the image policy and ensure the material matches the stage label.

Keep stage, output and system wording concise. The default three-stage layout has fixed stage positions and a fixed fan-out origin; if using fewer stages, inspect their apparent connection to the outputs. No presenter or alpha matte is used, and adding extra stages in JSON does not expand the supported layout.

From the extracted package, prepare Node.js 22+, FFmpeg and HyperFrames CLI 0.8.30. Run node scripts/create.mjs --out PROJECT --data CONTENT.json --style white-yellow, substituting another documented palette if wanted. Read the motion specification and image policy before adapting the scene; use semantic --overrides for deliberate style changes.

Inspect the editable project at entry, each motion handoff and final hold, then render with the command printed by the generator. Check the resulting frames for text collisions, correct numbers and readable contrast. Keep at least 1.2 seconds for the final reading when editing, and compare all four palettes with identical content after structural changes. Narration, music and assembly into a longer film remain separate work. Review stage arrivals, output fan-out, group scaling, enclosure and external outcome in actual MP4 frames. Keep source-to-output continuity intact and supporting text at least 24 px. Check the small enclosed labels as well as the large final outcome; a readable wide frame matters more than the success of the generation command.