-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
FFmpegFrameGrabber's timeout for RTSP #711 #712
Conversation
Thanks for the contribution! Since this works only for RTSP, maybe we could name the sample RtspStreamingTimeout.java, what do you think? |
Ok. Should I do it or you will rename it? |
Yes, please rename! Thanks
|
It looks like we can set the "timeout" for the FTP, HTTP, RTMP, SMB, SSH, TCP, UDP, and UNIX protocols as well, in addition to a generic "rw_timeout": http://ffmpeg.org/ffmpeg-all.html#Protocols Would you mind adding this in commented lines of (even if untested) code? |
Interesting. Yes, sure) I'll test it. If it works there is no need in "stimeout". |
Nope. "rw_timeout" isn't working. Actually it's working when grabber is already connected and has lost connection. But it's not working when network interface was disabled before connection attempt. |
Ok, cool, thanks for testing. Let's just leave that as well as "timeout"
for the other protocols in comment.
|
Is it normal? I didn't change the file's name because the option doesn't work the way we expected. Right? |
Yeah, I still need to get Travis going. You can ignore that for now.
|
I'm sure the "timeout" and "rw_timeout" options work for some protocols...
|
Ok. I can rename it to FFmpegStreamingTimeout but I will add comment that it was tested with RTSP only. |
Sounds good! Thanks
|
I think it's done. |
Thanks! Had to fix the filename though |
Oops. Sorry) |
Two methods to test "connection is lost" situations. In addition to #711 issue.