You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OBS should stop trying to push to the SRT-Server if it receives one of the SRT rejection codes or if the server goes offline.
It should also display a message to the user why the connection failed, similar to the way how it handles RTMP rejection cases.
Current Behavior
OBS keeps trying to push to the SRT-Server, no matter what SRT response code is send to OBS.
Even if the SRT-Server goes offline OBS keeps trying to push indefinitely and has to be killed and relaunched to return to a functional state.
Steps to Reproduce
Setup an SRT Server to push a stream to, that only accepts a specific StreamID or requires encryption.
In OBS, select 'Custom...' under Settings -> Stream -> Service
Input the SRT-URL into Settings -> Stream -> Server. (Make sure the SRT-URL will raise a REJECT response from the SRT-Server. For example by putting in a StreamID that isn't allowed by the server or sending a unencrypted stream when a encrypted one is mandatory)
Click 'Apply'
Click 'Start Streaming'
...
Anything else we should know?
In the log output it is visible that the libsrt package is recognizing the rejection code given by the SRT-Server:
OBS just seems to not do anything with the return code and keeps trying to push to the SRT-Server.
When trying to push a stream to the server via FFMPEG with the same SRT-URL as given to OBS, it properly stops trying to stream to the SRT-Server if the Server returns a valid REJECT reason.
At 17:53:21.496 I closed down the SRT-Server which was recognized by OBS, but it still tried to push to the SRT-Server.
The text was updated successfully, but these errors were encountered:
Operating System Info
Ubuntu 24.04
Other OS
No response
OBS Studio Version
31.0.0
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/s1jlQq5MpdMAwQsS
OBS Studio Crash Log URL
No response
Expected Behavior
OBS should stop trying to push to the SRT-Server if it receives one of the SRT rejection codes or if the server goes offline.
It should also display a message to the user why the connection failed, similar to the way how it handles RTMP rejection cases.
Current Behavior
OBS keeps trying to push to the SRT-Server, no matter what SRT response code is send to OBS.
Even if the SRT-Server goes offline OBS keeps trying to push indefinitely and has to be killed and relaunched to return to a functional state.
Steps to Reproduce
...
Anything else we should know?
In the log output it is visible that the libsrt package is recognizing the rejection code given by the SRT-Server:
OBS just seems to not do anything with the return code and keeps trying to push to the SRT-Server.
When trying to push a stream to the server via FFMPEG with the same SRT-URL as given to OBS, it properly stops trying to stream to the SRT-Server if the Server returns a valid REJECT reason.
At 17:53:21.496 I closed down the SRT-Server which was recognized by OBS, but it still tried to push to the SRT-Server.
The text was updated successfully, but these errors were encountered: