aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGyan Doshi <ffmpeg@gyani.pro>2021-06-10 09:53:52 +0530
committerGyan Doshi <ffmpeg@gyani.pro>2021-06-10 09:57:18 +0530
commit99bbf4a5be77edbde4106a459475cb7973d027c7 (patch)
tree93bcb4b82b1578f51f22b4ea915f9ad931bb3aac
parent591b88e6787c4e678237f02a50421d101abd25c2 (diff)
downloadffmpeg-99bbf4a5be77edbde4106a459475cb7973d027c7.tar.gz
doc/ffmpeg: document reinit_filter
-rw-r--r--doc/ffmpeg.texi10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/ffmpeg.texi b/doc/ffmpeg.texi
index 9feabe6517..7827291755 100644
--- a/doc/ffmpeg.texi
+++ b/doc/ffmpeg.texi
@@ -759,6 +759,16 @@ This option is similar to @option{-filter}, the only difference is that its
argument is the name of the file from which a filtergraph description is to be
read.
+@item -reinit_filter[:@var{stream_specifier}] @var{integer} (@emph{input,per-stream})
+This boolean option determines if the filtergraph(s) to which this stream is fed gets
+reinitialized when input frame parameters change mid-stream. This option is enabled by
+default as most video and all audio filters cannot handle deviation in input frame properties.
+Upon reinitialization, existing filter state is lost, like e.g. the frame count @code{n}
+reference available in some filters. Any frames buffered at time of reinitialization are lost.
+The properties where a change triggers reinitialization are,
+for video, frame resolution or pixel format;
+for audio, sample format, sample rate, channel count or channel layout.
+
@item -filter_threads @var{nb_threads} (@emph{global})
Defines how many threads are used to process a filter pipeline. Each pipeline
will produce a thread pool with this many threads available for parallel processing.