> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> On Behalf Of
> Marton Balint
> Sent: Samstag, 14. Juni 2025 00:00
> To: FFmpeg development discussions and patches <ffmpeg-
> de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH 05/10] doc/muxers: Add
> documentation for segment_limit option
>
>
>
> On Fri, 13 Jun 2025, softworkz . wrote:
>
> >
> >> -----Original Message-----
> >> From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> On Behalf
> Of
> >> Marton Balint
> >> Sent: Freitag, 13. Juni 2025 22:26
> >> To: FFmpeg development discussions and patches <ffmpeg-
> >> de...@ffmpeg.org>
> >> Subject: Re: [FFmpeg-devel] [PATCH 05/10] doc/muxers: Add
> >> documentation for segment_limit option
> >>
> >>
> >>
> >> 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.
> >
> > Hi Marton,
> >
> > thanks a lot for reviewing.
> >
> >> You can merge the documentation patch with the feature patch,
> there
> >> is no
> >> need to split.
> >
> > Sure, will do that - I just never know which way is right.
> >
> >
> >> 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.
> >
> > Well, that's the whole point of the feature. FFmpeg will stop as
> > soon as the specified number of segments has been generated.
>
> As far as I understand ffmpeg will not stop, but will keep reading
> on the
> input till the end of the source file, gigabytes worst case. Or am
> I
> missing something?
Ah you are right! It's been a while since I had been dealing with the
use cases. The reason why I said that "it stops" is because we're
additionally setting an end time ('-to') which is slightly after the
end of the last segment to generate.
> > (Please note, that the default is 0, which means that nothing is
> > dropped and there's no change in behavior when it's 0).
> >
> > Probably it's best to look at an example. Let's say we have:
> >
> > - a 300s video
> > - that we want to stream via HLS
> > - Segment-Duration: 3s - makes 100 segments
> > - Now we want to create the segments on-demand only,
> > so we deliver a synthetic playlist with 100 3s segments,
> > even though we don't have any segment yet
> > - Once specific segments are needed, we create them on-the-fly
> >
> > That's a situation that the commit message is about:
> >
> > Existing segments 0-30 and 70-99 => we already have them on disk
> >
> > 31-69 need to be created
> >
> > This option allows to stop precisely after 69.
> > Otherwise, it would start overwriting segment 70 before stopping
> > via 'q' or break signal.
> >
> > So, in order to generate segments 31-69, you will set
> > segment_start_number to 31 and the segment_limit to 38.
> > This causes the muxer to write and complete segment 69
> > in the exact same way like when it would be creating segment
> > 70, but without starting to write segment 70 - which would
> destroy
> > the existing segment 70 (which is good already).
>
> Buy you have to seek in the input to achieve that, don't you? And
> you can
> just as easily specify the input duration to not overwrite segment
> 70...
Here we're getting at the core of the problem: When specifying -to or
a duration, you cannot achieve the exact same "cut" like the segment
muxer does it. It usually cuts by video key frames. And when it does
the cut it also cuts all other streams at that moment. Timestamp
offsets between video and audio are common, often the audio is
somewhat ahead of the video (specifically in case of TV broadcast
streams), but it varies. Also, when transcoding before segmenting,
it's not easy to predict the exact video key frame times.
For each segment n to segment n+1 the cut must be done in a way
that for each stream, there is neither a duplicate nor a missing
frame. That is what makes it non-trivial.
In the end, it always comes down to the same conclusion: the only
way to get the exact same cut point through all streams like the
segment muxer does it - is to let the segment muxer do it.
At least that was my conclusion from intensive work on this, some
years ago.
> If you want to implement the segment limit, you have to make sure
> the
> ffmpeg encoding process stops after the last segment. One idea is
> to
> return an error if the segment limit is reached.
Maybe an EOF/EOS error?
Thanks,
sw
_______________________________________________
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".
