HyperFrames v0.8.207
By Steven Van ·
v0.8.207 adds keyframe interval and peak bitrate settings to renders, makes stalled captures resume, and improves Windows support.
Renders in HyperFrames can now set a keyframe interval and a peak bitrate cap, and a stalled capture resumes instead of failing. The linked commit covers one docs change in v0.8.207, while the release also adds CLI options and fixes for Windows, Mac and the player.
Features
- Capture can route its traffic through an opt-in upstream proxy.
- Setting HYPERFRAMES_NO_PREVIEW_DISCOVERY=1 skips the preview-server scan.
- The CLI writes one diagnostic report when a command stays silent for 60 seconds.
- Renders set a keyframe interval and a peak bitrate cap.
- hyperframes open hands the project to the app on Windows and Linux as well.
- Download links in the docs carry the docs visitor's PostHog id.
Fixes
- On a Mac, renders decode a clip in software when the media engine refuses it.
- In the player, each take plays its own audio when the browser blocks autoplay.
- A video no longer runs ahead of the playhead or past its out-point.
- history show --diff works without git on PATH.
- For a media src whose file name contains # or ?, lint says to write it percent-encoded.
- A stalled BeginFrame capture resumes from the first unwritten frame.
Docs download attribution
The linked commit adds a script, docs/download-attribution.js, to the docs. Studio download links to hyperframes.dev name the visitor's PostHog id (ph_id), so the download is counted under the same person as their docs pageviews. The two sites send to one PostHog project but each domain has its own cookie, so the download site cannot read the docs cookie.
The id is added at click time only, so a copied link never carries it. It is added only when PostHog is running on the page and the visitor has not opted out. A browser-wide "do not track" or Global Privacy Control signal counts as no consent.