Chiebot-Mirror
/
FFmpeg
mirror of https://github.com/FFmpeg/FFmpeg.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity

doc/muxers: remove confusing example for segment muxer option clocktime_wrap_duration

Browse Source 
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@passwd.hu>
pull/250/head
Marton Balint 8 years ago
parent 85169a75e1
commit 1687fa2131
1 changed files with 0 additions and 3 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 3
      doc/muxers.texi

3
doc/muxers.texi
Unescape View File

@ -1441,9 +1441,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 can make the segmenter more resilient to backward local time jumps, such as
leap seconds or transition to standard time from daylight savings time. 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 Default is the maximum possible duration which means starting a new segment
regardless of the elapsed time since the last clock time. regardless of the elapsed time since the last clock time.

Write Preview
Loading…
Cancel
Save