Obs-studio: OBS Studio doesn't destroy(close) SRT Port.

Created on 19 Sep 2020  路  10Comments  路  Source: obsproject/obs-studio

Platform

Operating system; Edition: Windows 10 Pro / Version: 20H2 / OS Build: 19042.508 / Windows Feature Experience Park: 120.2212.31.0
OBS Studio version: 25.0.8 (64-bit, windows)

Expected Behavior

OBS Studio needs to close and destroy the SRT listener port after you do one of the following;

  • SRT caller disconnects
  • If you delete the source
  • Hide visibility of the source

After the SRT Port is successfully destroyed (closed) and if it's still visible then OBS Studio needs to start listening again (srt mode listener) on said port.

Current Behavior

OBS Studio doesn't destroy(close) and "if" still visible reopen the SRT port after SRT caller disconnects, you have to fully close OBS Studio and start it back up again to regain access to the port SRT used.

Steps to Reproduce

(I have opened and forward ports)

  1. Create new 'Media Source'.
  2. Remove local file check mark.
  3. Add: srt://127.0.0.1:30000?mode=listener into 'Input' field.
  4. Add: mpegts into the 'Input Format' field.
  5. Connect SRT caller to OBS, gain a successful connection, which results in being able to see and hear (Video & Audio) from SRT caller.
  6. Disconnect SRT caller.
  7. Try to reconnect SRT caller with no success.
  8. Restart OBS to destroy and close SRT port.
  9. Reconnect SRT caller with success.

Additional information

The srt-live-transmit does this normally so I don't know why this wasn't implemented when adding SRT support for the Media Source 馃

Confirmed Dependency Issue

Most helpful comment

it might be related to this issue: http://trac.ffmpeg.org/ticket/8372
which is fixed in last ffmpeg build; this would require us to update the ffmpeg deps. It's scheduled for 26.1 release.

All 10 comments

Please fill in the issue template, including reproduction steps especially.

also add as an info the obs version tested. It might be worth testing with 26 rc2 since there's been fixes with Media Source. The issue rests solely on Media Source (which relies on ffmpeg libs)

Sorry I should've know, the issue has been updated.

you might want to try the other way; have the Media Source be a caller. But test rc2 first.

I have a HDMI Encoder with SRT support, I want to be able to send Video & Audio from this HDMI Encoder to OBS and if I disconnect the HDMI Encoder from OBS due to a connection issue I want to be able to reconnect when I am able to.

Trying rc2 now.

what's the encoder ?

You can find the encoder on Amazon here >> DDMALL HEV-4K

oh interesting device; thanks

I am also able to reproduce this on OBS 26.0.2 using the Larix Broadcaster app as my SRT caller.

it might be related to this issue: http://trac.ffmpeg.org/ticket/8372
which is fixed in last ffmpeg build; this would require us to update the ffmpeg deps. It's scheduled for 26.1 release.

Was this page helpful?
0 / 5 - 0 ratings