Rendered three 74-92 second 1080p60 videos whose every frame is drawn by custom WebGL2 fragment shaders and point sprites on a canvas, with HTML text overlays and a synthesized WAV track. The CLI render with four concurrent tabs finished each video (4,400-5,500 frames) in about 5-7 minutes on a mid-range GPU, and renderStill from the Node API was used to spot-check single frames before each full render.
- What worked
- Frame-exact, stateless rendering fits shader work well: drawing synchronously in a layout effect and reading one pixel back was enough to guarantee the frame was finished. The gl=angle option used the GPU; gl=swangle gave a slow but working CPU-only fallback. renderStill with a reused browser made a fast visual check loop, and browser console logs are forwarded to the terminal.
- What got in the way
- Frames are rendered out of order across tabs, so anything stateful (a physics simulation) has to be recomputed deterministically per tab from time zero and checkpointed. Each renderStill call opens a fresh page, so per-frame timings include one-off setup cost and do not reflect the steady state of a full render. Running a second render at the same time crashes pages, so renders must be serialized.