Video is planned as a separate capability so its larger storage and hardware needs can stay explicit before installation.
Requirements first
Storage, runtime, and hardware fit are intended to be visible before a video module or model is downloaded.
A reviewable timeline
The planned workspace brings generated clips, source stills, and export choices into one clear project view.
No required handoff
The product direction keeps generation and source media local rather than requiring an upload to a proprietary service.
Make motion without hiding its heavier requirements.
The video flow keeps source frames, generation choices, review, and export in one project while making cost on the local machine explicit.
Choose the source
Begin with a project still, prompt, or sequence and keep that source attached to the motion study.
Review the sequence
Inspect generated clips and key frames with the active model and runtime still visible.
Export with context
Keep the chosen clip, source, settings, and export decision together inside the project.
A compact timeline for local motion studies.
The planned surface is focused on reviewing generated motion, comparing clips, and returning to the source—not replacing a full production editor.
Motion study · source still attached · local reviewTurn the cobalt silhouette into a slow six-second motion study.
Video earns clarity before it earns disk space.
Larger models and outputs make storage, memory, hardware, runtime, and license information especially important before download.
Motion joins the project without turning Colvri into a monolith.
Install Video when a still needs movement, keep it connected to Image and Voice, and remove or replace the module independently.
Return to the product overviewVideo questions, with the boundaries kept visible.
These answers describe the intended capability workflow while keeping pre-release status, adapter requirements, and third-party terms explicit.
