[FFmpeg-user] 371MB Output file for 6:50 min?

Ferdi Scholten ferdi at sttc-nlp.nl
Sun Jun 27 01:57:35 EEST 2021

Several issues

-timelimit uses CPU time in seconds, so whenever ffmpeg has used 1800 
seconds CPU time on your system. This is not related to the actual 
duration of the video, but how much time ffmpeg needs to execute on your 
CPU, which is on a modern system a fraction of a second for every second 
of video.
Use -t 1800 if you want you recording to stop after an actual duration 
of 1800 seconds.
You dit not specify a codec for your output, could be that ffmpeg is 
just writing raw (uncrompressed) video in there, which will grow to huge 
size very fast.

On 26-06-2021 20:16, S. Helbig via ffmpeg-user wrote:
> Hello,
> FFMPEG is creating an ever growing output file from a recorded IP cam
> stream.
> But the acual video is only about 7min.
> My input command was:
> ffmpeg -loglevel debug -timelimit 1.800 -hide_banner -i
> '' -y
> -segment_time 1.800 /path/to/destination/stream.mp4
> There are a few issues with this:
> FFMPEG doesn't exit after 1800sec/30min. '-timelimit 1.800' seems to be
> ignored (I also tried '1800', same result.)
> The video time in the output file does not correspond to 1800sec/30min
> despite its size (371 MB this time). This may be due to the
> segmentation, so when stopped manually, it may not have completed a segment.
> But why is the output file growing then? '-segment_time' should limit
> the size of this file = segment.
> 1800 seconds of .mp4 should correspond to a fixed maximum size...or not?
> Stephan
> _______________________________________________
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> To unsubscribe, visit link above, or email
> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".

More information about the ffmpeg-user mailing list