-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SRT: How to disable covert SRT to RTMP. #3060
Comments
|
Super, thanks, I will try these out and report back. |
Ah, so none of those options are available yet in any Docker release? I tried to build the StateThread branch, but couldn't get it to work. I suppose I'll wait then for the official Docker versions. Good to know that is progressing. |
Is any error in the StateThread branch, compiler error or run time error? |
I got it to compile with no problems with SRT enabled in the config, I wasn't able to stream SRT in. Perhaps the config has changed in some way I didn't spot or something, or I missed some other parameter somewhere. Anyway, I can wait for the docker version. Thanks for the help so far! |
Have any logs about errors or warnings? Now #3010 is merged into develop branch, docker version arriving soon. |
Great! I took the new 5.0.30 docker and can now run srt_to_rtmp off and the "common live" config from the wiki. I'll see if that changes the issue. Did I understand correctly that peer_idle_timeout is not yet included in this docker version? All blocks I tried to include it in reported an illegal argument. I suggest adding in the docs that you now need to include the srt {enabled on;} block in the vhost config. :) |
Seems fixed. |
Description
If an SRT gets cut without a proper end of stream message from the sender, the stream gets stuck and the same stream id can't be reused until SRS is rebooted. This may have something to do with H256 content and RTMP not supporting it.
Is there a way to prevent SRT to RTMP, as this may affect the situation? I use SRT again to pull the stream down to OBS.
1. SRS Version: all released 4.0 versions so far
Expect (Expected Behavior)
I expect the stream to be freed / ended with a preferably configurable timeout and to be reusable after that. I have not found such a timeout.
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered: