HyperFrames v0.8.184
By Steven Van ·
Cloud render handles media far above the upload limit, multi-worker mp4 renders encode while capturing, and Lambda chunks use five capture browsers.
Cloud rendering in HyperFrames now accepts projects whose media is far larger than the project upload limit. The change is in v0.8.184, along with render speed-ups and several fixes.
Large media in cloud render
The CLI's cloud render now uploads media files of 5 MB or more as hosted assets before it zips the project. Projects with media far above the upload limit render with no manual step. Uploads are cached, so a re-render sends only new or changed media.
Performance
- A multi-worker mp4 render starts encoding while frames are still being captured, instead of afterwards. The output is byte-identical.
- On AWS Lambda, each chunk renders with as many capture browsers as the function can host: five instead of three on a 10 GB function. Heavy 4K chunks finish sooner.
- A heavy project's first preview page builds sooner, because styles are no longer rescanned once per composition variable.
- A page build reads fonts, inlined assets and scenes mounted many times only once. An offline build with a warm font cache makes no network request.
Fixes
- A transparent VP8 or VP9 webm, such as remove-background output, keeps its transparency in the preview copy made by check, Studio and publish.
- A color-graded image renders graded in snapshot and render when it is hidden as its scene starts and revealed later.
- A preview refused inside a host app no longer stops other Chrome processes left behind by earlier runs.
Internal changes
The release adds the building blocks of capture motion blur: element poses, finding fast movers and the per-frame draw. Nothing uses them yet. It also fixes flaky capture network tests on CI, keeps the log of a hung Windows test run, and has commit hooks lint .mjs and .cjs files.