MRGI MOTION / WORKFLOW FIELD GUIDE
Deliver a short campaign film in multiple formats
Keep every delivery tied to the approved edit and the correct channel recipe.
01 / FROM INPUT TO HANDOFF
Follow the decisions.
This walkthrough describes the intended MRGI product behavior. The browser demo illustrates a small part of the workflow; it does not run the complete application.
- 01
Assemble the sequence
- Start with
- Three fictional shots and a title.
- Work through
- Arrange the timeline and identify the intended narrative.
- Result
- A candidate edit.
- 02
Review the cut
- Start with
- The edit and stakeholder notes.
- Work through
- Resolve notes and select the exact timeline revision for delivery.
- Result
- A reviewed cut snapshot.
- 03
Inspect each format
- Start with
- Landscape and portrait delivery recipes.
- Work through
- Check framing and required presentation elements for each destination.
- Result
- A reviewed set of delivery settings.
- 04
Record the output
- Start with
- The timeline, recipes, and rendered files.
- Work through
- Retain the revision and settings behind each output.
- Result
- A traceable delivery set.
02 / INPUTS & INTERCHANGE
What travels with the work.
These are foundation formats and intended handoff contracts. Support and fidelity must be confirmed for each released build.
| Artifact | Role | Review consideration |
|---|---|---|
| Media sources | Timeline inputs | Codec and hardware support vary and require testing. |
| Timeline interchange | Editing handoff | Effects, timing, and metadata may not round-trip exactly. |
| Rendered outputs | Distribution files | Validate actual codec, dimensions, audio, and playback behavior. |
A deliberate cross-app boundary
Combine Audio production and Flux graphics, then preserve delivery decisions in Evidence.
The intended handoff should identify the selected resource, its version, the destination, and the user’s authorization. A linked application should not inherit unrestricted file access.
Explore the connected applications ↗03 / BOUNDARIES & READINESS
Know what this example establishes.
- The browser lab contains no actual media decoding.
- A format preset does not guarantee platform acceptance.
- Complex effect and codec reproducibility requires pinned dependencies.
Development status
The source foundation is imported. Delivery governance, version comparisons, and the redesigned editor are planned.
Before a production release
Validate real-file behavior and platform support, implement the stated authorization and review rules, and document the tested acceptance scope. The interactive website is a product demonstration, not a release candidate for the application.
04 / PRODUCT QUESTIONS
The details that matter.
Does changing aspect ratio guarantee a good crop?
No. The recipe can prepare the framing, but subject visibility, captions, and composition still need review.
Can I compare real edits here?
The lab only scrubs a synthetic sequence. Production timeline comparison is part of the proposed product work.
Open-source foundation
Multitrack timelines, effects, audio mixing, and codec/interchange crates exist in FilmCraft. Review-bound delivery packages are the proposed MRGI focus. Read the credits and foundation mapping.
Keep exploring Motion.
Return to the product breakdown or try the local interactive example.