Split Rendering TV Applications Using WASM

on YouTube ↗31m

" summary

BBC R&D builds a prototype that runs the same Rust wasm32-unknown no_std module in-browser and on server-side Wasmtime, using WebGL/TypeScript in TVs and SDL/OpenGL + GStreamer on Linux with an Nvidia A40 in the cloud. Input travels over WebRTC libdatachannel, frames use a zero-copy GPU→encoder pipeline, and end-to-end tests show a 230 ms max latency with ~50–55 ms attributed to frame capture/encode/network; prototype meets smooth 30–60fps UX.

AI-written summary · about

" chapters (12)

1. 0:00BBC R&D and split rendering
2. 3:11TV device ecosystem challenges
3. 7:41Why split rendering with WASM
4. 10:11Prototype architecture for universal access
5. 13:21Performance and latency analysis
6. 16:10WebAssembly standards and API needs
7. 19:22Personalized TV experiences and limits
8. 21:31Q&A on server and latency
9. 24:19Accessibility in WASM TV apps
10. 27:06Non-WASM devices and browser limits
11. 29:14Browser-bound WebAssembly and runtime alternatives
12. 30:38Closing remarks

" related talks

• 27mWebAssembly for Performant InteractivityMani Nilchiani · EmpireJS 2018
• 47mRewrite the web with Rust and Web AssemblyGeoffroy Couprie · Voxxed Days Luxembourg 2018
• 24mVideo Editing in the BrowserChristopher Chedeau · React Summit 2023
• 02h 58mWebassembly: Expectation vs. RealityPatrick Walther · JSConf.Asia 2019
• 12mExploring Video Editing in the BrowserLuke McGartland · Demuxed 2023
• 25mLessons in WebAssembly: Client Side Video EditingMegan Slater · CascadiaJS 2018
• 41mLet's build with WebAssembly!Tejas Kumar · JSCamp Romania 2019
• 37mBeyond the browser: Moving forward with a more Declarative Future with WebAssemblyShivay Lamba · XtremeJS 2023