Problem
Feature Request: Dual-Aspect Export (Responsive Video Output)
Summary
Render a single HyperFrames composition to both 9:16 and 16:9 in one pass, with outputs designed to be swapped at runtime by a web player when a phone rotates — effectively responsive video.
Problem
Video today is locked to one aspect ratio per file. Creators building for both feeds (vertical) and embedded/landscape contexts have to run two separate renders, manually reframing each. There's no first-class way to produce a pair of outputs guaranteed to stay in sync.
Proposed solution
Proposed Behavior
- A composition can define layout per aspect ratio (or auto-reframe with a safe-zone / focal-point hint per scene).
- One render job outputs both files:
myvideo_9x16.mp4 and myvideo_16x9.mp4.
- Both outputs are frame-accurate to each other: identical duration, frame rate, cut points, and a shared audio track — so a player can hot-swap between them at the same timestamp with no drift.
- Optional: a small JSON manifest alongside the renders (durations, resolutions, file paths) so a player component can consume the pair without config.
Requirements for the Output
- Identical timeline: same total duration and scene boundaries in both renders.
- Same audio stream (or bit-identical audio) in both files.
- Matching frame rate and keyframe intervals, so seeking after a swap lands cleanly.
- Consistent color/encode settings between the pair.
Player Side (out of scope, but for context)
A lightweight web player listens for orientation change, swaps the video source, and seeks to currentTime from the previous source. With the sync guarantees above, the swap reads as the video "morphing" between aspects.
Why This Fits HyperFrames
This is the kind of thing Remotion can technically do — because compositions are React code, a live player can re-flow layout on viewport change. But that approach requires client-side rendering, falls apart with heavy AI-generated footage, and taxes the viewer's device. HyperFrames shipping this as baked, synced dual renders delivers the same responsive-video experience with none of the runtime cost — a genuinely better answer to one of Remotion's few real advantages.
Use Case
AI-heavy promo/review video pipelines where the same piece needs to live on vertical social and embedded landscape web players without a second production pass.
Alternatives considered
No response
Additional context
No response
Problem
Feature Request: Dual-Aspect Export (Responsive Video Output)
Summary
Render a single HyperFrames composition to both 9:16 and 16:9 in one pass, with outputs designed to be swapped at runtime by a web player when a phone rotates — effectively responsive video.
Problem
Video today is locked to one aspect ratio per file. Creators building for both feeds (vertical) and embedded/landscape contexts have to run two separate renders, manually reframing each. There's no first-class way to produce a pair of outputs guaranteed to stay in sync.
Proposed solution
Proposed Behavior
myvideo_9x16.mp4andmyvideo_16x9.mp4.Requirements for the Output
Player Side (out of scope, but for context)
A lightweight web player listens for orientation change, swaps the video source, and seeks to
currentTimefrom the previous source. With the sync guarantees above, the swap reads as the video "morphing" between aspects.Why This Fits HyperFrames
This is the kind of thing Remotion can technically do — because compositions are React code, a live player can re-flow layout on viewport change. But that approach requires client-side rendering, falls apart with heavy AI-generated footage, and taxes the viewer's device. HyperFrames shipping this as baked, synced dual renders delivers the same responsive-video experience with none of the runtime cost — a genuinely better answer to one of Remotion's few real advantages.
Use Case
AI-heavy promo/review video pipelines where the same piece needs to live on vertical social and embedded landscape web players without a second production pass.
Alternatives considered
No response
Additional context
No response