OBS Scene Automation
Local Connection. Sub-120ms. No Cloud Relay.
VPE talks directly to OBS on your machine via WebSocket. No cloud middleman. No server round-trip. You define which events trigger which scenes. The response fires in under 120ms because both apps are on the same PC.
Sub-120ms LocalDirect OBS WebSocketYour Scene RulesZero Cloud Relay
What VPE Is Doing Right NowLive
obs.connected → WebSocket v5 handshake complete
obs.sources.discovered → 12 sources found (8 with VPE_ prefix)
obs.scenes.loaded → Main, BRB, Hype, Raid, Ending
obs.source.claimed → VPE_overlay_1, VPE_sfx_1, VPE_stinger_1
v5
WebSocket
8
Sources Claimed
Local
Your PC
VPE Engine
→WebSocket v5
→OBS Studio
Direct local WebSocket — no cloud relay
You map events to scenes — your rules
Sub-120ms response on your own hardware
Works with any OBS plugin or source
How It Works
How OBS Control Works
01
Your Events, Your Triggers
You define what matters — raids, donations, chat drops, viewer spikes. VPE watches the events you care about on the platforms you connected.
02
Your Policies Decide the Response
The AI checks your rules — which scene fits, which overlay fires, what cooldowns apply. You wrote the policy. VPE enforces it locally.
03
OBS Responds in Under 120ms
Direct local WebSocket. No cloud hop. No server relay. Your scene changes before your viewers finish blinking. Everything stays on your machine.
Your OBS. Your rules. Sub-120ms. Locally.