Hello!
I am utilizing OBS as a solution to a unique task (though it may not seem so unique at first- read on!). I'm trying to set up a completely autonomous casting system for an online music/video service. The machine is an NuC 13 streaming to mixer with still images, as a slideshow, and music being played by request and auto-generated playlists. this system is running Windows 7 emb and loading off a DoM/EPROM. I have the system working- however, I can't seem to get OBS to load without throwing errors unless I use a logged in user AND a screen and keyboard is connected and POWERED ON.. and then MANUALLY having to load OBS despite having " --portable --startstreaming" flags set in the command-line variables; and though, this in itself, "could" be tolerated except there are times when the power here tends to go off for 10 second intervals and at random.. especially when there is noone here to MANUALLY RELOAD OBS! this HAS to be done EFFICIENTLY and RELIABLY. (using Firedaemon, a service manager, to handle the start ups, but even tried using startup batch files to no avail.. any suggestions would be appreciated! (I don't understand WHY a screen and mouse/keyboard HAS to be connected and powered just to get OBS to load and stream!).
2 logs 2 different NET connections... third log is when manually loading (by desktop with screen/keyboard/mouse and it working)
I am utilizing OBS as a solution to a unique task (though it may not seem so unique at first- read on!). I'm trying to set up a completely autonomous casting system for an online music/video service. The machine is an NuC 13 streaming to mixer with still images, as a slideshow, and music being played by request and auto-generated playlists. this system is running Windows 7 emb and loading off a DoM/EPROM. I have the system working- however, I can't seem to get OBS to load without throwing errors unless I use a logged in user AND a screen and keyboard is connected and POWERED ON.. and then MANUALLY having to load OBS despite having " --portable --startstreaming" flags set in the command-line variables; and though, this in itself, "could" be tolerated except there are times when the power here tends to go off for 10 second intervals and at random.. especially when there is noone here to MANUALLY RELOAD OBS! this HAS to be done EFFICIENTLY and RELIABLY. (using Firedaemon, a service manager, to handle the start ups, but even tried using startup batch files to no avail.. any suggestions would be appreciated! (I don't understand WHY a screen and mouse/keyboard HAS to be connected and powered just to get OBS to load and stream!).
2 logs 2 different NET connections... third log is when manually loading (by desktop with screen/keyboard/mouse and it working)
Last edited: