| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
This was required by vf_pp, which was just removed.
vf_dlopen has this stuff in its API. This API is considered stable, so
the related fields are not removed from it. But the fields are always 0
now, so there's no point in keeping the example program around.
vf_pullup.c did some extremely awkward passthrough of this information,
but didn't actually use it.
|
| | |
|
| |
|
|
| |
Signed-off-by: wm4 <wm4@nowhere>
|
| | |
|
| |
|
|
| |
assume yadif).
|
| | |
|
| |
|
|
|
|
|
| |
For quiet mode: ILDETECT_QUIET=1 ildetect.sh ...
Telecine decision (guess by ildetect.so) is verified by retrying the
ildetect run with the pullup filter inserted.
|
| |
|
|
|
| |
We can now turn off encoding mode by command line and use vo_null
instead.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
The filter analyzes each frame for combing, and decides at the end
whether the content is likely interlaced, telecined or progressive.
|
| |
|
|
|
| |
This is now defined to mean to never output any frame again (except for
the first).
|
| |
|
|
|
| |
also, default to 0-indexed frame counts (so by default, the 1st frame is
output). Old behaviour can be done by -vf dlopen=./framestep.so:42:41.
|
| |
|
|
| |
We don't need config() ;)
|
| |
|
|
| |
Usage: -vf dlopen=./framestep.so:5
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the first frame of a telecine pattern did not generate an output
frame (because it is a 0 or a 1), this could lead to the first two
output frames getting equal pts values.
When the first frame of a telecine pattern generates exactly one output
frame (i.e. when the telecine pattern starts with 2 or 3), then the
output was correct before this comment, and still is unchanged.
When the first frame of a telecine pattern generates more than one
output frame (i.e. when it starts with 4 to 9), then output pts are
still broken. This is not really solvable without knowing the frame
duration, or delaying output by one frame.
|
| |
|
|
| |
It is unix only, because vf_dlopen filters have no way to receive input (yet)
|
| |
|
|
|
|
| |
This is done by requesting a buffer from the next filter in the chain, instead
of always allocating our own. This allows the next filter to e.g. ensure its
own preferred memory layout.
|
|
|
Usage: -vf dlopen=filename.so:args...
Examples of such filters are provided in TOOLS/vf_dlopen/
|
wm4
shdown
Bruno George de Moraes
Kevin Mitchell
Rudolf Polzer