Files
hyperframes/packages/engine
Vance Ingalls a0e3a75d0b refactor(engine): one RIFF chunk walk, not two
`readWavChunks` and `parseWavLayout` each carried the same word-aligned
walk. The reason this was left alone before is real — the two are *not*
the same function, and unifying them means picking one behaviour for each
of four differences in the parser every render's audio goes through: one
breaks at the first `data` and returns a slice, the other scans every
chunk and returns offsets; one lets the decoder judge the format, the
other refuses anything but 16-bit PCM.

So only the walk moves. `riffChunks` yields `{ id, body, size }` and holds
no policy at all, both readers keep every one of those four behaviours,
and there is no cycle to route around because it belongs to neither of
them. It lives in engine/services beside both.

It also had no test, in either copy. A real WAV out of the mixer has an
even-sized `fmt ` first and `data` last, so neither of the two things the
walk exists for ever came up: the pad byte after an odd chunk, and not
assuming an ordering. Both mutations survived a full engine run before
`wavChunks.test.ts`; both fail now, as does removing the guard against a
header that runs past a truncated file.

engine services 739 passing / 3 skipped (736 + the 3 new).
2026-08-10 15:38:57 -07:00
..
2026-08-03 22:48:00 -07:00
2026-03-21 22:43:56 -07:00

@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