Documentation for -avoid_negative_ts is too vague

[dbuitenh]

Currently it says: "Shift timestamps to make them positive. 1 enables, 0 disables, default of -1 enables when required by target format."

This fails to cover a few important details:

• How does it interact with the various async and vsync algos?
• How does it interact with -copyts?
• How does it interact with non-monotonic timestamps with both of the above?

[Michael Niedermayer]

There are no specific interactions iam aware of, all combinations should work. If something doesnt work, please be more specific.

[Michael Niedermayer]

Or said differently, which specific case is vague ?
if you ask for constant frame rate through vsync and shifting timestamps to avoid negative ones theres nothing contradicting nor is there is you ask for timestamps to be copied and shifted so they arent negative. But iam happy to clarify any cases that need clarification, i just need to know which cases people find unclear.

[dbuitenh]

If example, if you do -copyts and -avoid_negative_ts, which takes precedent?

If you do -vsync 0 -avoid_negative_ts, which is applied first?

If you do -vsync 0, is avoid_negative_ts ignored?

What about -copyts -vsync 1 -avoid_negative_ts? -async 1 -copyts -avoid_negative_ts?

The interaction between these sorts of flags is not at all clear to anyone without prior knowledge of the code.

[Stefano Sabatini]

Should be fixed since:

commit 9c22039c158c47c03df6c1e3b820fdf727a6c9c2
Author: Michael Niedermayer <michaelni@gmx.at>
Date:   Mon Mar 18 23:17:16 2013 +0100

    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>

and following commits.