HyperFrames v0.8.188
By Steven Van ·
Lambda renders default to cheaper arm64 video work, with a flag to keep x86, plus fixes for long renders, odd folder names and console-shadowing scripts.
Lambda cloud renders in HyperFrames now run their video work on arm64 by default, which costs less per render. Passing --video-arch x86_64 keeps x86. The change is part of v0.8.188, which also includes several render fixes.
Arm64 on AWS Lambda
- The CLI deploys Lambda renders on arm64 by default. --video-arch x86_64 keeps x86.
- Chunks can run on an optional arm64 image function.
- The arm64 video function image is built from the handler ZIP and attached to releases, where it is pinned.
- A prebuilt image can be pushed to ECR without Docker.
- The arm64 image staging script is kept out of the published package.
Render fixes
- Long renders with small frames no longer fail the up-front disk estimate.
- A composition script that shadows console no longer breaks the render runtime.
- A blank media src is now treated as no source, rather than as the page itself.
- Local renders from the CLI keep page motion blur off.
- Renders in folders with a percent sign in the path are fixed. The release also lists fixes for motion blur, audio timing and frame handling.
HyperFrames
Open-source framework for rendering HTML compositions into MP4 videos, built for AI agents and automated pipelines.
View HyperFrames →