Palakis submitted a new resource: Websocket plugin - Remote-control your OBS Studio with Websockets A Websocket API for OBS Studio. The websocket server runs on port 4444 and the protocol is based on the OBSRemote protocol (including authentication) with some additions specific to OBS Studio...
Only download obs-websocket from here if you are running OBS v27. For v28 and above, obs-websocket is included with OBS Studio. A WebSocket RPC API for OBS Studio. The WebSocket server runs on port 4455. See here for client software and...
However, you can download obs-websocket for older releases of OBS Studio. It is highly recommended to keep the WebSocket protected with a password against unauthorized control. A password is generated password for you automatically when you load it for the first time. To change this: Click on the Tools menu Click on obs-websocket Settings
Hello everyone, I’m working on macOS and using Automator to run scripts, whether they’re in Python, Shell, or another language. I’m trying to set up a script that, when launched from Automator, connects to the OBS Studio WebSocket server (port 4455 with a password) to activate or deactivate a...
WebSocket Connecting to the built-in WebSocket endpoint allows for interacting with OBS Studio from external applications and scripts. For more details on enabling WebSocket, see the Remote Control Guide. For more information on the WebSocket library, see the GitHub repository. You can also learn about the obs-websocket protocol API.
We use Websocket extensively to manage our 8 scenes for live broadcasts. We can do almost everything except for start/stop stream, because we first have to go to Manage Stream to select the previously configured stream on YouTube for broadcast. Is there a way to tell StartStream in websocket...
Hi suslik, I managed to get obs-websocket-js to work on a local html file and it records as i wanted. however, when i moved the code to my web app which is online, there is a new problem. The browser due to its security settings does not allow the websocket connection, saying its insecure.
Instead of Qt's WebSockets library, starting with 4.6 obs-websocket now uses websocketpp by zaphoyd. Other benefits include: Requests are received and processed in a separate dedicated threads. The old server processed everything in the UI/main window thread. Everything (main plugin + server dependencies) is now in a single binary file.
OK, thanks for putting me on the right track. I had to wade through a lot of docs on the websocket pages, and dive into the Python SDK for what was a fairly simple task. My use case is fairly basic, as we configure OBS manually, and we just use websocket to start and stop recording remotely to sync with external triggers.
