-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
srs_error_t SrsRtmpServer::handshake() The logic inside here is problematic. #1057
Comments
The version I just downloaded has the same test results as yours. Additionally, currently IPV4 is handling errors and connection failures. The previous older version did not have this issue.
|
I now comment out the sentence "return srs_error_wrap(err, "complex handshake");", but it still doesn't work. I found that the video data still cannot be transmitted properly through packet capture. @ZiJinMountain, what version are you currently using?
|
The version I am using should be the 3.0 version that has been around for almost a year, and the error code format has not been changed since then.
|
I am using the latest version and streaming files with ffmpeg. Currently, I have only captured one video data packet, and then ffmpeg encountered an error.
|
The live streaming was successful. I found that the issue was with the content of my h264 file. There was some unnecessary information at the beginning, which should not start with 67 or 68.
|
When Complex fails to switch to Simple handshake, there is a logic issue, missing an else statement.
|
srs_error_t SrsRtmpServer::handshake()
{
srs_error_t err = srs_success;
}
If I go for a simple handshake and it succeeds, will I still execute
return srs_error_wrap(err, "complex handshake");
? In that case,err
will not besrs_success
. Please confirm.TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered: