| title | Product updates |
|---|---|
| description | The HyperFrames changes that matter when you create, edit, and render projects. |
This page explains meaningful product changes in human terms. Use Weekly updates for the detailed digest and films, or the complete release archive for every versioned change.
Studio, published projects, and the render pipeline can prepare compatible preview versions of difficult video formats automatically. This particularly helps with HEVC and other files that a browser may not decode even though FFmpeg can render them.
What this means:
- fewer black video frames in Studio;
- preview and render use consistent media decisions;
- published projects can include the prepared media;
- projects can opt out when automatic proxying is not wanted.
The flatter Studio inspector is now the normal editing surface. Text, layout, style, motion, media, grade, and element-specific controls are easier to scan without navigating several competing panels.
Recent releases improved software-GPU capture, Windows behavior, browser worker reuse, failure diagnostics, audio handling, and composition synchronization.
For most users, the result is simple: fewer cases where a long or media-heavy render stalls or produces a frame that differs from preview.
Storyboard review now has clearer handoff behavior, safer history navigation, and a more explicit relationship between human comments and the next agent pass.
Lint and validation now catch more animation problems involving seek order, hidden initial states, conflicting writers, relative values, and SVG drawing.
Scaffolded projects can pin a HyperFrames version for reproducibility. Ask your agent to check the project before render-affecting work, or run:
npx hyperframes@latest upgrade --project . --checkRead the release archive before upgrading a production workflow with custom integrations.