I think the first one could be done with the WebSocket server that already exists in OBS.
Tools -> Websocket Server Settings
Remote-control of OBS Studio through WebSocket. Contribute to obsproject/obs-websocket development by creating an account on GitHub.
github.com
The second one is still ambiguous as to what you actually want:
- OBS can take a screenshot of the content that you're producing - main output or a particular source - and it drops that in a PNG image file. You can then use an external tool to grab that file and do what you want with it.
- Or you can take a screenshot of the controls as seen on the physical screen. That's an operating system function that OBS has nothing to do with.
For #1, the Advanced Scene Switcher plugin can already respond to a WebSocket message and both take the screenshot and run an external tool to do something with it. So the standardization is already on WebSockets, not HTTP.
This plugin will allow you to automate various tasks using "Macros". Macros consist of a list of conditions under which a list of actions will be performed. Examples and guides can be found in the wiki. Feel free to contribute! If you run...
obsproject.com
Or, there might already be a WS function for this in OBS, so no need for Adv. SS if this is all you're doing with it.
If you absolutely *must* use HTTP, then you probably need another external thing to do that translation. Much easier than inventing a new standard. Node-RED *might* be a possibility, or maybe something else that I haven't heard of yet.
