Motion

In plain words: Atelier: animation and video

Designed 3 min read 7 glossary terms 8 connected pages
The short version written for the Snayu team

How Atelier handles moving visuals: animation, transitions, camera moves and generated video, typically from an accepted first frame through video generation to a reviewed sequence.

Why read it: Read when working on image-to-video pipelines, music-synced visuals, or video models that also return sound.
  1. 1A finished still can end the job; later animation starts a new job using the kept image.
  2. 2Sound returned by a video model needs its own owner declared beforehand; undeclared sound is quarantined.
  3. 3Review covers the whole duration: seams, flicker, continuity and timing, not single frames.

Words on this page, decoded click one for its card

The original text Underlined words open their plain-English card.

The first frame has been chosen. Motion asks what should change, over which timebase, and how the director will recognize a finished sequence. Its material includes animation, transitions, camera movement, loops, and generated or authored visual sequences.

PrismVision & Media's Video supplies pixel effects; Kinesis supplies structured motion recovery, generation, retargeting, cleanup, synchronization, and conversion. Atelier keeps choreography, visual direction, review, and acceptance across those replaceable tools. Music, sound design, final audiovisual editing, and public rendering retain separate owners.

Progressive visual depth

The commission declares an accepted still, accepted motion, or sealed package as the requested finish. atelier.build_visual_package@3 may contain exact image, review, motion, probe, and package placements branching on that typed policy. Alternatively, a completed image becomes immutable input to a new atelier.forge_visual_sequence@3 InvocationJob Request.

A path through motion to a sealed package is:

brief + target profiles + language policy
→ ImageJob@2 generate or edit
→ review and select exact first frame
→ optional second boundary image
→ VideoJob@2 i2v or first_last
→ temporal probe and visual review
→ VisualAssetBundle@1

At a requested still boundary, success is terminal. A declared review Gate or hardware transition may enter StasisPause while something remains outstanding; future animation alone is no reason to keep the completed RunJob Record open.

The ScrollWorkflow Version names Image and Video SpellStep contracts. Its exact Resolution Lock may bind Qwen Image and an LTX-2.5 Comfy preset, other local profiles, or separately admitted PortalCloud Model implementations. This is an illustrative binding, not a delivery claim. PrismVision & Media's prompt-translation record preserves original/model-facing texts, translator revision, and loss; an imported Comfy graph is no portable ScrollWorkflow Version or global Translation service.

Clips and cues

atelier.forge_animation_set@1 binds clips to exact assets and Form rigs, plus Kinesis motion revisions when used. atelier.forge_visual_sequence@3 binds frame rate, duration, aspect, continuity, and transitions. Exports retain source revisions, tools, transforms, timeline, probes, and checksum.

A Riffmaw MusicCueMap@1 offers musical events, windows, intensity, and transitions. The director chooses their visual answer without editing the musical map. Audio conditioning likewise requires an exact admitted reference.

A video attempt may also produce sound, so its owners must be known before execution. Before a VideoJob@2, MediaFacetAuthoritySet@1 must declare the visual role, atelier.studio revision 5, and exact commission request digest. Any sound role needs separate authority.

After production, Atelier issues its own SemanticFacetAdmissionReceipt@1 for the visual facet, keeping the compound PrismVision & Media parent attached. Riffmaw, Language Edition, Broadcast, or Foundry separately admits declared music, timed-language, picture-sound, or world-sound facets. Undeclared sound is quarantined/deleted. When streams are inseparable, refusal by any required owner prevents use of the compound.

Those judgments may concern one joint model attempt with a shared timebase. They require neither duplicate generation nor a separate screen for each role; Vision keeps the single technical parent and each facet's admission explicit.

Review the movement

Check the sequence duration against the target, then review across that full duration: seams, ordering, camera continuity, clipping, flicker/accessibility hazards, and export stability can fail between otherwise acceptable frames. A bounded correction makes a successor revision. A wrong timebase, stale assets, unsupported profile, or ambiguous synchronization returns findings or refusal.

Package receives accepted motion as visual material. Broadcast owns its final placement, trim, retime, transitions, captions, sound relation, and claims. Foundry owns engine import/runtime behavior. A pinned FFmpeg or other deterministic renderer may serve either office without deciding the creative sequence or final cut.