CreatorMotion · Funnel Absorption

Make a many-to-one transformation visible by moving scattered inputs into one funnel. Illustrated source nodes shrink and disappear toward a named processor; a large result and recipient follow below it. This 6.5-second shot is a visual explanation of a process you describe, not a tool that analyzes the inputs or produces the claimed outcome.

What you get

  • A local generator, editable HyperFrames shot and motion/review instructions for a 1920×1080, 30 fps segment. Generate the scene from your content and chosen visual material, then render the animation.
  • Up to seven inputs, processor, result and recipient labels. Bundled input-image-1 through input-image-7 and output-image raster slots supply the illustrated sources and processor material; named local replacements are supported.
  • A scattered input field and enclosing funnel, a processor entrance at 1.13 seconds, staggered absorption beginning at 1.40 seconds, a result from 2.65 seconds and recipient from 3.35 seconds. Physical convergence and disappearance are the defining motion, rather than static connecting lines.
  • Four styles keep the same data and choreography: White & Yellow (white-yellow), Charcoal & Lime (charcoal-lime), Paper & Orange (paper-orange), and Black & White (midnight-ice). Semantic style overrides are supported; check contrast after changing them. Dark canvases use a fine grid. Local fonts include Inter, IBM Plex Mono for measurements and ordinals, Smiley Sans and Noto Sans SC. Chinese text selects Smiley Sans automatically, including accompanying Latin text; --zh-font noto-sans-sc selects Noto Sans SC, while --font takes precedence for a supplied font.

Before you choose

Name the real processing step, not just an attractive outcome. The disappearing nodes explain a transformation metaphor; they do not demonstrate measured filtering, information retention or successful analysis.

Good fit

  • A creator illustrating how several source types are filtered or synthesized into one clearly described outcome.
  • A short teaching passage where the audience should see a transition from many inputs to one result.
  • A series using consistent source imagery, funnel geometry and result/recipient typography.

Not for

  • Actually processing source files, automatically filtering ideas, generating the result or validating its accuracy.
  • A quantitative conversion funnel, measured loss rates or a claim that shrinking nodes demonstrates real compression efficiency.
  • Automatic editing of a full film, invented presenter footage or soundtrack, or copying another creator’s identity and source material.

How to use

You say/creatormotion-diagram-funnel-absorption Turn my supplied explanation into a white-yellow B-roll scene using the Funnel Absorption effect. Use the text, data and media I provide, and ask for any required input that is missing.
  1. Prepare up to seven input labels plus processor, result and recipient. Keep the processing claim grounded in the workflow you are explaining; the result is independent supplied text. Extra inputs beyond seven are not shown.

  2. Choose imagery for each active input and the processor. The complete slot map supplies input-image-1 through input-image-7 plus output-image, even though the guide’s shorter slot list mentions only the first five. Reuse those defaults for an illustrative example or replace named slots through --images MAP.json; relative paths resolve beside that file.

  3. Keep source names short and match images to their meaning. Required image helpers have no silent placeholder fallback. Follow the image policy and distinguish generated illustrations from factual evidence; no presenter clip or matte is used.

  4. 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.

  5. 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. Inspect node paths, shrinking/fading and the processor, result and recipient in actual MP4 frames. With seven inputs, the last absorption overlaps the fixed result entrance slightly; review that handoff and adjust timing if your explanation needs all inputs gone first. Keep supporting text at least 24 px and preserve the many-to-one movement.

Requirements and costs

You bring
inputs: provide your own content or retain the illustrative default. · processor: provide your own content or retain the illustrative default. · result: provide your own content or retain the illustrative default. · recipient: provide your own content or retain the illustrative default.
Dependencies
HyperFrames CLI 0.8.30 or compatible — required · Node.js 22 or newer — required · FFmpeg — required
Outside costs
Not collected yet
Tools used
HyperFrames
Publisher testing
v1.0.1 — Claude Code / Claude Desktop / Cowork / Codex / ChatGPT

FAQ

User reviews

—0 reviews

Select a star to share your experience.

No reviews yet. Ratings appear once readers share real experiences.

Similar Skills

View all skills