Remote RTMP Server
Posted: Sat Sep 28, 2019 9:24 pm
The article in CQ-TV256 on OBS inspired me to have a go at streaming from OBS to a remote RTMP server running NGINX on a Raspberry Pi then UTP into Portsdown. Using the code in the article but converted to run to as bash scripted for Linux, after several tweaks, I have been successful in doing so. But I have found that if I stop Streaming from OBS and then start Streaming again, ffmpeg objects with errors like this:
Non-monotonous DTS in out stream 0:1 previous: 2252563, current 290108; changing to 2252564. This may result in incorrect timestamps in the output file.
I believe the error is due to OBS starting a new RTMP stream, but ffmpeg is still expecting the next frame from the original RTMP stream. So the OBS stream now has to be stopped and the ffmpeg script has to be restarted, only then can the OBS stream can be restarted with no errors from ffmpeg.
As the ffmpeg script has to be restarted every time the OBS RTMP stream is restarted, has anyone got a possible workaround not having to restart ffmpeg with every new RTMP stream?
Phil M0PIT
Non-monotonous DTS in out stream 0:1 previous: 2252563, current 290108; changing to 2252564. This may result in incorrect timestamps in the output file.
I believe the error is due to OBS starting a new RTMP stream, but ffmpeg is still expecting the next frame from the original RTMP stream. So the OBS stream now has to be stopped and the ffmpeg script has to be restarted, only then can the OBS stream can be restarted with no errors from ffmpeg.
As the ffmpeg script has to be restarted every time the OBS RTMP stream is restarted, has anyone got a possible workaround not having to restart ffmpeg with every new RTMP stream?
Phil M0PIT