Problem
Stream control surface disconnects and removes the operator's primary scene-switching workflow.
Solution
Root Cause / Diagnostic:
USB selective suspend, under-powered passive USB hubs, or unstable WebSocket network sockets cause hardware control decks (e.g., Stream Deck, MIDI consoles) to disconnect mid-broadcast. When the surface crashes or unmounts, the switcher operator loses physical tactile switching capabilities and scrambles to find on-screen GUI alternatives.
Actionable Fix:
1. Disable Windows USB Selective Suspend and Power Throttling: In Device Manager > Universal Serial Bus controllers, open Root Hub properties and uncheck "Allow the computer to turn off this device to save power"; set Windows Power Plan to "High Performance".
2. Connect Surface via Dedicated Powered USB 3.0 Host Port: Plug control surfaces directly into motherboard rear I/O ports or a dedicated AC-powered 12V USB hub to prevent voltage dips during heavy LED backlight draws.
3. Deploy Secondary Browser/Tablet Web GUI Fallback: Configure a secondary control surface via Bitfocus Companion Web GUI or OBS WebSocket Web interface on an independent iPad or mobile browser connected over LAN.
Pro Tip:
Keep a printed "Panic Sheet" laminated at the broadcast desk showing emergency mouse-click layouts and keyboard overrides, and run Bitfocus Companion on a separate local Raspberry Pi or mini-PC so control surfaces survive an encoder software reboot.
USB selective suspend, under-powered passive USB hubs, or unstable WebSocket network sockets cause hardware control decks (e.g., Stream Deck, MIDI consoles) to disconnect mid-broadcast. When the surface crashes or unmounts, the switcher operator loses physical tactile switching capabilities and scrambles to find on-screen GUI alternatives.
Actionable Fix:
1. Disable Windows USB Selective Suspend and Power Throttling: In Device Manager > Universal Serial Bus controllers, open Root Hub properties and uncheck "Allow the computer to turn off this device to save power"; set Windows Power Plan to "High Performance".
2. Connect Surface via Dedicated Powered USB 3.0 Host Port: Plug control surfaces directly into motherboard rear I/O ports or a dedicated AC-powered 12V USB hub to prevent voltage dips during heavy LED backlight draws.
3. Deploy Secondary Browser/Tablet Web GUI Fallback: Configure a secondary control surface via Bitfocus Companion Web GUI or OBS WebSocket Web interface on an independent iPad or mobile browser connected over LAN.
Pro Tip:
Keep a printed "Panic Sheet" laminated at the broadcast desk showing emergency mouse-click layouts and keyboard overrides, and run Bitfocus Companion on a separate local Raspberry Pi or mini-PC so control surfaces survive an encoder software reboot.