HyperFrames 0.9: a breaking cloud-render change, plus a weekend of fixes
HeyGen shipped 15 HyperFrames releases between Friday night and Monday morning, going from v0.8.223 to v0.9.5. The version bump marks a breaking change for anyone running distributed renders on AWS Lambda or Cloud Run. Most of the rest are quality-of-life fixes you'll notice in exports.
The breaking part. v0.9.0 (Nov 1, 10:41 PM MST) makes distributed rendering on Lambda and Cloud Run Plan v2 only. Per the release notes, you need to upgrade the SDK and your deployed render stack together and redeploy. Remove the planProtocol option (passing "v1" now throws an error). v1 plan events are rejected with PLAN_PROTOCOL_UNSUPPORTED. The old producer exports are gone, so move to planV2, planV2WithPublisher or publishPlanV2FromExecutionPlan. v0.9.1 made a Lambda state machine without a PlanProtocol setting default to v2. If you only render locally or in Studio, this doesn't affect you.
What else landed. v0.8.224 lets paid HyperFrames plans render final cuts in the cloud at the composition's own frame rate and high quality, and Studio can now download exports over 2 GiB. v0.8.228 switches to peak-only limiting, so one loud moment no longer turns down the whole export, and the render warns you when it has to lower the mix. v0.8.229 makes CLI sign-in wait up to 60 minutes. v0.8.230-231 added remappable shortcuts and a HYPERFRAMES_CACHE_DIR setting, and let Three.js and Lottie load from the parent page. v0.8.223 added reverse video on the HyperFrames plan.
Fixes worth knowing. Nested clips no longer drop frames (v0.8.225). check and snapshot use about half the memory, and older NVENC builds work again (v0.8.227). A scene that has ended releases its WebGL context, and lighter proxy copies are made ahead of time (v0.9.2). Snapshots now fail instead of rendering black or stale video frames (v0.9.4). Renders no longer release WebGL too early and stop outright if every composition script fails, rather than exporting a broken file (v0.9.5, Nov 2, 9:48 AM MST).
Our take: if you deploy HyperFrames' Lambda or Cloud Run renderer, pin your version until you can upgrade both sides at once, because a half-upgrade will reject jobs. Everyone else gets a good update. The loudness fix and the fail-instead-of-black snapshot change remove two of the most annoying ways an agent-made video comes out wrong without anyone noticing.
Related tools on ReelStack
Skills & repos in our directory
- HyperFrames skills · Skill, Code-to-video engine
More from the Lab
- Remotion 4.0.540: WebGPU for every effect, film burn and weather
- Code2Video-AA ranks 27 models on writing videos in code: Claude Opus 5.5 leads, GPT-6.1 Sol is the value pick
- Code-video engines this week: Remotion adds shatter() and curves(), HyperFrames gets GIF export and a Windows app
- Framefields: code-first video for agents that renders on the GPU, with no headless Chrome
Topics: HyperFrames