On Fri, 13 Jun 2025, softworkz wrote:
From: softworkz <softwo...@hotmail.com>
Signed-off-by: softworkz <softwo...@hotmail.com>
---
doc/muxers.texi | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/doc/muxers.texi b/doc/muxers.texi
index 6d5c17b4cc..1cca8da1fb 100644
--- a/doc/muxers.texi
+++ b/doc/muxers.texi
@@ -3510,6 +3510,13 @@ packet written. Defaults to @code{0}.
Write segments to files with a .tmp extension. Each file is renamed to its
actual name on completion. This can help to prevent segment files from
being accessed before they are complete. Disabled by default (@code{0}).
+
+@item segment_limit @var{number}
+Stops after the specified number of segments has been generated.
+This can be helpful to fill gaps in a range of already generated segments,
+which is difficult to achieve otherwise as it would either cause the last
+segment to be incomplete or to overwrite an existing segment with a partial
+data. Default is @code{0} - no limit.
You can merge the documentation patch with the feature patch, there is no
need to split.
What is not quite clear is that what is going to happen to the surplus
data at after the last segment? Is it silently dropped? Because that would
be unacceptable IMHO.
Regards,
Marton
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
