A very nice option is to save a live stream with ffmpeg in "server side task control". The main purpose of direct recording on the origin Nimble-server is: Remux and Uploading of the video files are not needed anymore. second: when you have a live event, you have a local copy of your live event and a second on the server.
What I discover by recording a livestream with multible bitrate streams by starting 3 seperate ffmpeg task in the Wmspanel, it takes about 10sec before the "playback" will start in the webplayer(jwplayer). playing the files on a ipad
providing a smil playlist by nimble.
Can you give me a direction of what is the best way the record a stream with ffmpeg, without remuxing the files again.
current tasks in the wmspanel
ffmpeg -re -i rtmp://localhost/rtmp/video_1 -c copy "/mnt/archive/vod/video_360p-1.mp4"
ffmpeg -re -i rtmp://localhost/rtmp/video_2 -c copy "/mnt/archive/vod/video_480p-2.mp4"
ffmpeg -re -i rtmp://localhost/rtmp/video_3 -c copy "/mnt/archive/vod/video_1080p-3.mp4"
I cannot get what you see in ipad comparing to web players
I use the same jwplayer for both, desktop and mobile devices as webplayer.
But i think maybe its the timestamps or the duration time that is not the same of each mp4 file, because of the seperate ffmpeg tasks. Maybe option -copyts will copy the original timestamps of the live encoder (fmle).
Or can I record the 3 streams in one task?
save only one bitrate and call transcoding after event. you can create script that call several ffmpeg commands. One to save original mp4 file and the rest for transcoding. I think calling several commands to transcode on the fly bad idea.
Yes, Transcoding several resolutions on the fly, is a bad idea. Too CPU intensive. Transcode one by one after event is beter. But actually, you don't want to transcode at all, because its already done. yes we can make script who can call more than one ffmpeg command. So the frames will start almost on the same time.
Again, I will do some several tests with copy the original timestamps during recording of the livestreams, or cutting the beginning and the end of the files afterwards, so the start and duration wil be the same.
and required to achieve the purposes illustrated in the
If you want to know more or withdraw your consent to all or some of the cookies, please
refer to the