u/CompellerAI

Building REACT live: audio-reactive visuals + NDI + OBS + lighting output
▲ 0 r/vjing

Building REACT live: audio-reactive visuals + NDI + OBS + lighting output

I’m building REACT, a live audio-reactive visual/stage system, and wanted to share what we’re working on with people who care about VJ workflows.

The goal is to connect the pieces that usually live in separate worlds:

- realtime audio-reactive visuals
- NDI / OBS live output
- stream workflows for Twitch/Kick/YouTube
- DMX / Art-Net / lighting output
- virtual stage previews before plugging in real fixtures
- eventually deeper DJ hardware awareness

We’re also starting to open-source pieces of the stack here:
https://github.com/compellerai

One area we’re especially excited about is Rust for live performance tooling. The performance matters a lot when visuals, audio analysis, NDI, lighting, and hardware control are all running at the same time.

For anyone dabbling with Rust + DJ/live-show hardware, we’ve been building around Pioneer Pro DJ Link too:
https://crates.io/crates/prodjlink-rs

I’d love feedback from VJs / live visual artists:

What would actually help your workflow?

- tighter OBS/NDI routing?
- lower-latency audio-reactive visuals?
- MIDI / controller mapping?
- DJ hardware sync?
- lighting/DMX preview?
- a way to test stage looks before a show?

Not trying to replace VJs - we’re trying to build tools that make live visuals and stage systems easier to control together.
u/CompellerAI — 14 days ago

Building a live visual + lighting preflight tool around DMX / Art-Net / sACN - looking for practical feedback

I’m working on a live stage system that connects audio-reactive visuals with actual lighting output.

The goal is simple: before someone plugs in a DMX cable, they should be able to see a basic virtual stage preview of what the fixtures are going to do — color, intensity, strobe, movement, hits — then confirm it against real lights.

Current direction:

OLA / DMX / Art-Net / sACN output path,
virtual fixture evaluator for wash, moving head, and simple laser-style fixtures,
2D front-elevation “stage preview” instead of heavy 3D,
fixture patching with universe/start address conflict warnings,
same control path drives both preview and real output,

The thing I’m trying to avoid is making a pretty simulator that lies. I’d rather have a boring preview that accurately shows timing/color/intensity intent.

For people who do real lighting work: what would make this useful vs annoying?

Questions:
- What does a preflight preview absolutely need to show?
- Would 2D front-elevation be enough for setup/design?
- What fixture metadata matters most early: channel map, mode, pan/tilt limits, strobe curve, color model?
- Anything you wish lightweight DMX tools handled better?
reddit.com
u/CompellerAI — 14 days ago