Preparing and routing the VJ video signal chain

The whole task here is the unglamorous half of VJing that decides whether a club set survives contact with reality: getting signal from source to projector, with media that plays back smoothly and a fallback when the laptop chokes. Picture a warehouse techno night — visuals feeding a projector from a laptop running Resolume plus a second app for generative layers. Everything in this module is what happens before the first beat drops.

The scaffolding arc starts on paper. First map your rig against the five functional roles — Source, Playback, Mixing, Effects, Output — and place a hardware mixer in the chain as crash insurance, so a software freeze never means a black screen. Next, media prep with training wheels: transcode a single clip, leaning on “video must be compressed to appropriate codecs before a live performance” for the why, then the HAP atoms for the how — GPU decompression buys CPU headroom, but the bandwidth tradeoff means the clip pack lives on an SSD, and variant selection (plain Hap for backgrounds, Hap Alpha for overlay logos, Hap Q where colour matters) is decided per clip. Then wire two apps together with Spout or Syphon depending on your OS, and split your screens so the audience sees the output while you watch the interface. The capstone repeats this whole sequence unsupported, on a full clip pack.

Every required atom gates the capstone: you cannot diagram the chain without the five-role taxonomy and the mixer-as-insurance rationale, cannot transcode intelligently without the codec and HAP tradeoffs, cannot wire or monitor without the inter-app and dual-screen concepts. The supporting atoms enrich the picture — how the move off broadcast standards freed resolution choices, and where performance software sits in the wider tool landscape — useful context, but the capstone stands without them.