Feature request: Support browser-side video export with Mediabunny

[HereOrCode]

Problem

Could HyperFrames support exporting videos directly in the browser using Mediabunny?

Proposed solution

Mediabunny can write MP4/WebM in the browser. It could provide an optional browser-side export path, while the existing FFmpeg-based renderer remains the default for full production renders.

Alternatives considered

No response

Additional context

No response

[jrusso1020]

@HereOrCode we would love to hear more about the context and reason behind this ask if you can provide more details!

[HereOrCode]

@jrusso1020

Thanks for the quick response!

The context is that I’m exploring a browser-first HyperFrames workflow:

1. Render and preview a HyperFrames index.html in the browser with @hyperframes/player
2. Export a downloadable video directly from the browser when possible

The main reason for asking about Mediabunny is that FFmpeg-based rendering usually requires a heavier server environment, while Mediabunny could potentially provide a lighter browser-side export path for supported formats like WebM/MP4.

I don’t think Mediabunny needs to replace the existing FFmpeg renderer. FFmpeg should probably remain the default production renderer. I’m more interested in whether HyperFrames could expose an optional browser export path, or a lower-level frame capture API that could be connected to Mediabunny.

For example, something like:

const frame = await player.captureFrame(time);

Then the app could pass those frames to Mediabunny for encoding/muxing in the browser.

So the request is mainly about enabling lightweight browser-side export for simpler/draft use cases, while keeping the current FFmpeg renderer for full-quality production renders.

[Larceniii]

MediaBunny might solve a problem for me where Hermes is using heygen in a docker container and cannot use the superior cpu/gpu on my main machine. Having it as an option might be very useful, esp when waiting 10 mins to render 30 seconds on a tiny docker container