#include "libavutil/opt.h"
#include "libavutil/imgutils.h"
#include "avfilter.h"
#include "formats.h"
#include "internal.h"
#include "video.h"
Go to the source code of this file.
◆ OFFSET
◆ FLAGS
◆ CHECK_BIT
#define CHECK_BIT |
( |
|
x, |
|
|
|
a, |
|
|
|
b, |
|
|
|
c |
|
) |
| |
◆ AVFILTER_DEFINE_CLASS()
AVFILTER_DEFINE_CLASS |
( |
bitplanenoise |
| ) |
|
◆ query_formats()
◆ config_input()
◆ filter_frame()
◆ bitplanenoise_options
◆ inputs
◆ outputs
◆ ff_vf_bitplanenoise
Initial value:= {
.name = "bitplanenoise",
.priv_class = &bitplanenoise_class,
}
Definition at line 217 of file vf_bitplanenoise.c.
static int query_formats(AVFilterContext *ctx)
filter_frame For filters that do not use the this method is called when a frame is pushed to the filter s input It can be called at any time except in a reentrant way If the input frame is enough to produce then the filter should push the output frames on the output link immediately As an exception to the previous rule if the input frame is enough to produce several output frames then the filter needs output only at least one per link The additional frames can be left buffered in the filter
static const AVFilterPad inputs[]
#define bit(string, value)
static int filter_frame(AVFilterLink *inlink, AVFrame *in)
static double val(void *priv, double ch)
static int config_input(AVFilterLink *inlink)
static const uint16_t mask[17]
Undefined Behavior In the C some operations are like signed integer dereferencing freed accessing outside allocated Undefined Behavior must not occur in a C it is not safe even if the output of undefined operations is unused The unsafety may seem nit picking but Optimizing compilers have in fact optimized code on the assumption that no undefined Behavior occurs Optimizing code based on wrong assumptions can and has in some cases lead to effects beyond the output of computations The signed integer overflow problem in speed critical code Code which is highly optimized and works with signed integers sometimes has the problem that often the output of the computation does not c
#define NULL_IF_CONFIG_SMALL(x)
Return NULL if CONFIG_SMALL is true, otherwise the argument without modification.
The reader does not expect b to be semantically here and if the code is changed by maybe adding a a division or other the signedness will almost certainly be mistaken To avoid this confusion a new type was SUINT is the C unsigned type but it holds a signed int to use the same example SUINT a
#define AVFILTER_FLAG_SUPPORT_TIMELINE_GENERIC
Some filters support a generic "enable" expression option that can be used to enable or disable a fil...
static const AVFilterPad outputs[]
static const int factor[16]
#define flags(name, subs,...)