[FFmpeg-trac] #11217(ffmpeg:new): -ss causing a substantial memory increase
FFmpeg
trac at avcodec.org
Fri Oct 4 19:43:16 EEST 2024
#11217: -ss causing a substantial memory increase
-------------------------------------+-------------------------------------
Reporter: Bryce | Owner: (none)
Chester Newman |
Type: defect | Status: new
Priority: important | Component: ffmpeg
Version: 7.1 | Resolution:
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by Bryce Chester Newman):
Replying to [comment:2 Marton Balint]:
> Are you using the -ss after the -i intentionally? Because the parameter
position controls if ffmpeg seeks in the input file, or decodes the whole
input up to the seek point.
Yes. We don't want to use the -ss before the -i, otherwise as you have
stated, the behavior will skip to the position the in video stream that is
after the start of the video and that will cause the video stream output
-map "[mp4-640]" to start wherever -ss value was set. We have been using
the -ss arg in "-map "[jpg-600]" -ss 67 -f image2 -q:v 5 -update 1
-frames:v 1 /tmp/jpg-600-123456.jpg" and the full example command in the
same position for years, so something has changed in 7.x that is causing a
500% increase memory allocation.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/11217#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list