-
Notifications
You must be signed in to change notification settings - Fork 1.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
RTSP Ondemand Proxy - Regression from 1.0.0 to 1.0.1+ #2302
Comments
Hello, the log you posted are not enough to identify the issue since they start from a point in time when the stream was already running. Please attach a log that contains lines from the moment the server is started to the moment the issue occurs. |
I masked the IP subnet and the authentication value but not sure if that is necessary. The stream has issues at
|
In case this is helpful, this is the log from v1.0.0 where the issue does not appear.
|
I think i've understood where the bug is. Between v1.0.0 and v1.0.1, the RTSP client was improved in order to support receiving server requests. A side effect of this refactoring is that the client now checks whether keepalive requests are acknowledged or not. Your camera doesn't reply to keepalive requests:
There should be a
And since the source is on demand, and no one is reading it anymore, the source is stopped by the server:
Of course all this needs to be fixed. |
please try the attached nightly release and let me know if it fixes the issue. [link removed] |
So far so good with the v1.0.3-11 version but I'll let it run through the paces tonight. As for the keep-alive requests; I'm not sure if wz_mini_hacks change to go2rtc impacted anything? I switched over to using go2rtc server for the rtsp feeds. I think previously it used v4l2rtspserver. Is the lack of a keepalive a bug that should be reported on the go2rtc side as well? Or is something just missing in my configuration? |
MediaMTX now supports RTSP streams regardless of the fact that keepalive responses are sent or not. We can't consider the lack of keepalive responses a bug since there are cameras that don't send them, as we have just demonstrated. |
Perfect thank you for fix. I can confirm I didn't see any drop outs with the proxied camera feed last night with the nightly. |
fixed in v1.1.0 |
This issue is being locked automatically because it has been closed for more than 6 months. |
Which version are you using?
v1.0.3 (issue starts with v1.0.1)
Which operating system are you using?
Describe the issue
I have a fairly simple setup with some wyze cameras flashed with rtsp (wz_hacks) that mediamtx is a rtsp proxy server ondemand to clients (android tinycam). Wyze RTSP feeds are secured with basic user/pass authentication. No authentication on rtsp proxy output side.
Within a minute of starting the stream, the rtsp server seems to drop the stream and restart it; leading to a dropped video. Rolling back to v1.0.0 fixes the issue.
Describe how to replicate the issue
Did you attach the server logs?
yes
Here is a IP cleaned log of v.1.0.1 from the time the stream started to when I closed it at the end.
in v1.0.1 I see a similar TEARDOWN event before the OPTIONS
In v1.0.0 I don't see this TEARDOWN event, not sure if this is the result of another error but there's nothing else in the log.
Did you attach a network dump?
no
The text was updated successfully, but these errors were encountered: