Post a new question



RTMP fallback

Pepijn 2015-12-19 18:17:35 UTC in Nimble Streamer


My server restreams RTMP servers to HLS. Sometimes a RTMP server is offline. What happens is that the stream goes black and nobody is able to connect to it.

I currently have an video file of 30 seconds with the text "The server is currently unavailable." and some fading background images. I'd like to use this as fallback video.

I already read this:
I know how to use a fallback stream but I don't know how to stream a video continuously to Nimble.
I tried ffmpeg with stream_loop -1 but this stops after one loop.

Can you give me some advice on how to stream a video file continuously to Nimble?

Thank you!

Andrey Goncharov 2015-12-19 22:14:51 UTC

Hello Pepijn.

stream_loop is supported by FFMPEG starting from version 2.8.2, however there is another approach for older versions.

Please check this answer:

Joël 2015-12-21 07:46:45 UTC

Hi Pepijn

something like this:
ffmpeg -re -f concat -i "loop.txt" -c copy -f flv "rtmp://IP-nimble/live?rtmpauth=username:password/teststream"

file 'input.mp4'
file 'input.mp4'
file 'input.mp4'
file 'input.mp4'
etc. etc.

With "server-side-task-control" of wmspanel
You can run the command over and over again.

I use JWplayer with two short error video messages.
live stream is not started yet and the live stream is broken please wait.

Pepijn 2015-12-21 20:19:46 UTC


Thank you both for answering!

I tried stream_loop with version 2.8.3 and git version g2dba040.
Both versions jumped to 1 minute after playing 30 seconds of video and stopped then.

I'm now using ffmpeg with a loop. It's far from perfect but I couldn't find a better way.
Here are my files:

Thank you for the help,

Joël 2016-01-04 19:51:02 UTC

Hello Pepijn

Do you make any progress? I have seen your scripts.
I'm not very familiar with making Bash scripts.
But is your authentication to Nimble streamer right?
I like the way you trie to make a fallback with a secondaire rtmp stream, with the rtmp pull functionality of Nimble.

I will try it that way too for our live events, I think.
Only you have to start and stop the second stream manualy.
Otherwise the people will see the error message before and after the live event.

I prefer "server-side-task-control" for starting and repeating the second stream

Post a reply

This website or its third-party tools use cookies, which are necessary to its functioning and required to achieve the purposes illustrated in the Privacy Policy. If you want to know more or withdraw your consent to all or some of the cookies, please refer to the Privacy Policy.
By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies.