Files
hyperframes/packages/engine
Miguel Angel Simon Sierra d302bc0f44 fix(audio): carry authoring gain above unity into preview and render
`HTMLMediaElement.volume` is spec-clamped to [0,1], so both timeline probes
lost a clip's authored gain the moment it also carried a fade: the probe
seeded the element at the clamped value and every sample read back at or
below 0 dB, and the mixer prefers probed keyframes over the static volume.
Both probes now shadow the accessor for their own duration and forward the
clamped value to the native setter, so the authored gain survives while
nothing outside the probe ever sees an illegal volume.

Measured on one 6 s composition, first 4 s: unity -32.8 LUFS, boosted -27.0,
boosted-with-fade -32.8 before and -27.0 after — +5.8 dB, exactly the gain
the clip was authored at.

Collapse the other owners of the same decision, each of which kept preview
and render disagreeing on their own: the Web Audio master gain had two
writers, so unmuting discarded the user's volume; the user's volume was
applied twice, once per clip and once on the master; and the control bridge
wrote `el.volume` for clips the transport already owned, which the next tick
read back as the clip's author gain. `<video data-has-audio>` is never
scheduled as a buffer source, so it now routes through a media-element gain
node — but only while the audio context is running, since routing into a
suspended graph would silence audio the native path is playing.
2026-08-17 14:19:31 -04:00
..
2026-08-14 10:21:26 -04: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