#11217: Output "-ss" memory consumption regression
-------------------------------------+-------------------------------------
Reporter: Bryce | Owner: (none)
Chester Newman |
Type: defect | Status: new
Priority: important | Component: ffmpeg
Version: 7.1 | Resolution:
Keywords: seek | Blocked By:
seeking |
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by Bryce Chester Newman):
Using the work around as shown here...
`time ffmpeg -y -i 1951279840.mov -i 1951279840.mov \
-filter_complex
"[0:v:0]scale='768:432':force_original_aspect_ratio=decrease:force_divisible_by=2[jpg-600];[1:v:0]scale='1280:640'[mp4-640]"
\
-map "[jpg-600]" -ss 67 -f image2 -q:v 5 -update 1 -frames:v 1
/tmp/jpg-600-123456.jpg \
-map "[mp4-640]" -map_metadata -1 -f mp4 -vcodec libx264 -profile:v main
-level 3.1 -crf 23 -b:v 2500K -movflags faststart -refs 4 -pix_fmt yuv420p
-color_primaries bt709 -color_trc bt709 -colorspace bt709 -preset medium
/tmp/mp4-640-23456.mp4`
...there are some observations worth noting.
1) Memory is as expected when using the above command, but like I
mentioned accessing the file more than once has a cost for us.
2) User Time. The CPU time outside the kernel increased by 35% compared to
the original command in this issue.
3) System Time. Increased by 3% compared to the original command in this
issue.
4) Time to execute increased by 30%(or 3 seconds) compared to the original
command in this issue.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/11217#comment:14>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac
To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".
