mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-11-16 06:19:21 +00:00
`threeDProjection` runs a depth test — `gl.enable(gl.DEPTH_TEST)` with `clearDepth(1)` and `depthFunc(LEQUAL)` — but the comparison was inverted. CSS puts +z toward the viewer, GL treats larger ndc z as FARTHER, and the ndc matrix passed CSS z through with a POSITIVE scale. So the nearest quad received the largest depth, lost the test, and was occluded by the quad behind it. The y-flip on the row above changes handedness. That had already been compensated for winding (`frontFace(gl.CW)`) but never for depth, so it only surfaced once two quads in one context could be visible simultaneously — a single-quad context has nothing to lose a depth test against, which is why it went unnoticed. Negating the z row fixes it at source. Measured on two planes at ±45° in one preserve-3d context, drawElement vs a screenshot render of the same comp: 18.8 dB -> 51.2 dB (visually identical to the screenshot arm) Single-quad cases are unchanged: backface flip card at rest 54.5 dB, perspective+rotationX 51.1 dB, matrix3d 49.5 dB. Not unit-testable: `initThreeDProjectionInPage` is contractually self-contained (shipped into the page via page.evaluate, no outer-scope references), so the matrix is unreachable from a test without breaking that. Verified at render level; the rationale and method are recorded at the call site. Note the self-verify net cannot catch a regression here — it captures ground truth AFTER this rewrite, so it would compare wrong geometry against wrong geometry. Refs PRINFRA-486
@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