Browse code

doc/muxers: Document problems of omitting nut syncpoints as well as alternatives

Signed-off-by: Michael Niedermayer <michaelni@gmx.at>

Michael Niedermayer authored on 2014/05/29 10:59:25
Showing 1 changed files
... ...
@@ -714,6 +714,11 @@ Change the syncpoint usage in nut:
714 714
 @table @option
715 715
 @item @var{default} use the normal low-overhead seeking aids.
716 716
 @item @var{none} do not use the syncpoints at all, reducing the overhead but making the stream non-seekable;
717
+    Use of this option is not recommanded, as the resulting files are very damage
718
+    sensitive and seeking is not possible. Also in general the overhead from
719
+    syncpoints is negligible. Note, -@code{write_index} 0 can be used to disable
720
+    all growing data tables, allowing to mux endless streams with limited memory
721
+    and wihout these disadvantages.
717 722
 @item @var{timestamped} extend the syncpoint with a wallclock field.
718 723
 @end table
719 724
 The @var{none} and @var{timestamped} flags are experimental.