I have a video archive and ffmpeg sends the movies in my video archive to my rtmp server in order, but each time I switch to a new movie, the server connection is momentarily interrupted and the stream is naturally restarted on my rtmp server. Can I prevent my users from disconnecting until the new stream is sent when my rtmp server is interrupted for a few seconds?
I can say that wait video doesn't work for me, it doesn't work well enough.
There is no way to keep a client connected to the RTMP session if the publisher goes away. My only suggestion is you trying chaining the inputs on the ffmpeg side to keep a persistent output to NGINX-rtmp.
I have a video archive and ffmpeg sends the movies in my video archive to my rtmp server in order, but each time I switch to a new movie, the server connection is momentarily interrupted and the stream is naturally restarted on my rtmp server. Can I prevent my users from disconnecting until the new stream is sent when my rtmp server is interrupted for a few seconds?
I can say that
wait video
doesn't work for me, it doesn't work well enough.