HyperFrames v0.8.174
By Steven Van ·
The CLI's timeline delete now cuts only the chosen range, and Lambda renders assemble in seconds and scale to account concurrency limits.
Deleting a time range from a timeline clip in HyperFrames now removes only that range instead of the whole clip. The change is part of v0.8.174, which also speeds up cloud renders and adds a batch of fixes.
Timeline delete
The CLI's timeline delete command with --start and --end now cuts just the range given. Before, it removed the whole clip.
Cloud and Lambda renders
- Cloud renders download faster, and chunk output is assembled with a single faststart index.
- Lambda renders assemble in seconds.
- Distributed Lambda renders are sized from the account's concurrency limits, so they scale to those limits.
Other fixes
- Color grading now applies to canvas compositions.
- Exports carry full colour tags with every encoder, for both SDR and HDR.
- A page-load timeout names the script or stylesheet the page was waiting on.
- Capture keeps other screenshots when Chrome refuses one.
- A render that no FFmpeg encoder can finish stops before capture, not after it.
- Back-to-back audio clips no longer count as overlapping in lint after float rounding.
- Preview inside a host app's agent run no longer outlives the run.
- init writes the project into a folder with a non-ASCII name on Windows.
- Generated artifacts are formatted without spawning bun from PATH.
Capture and proxies
The linked docs commit adds a note to the CLI documentation: capture needs direct internet access. Since 0.8.164 it does not use HTTPS_PROXY or HTTP_PROXY, because its own proxy dials each checked public address itself. Where the only way out is a proxy, as in some sandboxes and corporate networks, every page fails with net::ERR_TUNNEL_CONNECTION_FAILED, even though curl reaches the same site through that proxy.