FLOOD → Spout → Resolume

Program routing updated October 8, 2026. A curated set of published workflows and techniques; no search can guarantee every user post or undocumented trick.

Performance Desk

Open the Performance Desk to trigger patches or local media clips from banks. Each deck has separate camera slots, sound mappings, controls and feedback. Set Deck detail to the desired source quality and Program resolution to the output dimensions, then open Output… for the connected Program window. The desk defaults to720p decks and1080p output; use1080p decks for matching source detail. Higher settings need more GPU.

Store A or Store B then choose a pad to save a complete look. Export banks for backup. Local media files now persist in this browser when storage permits. Workspace and bank JSON files contain settings and references; reattach the original files on a different browser. Cameras require reconnection, and saved audio requires a click to resume. The fifteen program modes preserve clean A/B crossfader endpoints; per-input blends and source mesh mapping live in each deck’s Controls panel.

Playback and tempo

Thumbnail pads identify clips at a glance. Store A/B captures the current picture alongside its settings. Each channel offers playback speed, Forward/Reverse, Play/Pause, Restart, Loop and a position slider. Video reverse uses frame seeking; procedural reverse changes animation time without undoing feedback history. Live sources cannot be rewound.

The optional Clock has tap tempo and a four-beat timeline. It is a visual reference, with no automatic trigger quantization or clip-speed changes. Workspaces retain BPM and restore the clock off.

Dedicated Program through SpoutBrowser

1. Export your current set with Workspaces → Export backup. In SpoutBrowser, open this Performance Desk and import it. Reattach local files and reconnect devices: Chrome and SpoutBrowser keep separate browser storage.
2. Launch the full SpoutBrowser with --off-screen-frame-rate=60 --multi-threaded-message-loop --transparent-painting-enabled --hide-controls, plus --url="https://mpu-anon-hydra-engine.steve-grise.chatgpt.site/mixer" and a persistent --cache-path.
3. Set Program resolution and Deck detail. Open Output…, select 30 or 60 fps, choose an opaque background or preserved transparency, then Open Program Output. This window copies the running mixer's actual picture, including A/B effects, microphone mappings, devices and feedback. It runs no second Hydra engine.
4. Use Fit output window and check the buffer and window dimensions in the desk. Stock SpoutBrowser sends its viewport size, which the monitor work area can limit. A 1920×1080 canvas alone does not guarantee a 1920×1080 Spout feed. Verify the received size in Resolume.
5. In Resolume Avenue Sources, select the SpoutBrowser sender that shows only the Program picture. Stock sender names use the executable name and numeric suffixes; the control window may also be listed. Keep both windows open and unminimized.

The Program rate drives both decks. Actual frame rate still depends on the GPU, patch complexity and host painting. Preserve transparency keeps alpha already generated by a patch; it cannot remove an opaque background. The checkerboard appears only in the desk, never in output. For microphone/camera input, SpoutBrowser's right-click Media handling disabled must be unchecked on the trusted mixer page; that sample handler grants requested media without an origin prompt. The output window requests no devices. Resolume's Spout guide.

Alternative: OBS bridge

1. Run FLOOD at localhost:8770. Select Output → 16:9 and 1080 vertical pixels for 1920×1080. Use Clean preview to hide controls.
2. Capture the Chrome window in OBS, or use an OBS Browser Source for the local studio. A Browser Source is its own browser session: reconnect inputs and load settings there. Set source and OBS output dimensions to match.
3. Install the official OBS Spout2 plugin. Send the full composition through Spout Output, or use Spout Filter to send individual OBS sources. Select the corresponding Spout sender in Resolume Sources. This transport needs a native bridge; Chrome does not directly register a Spout sender.
4. Alternatively use OBS NDI output → Resolume NDI source, following Resolume’s browser/OBS routing guide. Network transport is useful between computers; plugin installation is required in OBS.

Virtual camera and channel control

The patch provides Final, Input 1–3, Red, Green, Blue, and Alpha views plus RGB gains. OBS can capture that selected view and expose it as its virtual camera. In OBS’s camera gear settings choose Program, Preview, Scene, or Source. These select one output feed, rather than creating three independent virtual cameras. OBS official guide.

Chrome canvas captureStream() produces a browser MediaStream. It does not install an operating-system webcam driver; OBS supplies that bridge. For independent native channels, use per-source Spout senders. Virtual webcam alpha should not be relied on: use a key or a native alpha-capable transport and test the receiving chain.

Inputs into Hydra

Start VSeeFace Virtual Camera or OBS Virtual Camera, refresh the MPU camera list, connect a slot, then raise that slot’s alpha. For native Spout feeds use a webcam bridge such as SpoutCam or OBS → OBS Virtual Camera. Images and looped videos can fill the same three slots. File/device connections survive patch switching in the studio but are deliberately not included in saved settings or JavaScript.

Published creator workflows

• David Vandenbogaerde: building HYDRACTRL — firsthand live setup combining Hydra, Resolume, TouchOSC, RESOCTRL, TouchDesigner and MIDI control. Useful ideas: scene recall, one controller for several tools, audio-driven generation and separate post-processing.
• brandon-stargrave / hydra-mcp — community tool advertising native Syphon on macOS and NDI output for integrations including Resolume. A separate project to evaluate, not installed in this studio and not evidence of native Windows Spout output.
• Andrei Jay: video feedback guide — creator explanation of internal feedback, including Hydra. Scale, rotation, decay and masking make feedback controllable; avoid accidental capture of the entire desktop.
• Jose Valverde: audio-reactive GLSL for live VJing — related browser/NDI/Resolume performance account and shader approach. It is a related GLSL workflow, not a drop-in Hydra patch.

Useful techniques built into this studio

• Render resolution and texture sampling are separate. More pixels plus smooth framebuffer sampling reduce jagged enlargement. Deliberate pixelate() effects remain deliberate; low-resolution source footage cannot acquire new detail.
• Three independent input opacity controls and15blend modes, four-corner mapping, bend/twist/perspective, animated mesh displacement, oscillator distortion, color adjustments and optional black keying.
• Map bass, mid, treble or overall level to numerical parameters across patch functions. Signed depth offsets the base control and clamps to its range; multiple mappings can stack. Export preserves the base values and mapping definitions.
• Motion controls and adjustable alternating scan lines. Interlacing is a visual simulation, not a hardware interlaced output format.
• M gives a temporary feedback/block-warp datamosh simulation; R ends it. It does not corrupt an encoded video’s motion vectors. Text fields suppress the hotkeys.
• Resolution changes clear feedback buffers. Start at 1080p/60 target, lower the target rate or resolution if the GPU cannot maintain it. The displayed rate is a target, not a measured benchmark.

Return to MPU studio