Membrane Framework: Bringing BEAM into multimedia
summary
Membrane Framework brings media pipelines to the BEAM by modeling GStreamer-style elements-as-processes where each element runs as an OTP process, links by typed pads, and passes buffers that can be binaries or GPU pointers. It ships with native helpers (bound_x and unifix), runs in production for about two years, powers real-time MP3 transcoding embedded in Phoenix, and targets features like backpressure, event/notification semantics and clock sync; not C‑level fast but horizontally scalable and already used in radio and multi‑party video (clients up to ~16–22) projects.
AI-written summary · about
chapters (5)
- 0:00Start
- 4:10CHAPTER 2 WHAT IS THE PROBLEM?
- 14:50ABSTRACTION LAYER
- 23:41MEMBRANE CORE
- 25:37SUPPLEMENTARY LIBRARIES
related talks
33mMembrane Framework - the true story of (...)
28mConcurrency, Functional Paradigm and Dynamic Flow Control in Multimedia Processing
48mGetting to Know the Erlang Virtual Machine, the BEAM
27mMembrane SFU: Bringing WebRTC to Elixir
26mseL4 and BEAM: A match made in Erlang
25mHow we built Algora.TV (livestreaming for developers) using Membrane and Elixir
45m12 years supporting Software Architecture teaching with BEAMs
28mPipelining WebRTC videoconferences in Elixir with Membrane Framework