The curious player of Benjamin Button: reverse video on the web
summary
A web player is actually built that decodes and renders frames manually using WebCodecs and a custom baby video element to achieve reverse playback; it must buffer and decode whole GOPs, keep at least two GOPs fully decoded to avoid stutter, and copy frames out of GPU memory which pressures RAM on phones. Audio is handled via Web Audio with scheduled audio buffers (some crackle), the reverse rendering works but has performance and memory tradeoffs.
AI-written summary · about
related talks
50m“The Upside Down” of the web, Video
24mVideo Editing in the Browser
43mUsing a modern web to recreate 1980S horribly slow and loud loading screens
33mogv.js: Rebuilding the Web Video Stack From Scratch in JS
28mPreserving and Delivering Retro Game Footage for Modern Viewers with JS and WebGL
27mVideo Editing in the Browser
26mBinary Data Adventures in Browser JavaScript
19mUser-friendly video playback on the web