![]() Same as on Windows - preferably you use the Docker/Container version. Run the irl-obs-switcher file after you installed dotnet 6. Most probably you will want to change the forward hosts and OBS host settings to use the correct mapped ip adress depending on your environment. The default config.json will be in the /app directory inside the container and can easily be swapped/edited as you like. This will build the image and name it "irl-obs-switcher". You can easily build the docker image yourself by running this inside the irl-obs-switcher directory: This software can be run almost on any platform and comes with a Dockerfile in the irl-obs-switcher directory. minimalkBitperSecond : The minimum kbit per second (bits not bytes!) of transfer rate to be and stay in the connected OBS scene.switchToConnectedTime : The wait time in milliseconds after a successful connect before switching to the connected OBS scene.timeOut : The timeout in milliseconds to detect disconnects - this is the time after the switch to the disconnected OBS scene is made.forwardPort : The port the traffic will be forwarded to.forwardHost : The ip the traffic will be forwarded to.If empty or missing, it will listen to ANY_ADDRESS. localip : An optional local binding IP the forwarder should listen to.localport : The local port the forwarder should listen to.SemaphoreFileWhenConnected: a file which will be created when a successful connection is made and removed when there is no connection.OBSsceneOnDisconnect : the OBS scene to be used when a disconnect happened.OBSsceneOnConnect : the OBS scene to be used when a successful connection is reported.OBSWebSocketPassword : the password of the OBS WebSocket server as you configured it.OBSWebSocketPort : The port of the OBS WebSocket server as you configured it.OBSWebSocketHost : The hostname/ip adress of the OBS WebSocket server."switchToConnectedTime": 1000 "minimalkBitperSecond": 400 NET 6.0 framework which can be freely downloaded here: dotnet 6 ConfigurationĬonfig.json contains the OBS WebSocket configuration and a list of forwarding rules, for instance : The number of concurrent clients is limited by the number of available ports in the server running the proxy.The original IP of the client is hidden to the server the packets are forwarded to.on macOS currently only IPv4 is supported.write a file when a successful connection is made (semaphore)Įach remote client is mapped to a port of the local server therefore:.when the data rate is at least over a configurable rate in kbit/s or below.after n seconds (configurable) upon connect.switch OBS scenes (by using OBS WebSocket) automatically based on simple rules.IPv4 and IPv6 and mixed scenarios supported (not on macOS currently).forward any stream using srt, rtmp, tcp or plain udp protocols to any IP.It offers a simple JSON formatted configuration file (config.json) where you define the TCP or UDP ports that you use to deliver RTMP (using TCP) or SRT (using UDP) streams to.įurthermore you configure the target IP and Port where you want the data to be delivered to as well as a couple of timeouts. ![]() Whatever your infrastructure this should work somehow. This is a keep-it-simple portable console application that can run on Windows, Linux, MacOS. This tool monitors a live-stream from your camera feed (SRT or RTMP) and when it detects a connect or disconnect it can switch scenes in Open Broadcaster Studio / OBS ( ). I needed a small and simple tool which can proxy TCP and UDP connections, like RTMP or SRT live-streams, and can react upon the availability of these streams. IRL (in real life) OBS scene switcher (and Proxy) Why?
0 Comments
Leave a Reply. |