Open djkcyl opened 4 months ago
Actually, this bug is caused by FFmpeg failing to reconnect when the RTSP stream is blocked while being pulled. Therefore, you need to modify SRS to detect this issue and restart FFmpeg when the RTSP stream pulling is blocked. We have implemented this feature in the SRS stack camera streaming. We monitor FFmpeg's log, check the time, and the speed rate. If any exceptions are detected, we restart the FFmpeg process. Thus, you can simply switch to using the SRS stack instead. We have already done this.
If you insist on using the SRS media server, you will need to patch the ingest feature, and we would be happy to accept such a patch. However, we currently do not have the time to do this ourselves, especially since we have already implemented it in the SRS stack. Therefore, this feature in SRS is not a high priority for us.
Describe the bug When an RTSP stream is interrupted due to network issues or abnormalities in the device pulling the stream, it cannot reconnect without restarting the SRS to restore functionality.
Version SRS/6.0.113
To Reproduce Steps to reproduce the behavior:
Config
TRANS_BY_GPT4