obs-web VS srt

OBS-Web remote control - Control OBS remotely from a web browser (on the same LAN)

Niek obs-web http://obs-web.niek.tv/ works great combined with noalbs or bot commands for manual scene controls

I use http://obs-web.niek.tv/ connected to OBS Websockets to control scene switching from my Galaxy Watch 5 Pro. If the Apple Watch has a reasonable web browser, you may be able to do the same. This really is designed for a mobile phone or tablet, but works fine on my watch.

OBS v28 is amazing. It's bundled with the obs-websocket v5 plugin now. I have updated OBS-web [1] to be compatible with this, so you can now control OBS remotely without any additional setup.

1. https://github.com/Niek/obs-web

Another option is minimizing OBS and using https://github.com/Niek/obs-web to control OBS from a tablet or phone.

Self-promo:

In case anyone is interested in controlling OBS remotely, you can use OBS-web: https://github.com/Niek/obs-web

It's not a full reimplementation of the UI, but offers the most often used controls so you can manage a livestream from e.g. a tablet or phone.

About how the director is controlling the scenes. I've one assistant connected on the GC VM via remote desktop to monitor the transmission and do the audio cues. For the director I've obs-websocket set up and the director is connecting through [obs-web](https://github.com/Niek/obs-web). I am also an actor in this play. Not 100% happy with this setup though. Perhaps the best would be the assistant in a zoom call with with the director and changing the scenes for her as commanded.

Is receiver side also using mobile internet? You could try to setup this on separate server and both sender and receiver connnect to it. https://github.com/Haivision/srt/blob/master/docs/apps/srt-live-transmit.md

Here is one example how to feed SRT stream to ffmpeg. Try streaming directly to this via OBS first and confirm it works before stacking more software between endpoints. https://github.com/Haivision/srt/issues/506

SRT, or Secure Reliable Transport, is a type of streaming protocol that provides enhanced security and reliability for video streaming. SRT is becoming increasingly popular among broadcasters and streamers including industry stalwarts such as ESPN because of its ability to deliver high-quality content over challenging network conditions and for its ability to make contribution and stream ingestion easy. SRT streams provide improved security, low latency, and flexibility and is supported by a global community of developers all contributing to the open-source project. Because of the power of SRT streams, Dolby.io Real-Time Streaming has decided to launch support with an SRT open beta program.

https://github.com/Haivision/srt/discussions/2220 I think this is probably the basis of what i did...

If it turns out to be an SRT/socket issue (rather than an audio issue) you can pump FFmpeg into https://github.com/Haivision/srt srt-live-transmit, and let that do the SRT. It is a very long time since I played with srt-live-transmit, but it did behave differently to both FFmpeg and TSDuck's SRT impementations when there were input issues. Obviously, putting more components in the chain may be disadvantageous, but component abstraction can help when debugging.

SRT is an open-source protocol developed by streaming technology provider Haivision. Known for its security, reliability, compatibility, and low-latency streaming it is the preferred protocol for members of the SRT Alliance. This protocol does not rely on a single codec, which allows developers to pair it with any audio and video codecs they desire.

I've also looked at SRT, which to all intents and purposes ought to work, but doesn't?