[FFmpeg-devel] [PATCH] doc/muxers: remove confusing example for segment muxer option clocktime_wrap_duration
cus at passwd.hu
Sun Feb 5 00:51:51 EET 2017
On Fri, 27 Jan 2017, Marton Balint wrote:
> Detecting a leap second depends on a lot of things, segment time, segment
> offset, system leap second implementation, the removed part is a huge
> simplification which can be misleading, so it is best to remove it.
> Signed-off-by: Marton Balint <cus at passwd.hu>
> doc/muxers.texi | 3 ---
> 1 file changed, 3 deletions(-)
> diff --git a/doc/muxers.texi b/doc/muxers.texi
> index 26a8f2d..2438ab2 100644
> --- a/doc/muxers.texi
> +++ b/doc/muxers.texi
> @@ -1408,9 +1408,6 @@ within the specified duration after the segmenting clock time. This way you
> can make the segmenter more resilient to backward local time jumps, such as
> leap seconds or transition to standard time from daylight savings time.
> -Assuming that the delay between the packets of your source is less than 0.5
> -second you can detect a leap second by specifying 0.5 as the duration.
> Default is the maximum possible duration which means starting a new segment
> regardless of the elapsed time since the last clock time.
More information about the ffmpeg-devel