Repository navigation
Replies: 1 comment
|
A view from a headless setup: we run OBS Studio Rust on a machine with nobody at the screen and control it over obs-websocket. A modal popup there blocks until someone opens a VNC session to close it, and the websocket client never learns about it. So, three suggestions: 1. A status bar item instead of a popup. For example "Repairs required (2)" in the status bar; a click opens the list of affected sources with a "re-pick" action for each. It does not block, a user who changes setups on purpose (dock on/off) can ignore it, and it stays visible until the device comes back or the source is fixed. Each finding also goes to the log as one warning line. 2. The same information over obs-websocket. The C++ plugin stays unchanged (AGENTS.md), but its public vendor API (
The re-pick itself already works with standard v5 requests ( 3. Load only, for now. The hotplug bugs of #2224 are fixed (#2260–#2265, #2838, #2839, and the ALSA reopen in #2933). Before a hotplug prompt, we would first collect the use cases that remain. One point for "load": some devices are not there at the moment the collection loads. NDI sources are found over the network a few seconds later, and ALSA/USB devices can come up late after a restart. A check exactly at load would report false repairs. A grace period (for example: report a source only if its device is still missing some seconds after load), plus an entry that clears itself when the device appears, avoids that. We can test this on our headless setup (NDI, ALSA, V4L2 sources) when there is an implementation. |
Uh oh!
There was an error while loading. Please reload this page.
Moved here from #2224, which closed after its hotplug bugs were fixed (#2260–#2265, #2838, #2839).
The idea raised in that thread: when a scene collection loads and a display, audio device or camera source points at hardware that is gone or changed (an undocked monitor, a replaced webcam), OBS Studio Rust could tell the user and offer to re-pick, instead of silently showing a black or silent source.
Open questions: when to prompt (load only, or on hotplug too), how to avoid nagging users whose setups change on purpose (laptop on/off a dock), and per-OS feasibility of matching "the same" device. Comments and use cases welcome; a concrete proposal can become an issue.
All reactions