XOSC

XOSC turns whatever the operating system reports — a key on a USB keypad, MIDI Note 60 on channel 1, button 9 on a generic gamepad, an RFID badge tap arriving as a keyboard burst, an ASCII line coming out of an Arduino at 115 200 baud, or an incoming OSC or Art-Net packet — into whatever the show needs: an OSC message, a DMX universe, a serial command, or a video cue on a second monitor. Designed around Resolume Arena; works with anything that speaks the protocols. One window, no daemons, no service to install.

The input matrix

• Keyboard — any key code with modifier capture. Discrete trigger, plus ASCII string payload for receivers that want the raw key name.
• MIDI via Web MIDI — Note On/Off, CC, Pitch Bend, Program Change. Channel and note number forward as OSC args; CC numbers fan out to addressable output nodes.
• Gamepad via the HTML5 Gamepad API, polled at 60 Hz. Buttons fire discrete triggers; axes forward raw floats. Up to four pads addressable independently.
• Serial on any COM port via node-serialport, line-buffered. Each unique line is its own trigger.
• RFID — HID keyboard-wedge readers get a burst detector, so a badge tap is one clean event instead of fourteen keystrokes.
• OSC and Art-Net in — XOSC sits in the middle of a rig, not just at the edge: incoming OSC and DMX-over-Art-Net are first-class graph inputs, timecode included.

The DMX engine

Output isn't just OSC anymore. XOSC transmits full DMX universes with HTP / LTP / smart merging, sACN priorities, and ArtPoll discovery, imports fixture definitions from GDTF and the Open Fixture Library, and can drive color in HSV space. A live inspector shows every universe as a 32×16 grid with source-attributed coloring and per-universe frame rates — when a channel misbehaves mid-show, you can see which input is holding it. Frames can be captured to JSONL for later replay and debugging.

Video out, on any monitor

A PlayerOut node opens a frameless video window on any connected display — playlists, a WebGL2 effect chain, and transport commands wired into the same mapping graph as everything else. A foot pedal can start a video on the projector while the same trigger fires a lighting cue. Resolume itself gets first-class treatment via its WebSocket API with Bonjour discovery.

Signal chain

Capture → match → emit. An event arrives; the input bus normalizes it to a stable signature (midi:noteOn:1:60, kbd:F13, serial:COM4:BTN1_DOWN); the React Flow mapping graph routes it to every wired output node; each output node owns its destination and emits. Pulse, Toggle, and Hold arg modes determine the payload shape, and multiple outputs fire in parallel — two Resolume machines, a lighting desk, and a video wall at the same time.

How it's split

The renderer is React + React Flow: the mapping graph, the listeners that don't need Node (keyboard, Web MIDI, Gamepad API), and every UI surface — including a nine-pane settings router with a context-aware help drawer. The main process owns the Node-only pieces: the node-osc UDP sender, the DMX/Art-Net transmitters, serialport, Resolume's WebSocket, video-player windows, Electron's globalShortcut, and persisted configuration. IPC is a thin command channel — the renderer asks; main streams events back.

Ten themes, no purple-cyan-glossy

The whole UI is driven by a flat token map applied to :root — eight dark themes (Solder, Phosphor, Blueprint, Sodium, Rack, Console, Vapor, Obsidian), two light (Bone, Newsprint), and a custom theme editor for rooms that need their own palette. Each one repaints both the marketing site and the in-app graph live with no reload. The defaults are tuned for FOH operators staring at the screen for hours — high-contrast monospace, no gloss, no gradients, no glow.

How it ships

Tagging vX.Y.Z kicks GitHub Actions, which builds on windows-latest, runs NSIS for the installer, and uploads XOSC-Setup-X.Y.Z.exe to the GitHub release. The Astro site at xosc.gamingworld.uk auto-fetches the latest release for its download button. The whole pipeline is just release patch → git push --tags. Windows 11 only, unsigned, by design — the rig machines it targets are Windows boxes.

Why "XOSC"

The X stands for "any" — any input, any output, any receiver. The original brief was a single binding for one Resolume macro from a USB foot-pedal; once the mapping graph existed, every other input class was a half-day of plumbing — and then the outputs got the same treatment.