Running a Multi-DJ Remote Broadcast

The whole task here is the community radio dream on a zero-euro budget: several DJs in different cities, one coherent stream, one operator. This is how lockdown-era 48-hour marathons and algorave takeovers actually run — no NDI licenses, no broadcast truck, just a Jitsi room, OBS, and Blender for the graphics polish that makes it look intentional rather than improvised.

You already know how to stream one set with OBS and keep a rig in sync; this module scales that to multiple humans you cannot physically reach. Start supported: with one friend (or a second device), practice the core move from “Multiple remote DJs can be brought into one OBS scene by popping each Jitsi Meet stream into its own window and window-capturing it” — pop out, capture, arrange, switch — until it is automatic, because mid-broadcast is the wrong time to hunt for a window. Then layer in a lower-third built in Blender, leaning on its real-time-friendly side (“Blender is a free, open-source 3D suite…”) rather than heavyweight rendering. Finally, run the full unsupported broadcast and write up your choices through the lens of music-centred design: why your layout, switching, and audio decisions serve performers, audiences, and musical flow rather than generic usability metrics.

The three required atoms gate the capstone directly — you cannot compose the scene, build the rig, or write the reflection without them. The supporting atoms enrich the run: the scene/source model refreshes the compositing mental model from your prereq module, and the noise-suppression misconception is the classic trap that quietly garbles DJ audio — check every music source’s filter chain before you go live.