From 9c22039c158c47c03df6c1e3b820fdf727a6c9c2 Mon Sep 17 00:00:00 2001
From: Michael Niedermayer <michaelni@gmx.at>
Date: Mon, 18 Mar 2013 23:17:16 +0100
Subject: [PATCH] doc: Document the order in which avoid_negative_ts is applied
 compared to other timestamp options

Also try to document the rational behind it.

This might fix Ticket2376

Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
---
 doc/ffmpeg-formats.texi | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/doc/ffmpeg-formats.texi b/doc/ffmpeg-formats.texi
index 381e3256adc..0e972a8bd73 100644
--- a/doc/ffmpeg-formats.texi
+++ b/doc/ffmpeg-formats.texi
@@ -146,6 +146,10 @@ 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.
+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
+with vsync/async and copyts.
 @end table
 
 @c man end FORMAT OPTIONS
-- 
GitLab