mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-10-30 17:27:09 +00:00
James RussoandClaude Opus 5.5
de1ef5a05a
* fix(engine): extract long video ranges in segments and keep plan uploads flowing A distributed render's plan step extracted a whole video in one ffmpeg process, so a long clip hit ffmpegProcessTimeout (300 s) however much of Lambda's 15-minute limit was left, and every frame then uploaded in batches of 16 that each waited for their slowest blob. Ranges longer than two minutes now extract as two-minute segments that run side by side, each numbered after the last. They sample the same absolute times as a single pass, so the frames are byte-identical (checked on a 26-minute, 37,440 frame clip). Plan v2 publishing keeps 32 uploads in flight instead of batching. On a 10 GB Lambda the 26-minute clip's plan step fell from 395 s to 200 s. The Lambda docs now state the plan-step length bound. Fixes #5260 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * fix(engine): split extraction on an integer frame count The split compared and subtracted float seconds, so 200.3 - 80.3 became 120.00000000000001 s: a second segment got `-t 1.42e-14`, which ffmpeg rejects, failing an ordinary two-minute range. The frame count now comes from extractionFrameCountForDuration, the rule a single pass follows, and every segment takes an exact frame count. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@hyperframes/engine
Seekable web-page-to-video rendering engine built on Puppeteer and FFmpeg.
Framework-agnostic: works with GSAP, Lottie, Three.js, CSS animations, or any web content that implements the window.__hf seek protocol.
Install
npm install @hyperframes/engine
Requirements: Node.js >= 22, Chrome/Chromium (auto-downloaded by Puppeteer), FFmpeg
What it does
The engine opens your HTML composition in a headless Chrome instance, seeks frame-by-frame using Chrome's HeadlessExperimental.beginFrame API, captures screenshots, and encodes them into video with FFmpeg.
Key services
| Service | Description |
|---|---|
| browserManager | Launches and pools headless Chrome instances (chrome-headless-shell) |
| frameCapture | Manages capture sessions — seek, screenshot, buffer lifecycle |
| screenshotService | BeginFrame-based capture with CDP (Chrome DevTools Protocol) |
| chunkEncoder | FFmpeg encoding with chunked concat, GPU detection, faststart |
| streamingEncoder | Pipe frames to FFmpeg in real time (no intermediate PNGs on disk) |
| audioMixer | Parse <audio> elements and mix audio tracks via FFmpeg |
| videoFrameExtractor | Extract frames from <video> elements for compositing |
| parallelCoordinator | Split frame ranges across worker processes |
| fileServer | Serve local HTML files to the browser via Hono |
Usage
import {
acquireBrowser,
createCaptureSession,
initializeSession,
captureFrame,
closeCaptureSession,
} from "@hyperframes/engine";
// 1. Launch browser
const browserLease = await acquireBrowser({ captureMode: "beginFrame" });
// 2. Open a capture session
const session = createCaptureSession({
browser: browserLease.browser,
url: "http://localhost:3000/my-composition.html",
width: 1920,
height: 1080,
fps: 30,
});
await initializeSession(session);
// 3. Capture frames
for (let i = 0; i < totalFrames; i++) {
await captureFrame(session, i, `/tmp/frames/frame-${i}.png`);
}
// 4. Clean up
await closeCaptureSession(session);
await browserLease.release();
Most users should use @hyperframes/producer or the hyperframes CLI instead of calling the engine directly.
Documentation
Full documentation: hyperframes.heygen.com/packages/engine
Related packages
@hyperframes/core— types, parsers, frame adapters@hyperframes/producer— high-level render pipeline built on this enginehyperframes— CLI