diff options
| author | Marton Balint <cus@passwd.hu> | 2017-01-27 03:56:30 +0300 |
|---|---|---|
| committer | Marton Balint <cus@passwd.hu> | 2017-02-05 01:36:46 +0300 |
| commit | 1687fa2131310875e9366b67601ff28e55a43d1c (patch) | |
| tree | 4ac267073f75d31159a2c5c34ec4bb50a879f652 /doc/muxers.texi | |
| parent | 85169a75e17e35d17d26769324628d3202050bff (diff) | |
doc/muxers: remove confusing example for segment muxer option clocktime_wrap_duration
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>
Diffstat (limited to 'doc/muxers.texi')
| -rw-r--r-- | doc/muxers.texi | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/doc/muxers.texi b/doc/muxers.texi index 4372078585..d07ae9ba19 100644 --- a/doc/muxers.texi +++ b/doc/muxers.texi @@ -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 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. |