I'm building a touchless OBS solution for a Windows-based implementation. This will involve a webclient remote control of some sort (possibly obs-web).
I can implement Wake-on-Lan, auto-login for Windows, and startup-upon-login for OBS, which gets me close. I can also implement a shutdown-if-idle timeout (I think) to shut it down afterwards.
The missing piece is that OBS hasn't implemented the graceful-close-upon-shutdown handshake with Windows (unless that's enabled by an option I haven't found yet). Consequently, if Windows shuts down while OBS is still running, then upon the next power-up OBS operation is blocked by a dialog offering "Safe mode" or "Normal operation", due to being terminated unexpectedly. This requires a human interaction on the Windows PC to get past the dialog, which prevents a fully-touchless solution for stream operation.
To address this, OBS should listen for and handle Windows events which signal shutdown, and do a graceful exit. I'd love it if that feature were implemented.
Note that the solution linked in this post is 10-years-old. There may well be a more modern/current approach to this application behavior today. This approach is suggested for reference only.
I can implement Wake-on-Lan, auto-login for Windows, and startup-upon-login for OBS, which gets me close. I can also implement a shutdown-if-idle timeout (I think) to shut it down afterwards.
The missing piece is that OBS hasn't implemented the graceful-close-upon-shutdown handshake with Windows (unless that's enabled by an option I haven't found yet). Consequently, if Windows shuts down while OBS is still running, then upon the next power-up OBS operation is blocked by a dialog offering "Safe mode" or "Normal operation", due to being terminated unexpectedly. This requires a human interaction on the Windows PC to get past the dialog, which prevents a fully-touchless solution for stream operation.
To address this, OBS should listen for and handle Windows events which signal shutdown, and do a graceful exit. I'd love it if that feature were implemented.
Note that the solution linked in this post is 10-years-old. There may well be a more modern/current approach to this application behavior today. This approach is suggested for reference only.
