migrating-to-forward-frames
Migrating to forwardFrames
Overview
forwardFrames pushes a bridge's paint frames to any renderer WebContents as zero-copy GPU handles — full resolution, paint-rate, no readback. It replaces CPU preview paths (capturePage polling, bitmap IPC) with one registration per source.
Prerequisites: Electron 40+, and a @napolab/texture-bridge-renderer version that ships TextureBridge.forwardFrames (check bridge.forwardFrames exists in your installed node_modules types before starting; upgrade if not).
Path A: capturePage preview → forwardFrames
Applies when sources are TextureBridge instances and previews poll capturePage (or IPC bitmaps from paint events).
Delete: the capture timer, the bitmap IPC channel (send + ipcRenderer.on + putImageData/drawImage of bitmaps), and any downscale logic — receivers draw the full-resolution VideoFrame scaled by canvas.
Add (sender, main process): one line per source: