|
|
|
@ -140,12 +140,18 @@ Consider things that a sane encoder should not do as an error. |
|
|
|
|
Use wallclock as timestamps. |
|
|
|
|
|
|
|
|
|
@item avoid_negative_ts @var{integer} (@emph{output}) |
|
|
|
|
Shift timestamps to make them positive. 1 enables, 0 disables, default |
|
|
|
|
of -1 enables when required by target format. |
|
|
|
|
When timestamps are shifted, all timestamps of a output file are shifted |
|
|
|
|
together by the same amount. AV sync, subtitle sync and relative timestamp |
|
|
|
|
differences are preserved compared to how they would have been without |
|
|
|
|
shifting. |
|
|
|
|
Shift timestamps to make them positive. A value of 1 enables shifting, |
|
|
|
|
a value of 0 disables it, the default value of -1 enables shifting |
|
|
|
|
when required by the target format. |
|
|
|
|
|
|
|
|
|
When shifting is enabled, all output timestamps are shifted by the |
|
|
|
|
same amount. Audio, video, and subtitles desynching and relative |
|
|
|
|
timestamp differences are preserved compared to how they would have |
|
|
|
|
been without shifting. |
|
|
|
|
|
|
|
|
|
Also note that this affects only leading negative timestamps, and not |
|
|
|
|
non-monotonic negative timestamps. |
|
|
|
|
|
|
|
|
|
When avoid_negative_ts is used together with copyts, vsync or async then |
|
|
|
|
avoid_negative_ts is applied last. This is neccessary so that containers |
|
|
|
|
which do not support negative timestamps wont get any and can be used |
|
|
|
|