FFmpeg  4.3
vf_idet.h
Go to the documentation of this file.
1 /*
2  * This file is part of FFmpeg.
3  *
4  * FFmpeg is free software; you can redistribute it and/or
5  * modify it under the terms of the GNU Lesser General Public
6  * License as published by the Free Software Foundation; either
7  * version 2.1 of the License, or (at your option) any later version.
8  *
9  * FFmpeg is distributed in the hope that it will be useful,
10  * but WITHOUT ANY WARRANTY; without even the implied warranty of
11  * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
12  * Lesser General Public License for more details.
13  *
14  * You should have received a copy of the GNU Lesser General Public
15  * License along with FFmpeg; if not, write to the Free Software
16  * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
17  */
18 
19 #ifndef AVFILTER_IDET_H
20 #define AVFILTER_IDET_H
21 
22 #include "libavutil/pixdesc.h"
23 #include "avfilter.h"
24 
25 #define HIST_SIZE 4
26 
27 typedef int (*ff_idet_filter_func)(const uint8_t *a, const uint8_t *b, const uint8_t *c, int w);
28 
29 typedef enum {
30  TFF,
31  BFF,
34 } Type;
35 
36 typedef enum {
41 
42 typedef struct IDETContext {
43  const AVClass *class;
47  float half_life;
49 
51 
52  uint64_t repeats[3];
53  uint64_t prestat[4];
54  uint64_t poststat[4];
55  uint64_t total_repeats[3];
56  uint64_t total_prestat[4];
57  uint64_t total_poststat[4];
58 
60 
65 
69 
71  int eof;
72 } IDETContext;
73 
74 void ff_idet_init_x86(IDETContext *idet, int for_16b);
75 
76 /* main fall-back for left-over */
77 int ff_idet_filter_line_c(const uint8_t *a, const uint8_t *b, const uint8_t *c, int w);
78 int ff_idet_filter_line_c_16bit(const uint16_t *a, const uint16_t *b, const uint16_t *c, int w);
79 
80 #endif
IDETContext::filter_line
ff_idet_filter_func filter_line
Definition: vf_idet.h:64
IDETContext::half_life
float half_life
Definition: vf_idet.h:47
AVFrame
This structure describes decoded (raw) audio or video data.
Definition: frame.h:300
pixdesc.h
b
#define b
Definition: input.c:41
REPEAT_NONE
@ REPEAT_NONE
Definition: vf_idet.h:37
REPEAT_BOTTOM
@ REPEAT_BOTTOM
Definition: vf_idet.h:39
IDETContext::analyze_interlaced_flag_done
int analyze_interlaced_flag_done
Definition: vf_idet.h:68
RepeatedField
RepeatedField
Definition: vf_idet.h:36
IDETContext
Definition: vf_idet.h:42
IDETContext::prestat
uint64_t prestat[4]
Definition: vf_idet.h:53
PROGRESSIVE
@ PROGRESSIVE
Definition: vf_idet.h:32
IDETContext::interlace_threshold
float interlace_threshold
Definition: vf_idet.h:44
IDETContext::prev
AVFrame * prev
Definition: vf_idet.h:63
BFF
@ BFF
Definition: vf_idet.h:31
IDETContext::next
AVFrame * next
Definition: vf_idet.h:62
REPEAT_TOP
@ REPEAT_TOP
Definition: vf_idet.h:38
IDETContext::repeat_threshold
float repeat_threshold
Definition: vf_idet.h:46
IDETContext::eof
int eof
Definition: vf_idet.h:71
IDETContext::csp
const AVPixFmtDescriptor * csp
Definition: vf_idet.h:70
AVClass
Describe the class of an AVClass context structure.
Definition: log.h:67
IDETContext::total_poststat
uint64_t total_poststat[4]
Definition: vf_idet.h:57
c
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
Definition: undefined.txt:32
IDETContext::interlaced_flag_accuracy
int interlaced_flag_accuracy
Definition: vf_idet.h:66
a
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
Definition: undefined.txt:41
ff_idet_filter_func
int(* ff_idet_filter_func)(const uint8_t *a, const uint8_t *b, const uint8_t *c, int w)
Definition: vf_idet.h:27
IDETContext::analyze_interlaced_flag
int analyze_interlaced_flag
Definition: vf_idet.h:67
HIST_SIZE
#define HIST_SIZE
Definition: vf_idet.h:25
Type
Type
Definition: vf_idet.h:29
uint8_t
uint8_t
Definition: audio_convert.c:194
ff_idet_filter_line_c
int ff_idet_filter_line_c(const uint8_t *a, const uint8_t *b, const uint8_t *c, int w)
Definition: vf_idet.c:87
IDETContext::cur
AVFrame * cur
Definition: vf_idet.h:61
IDETContext::poststat
uint64_t poststat[4]
Definition: vf_idet.h:54
IDETContext::total_prestat
uint64_t total_prestat[4]
Definition: vf_idet.h:56
UNDETERMINED
@ UNDETERMINED
Definition: vf_idet.h:33
IDETContext::total_repeats
uint64_t total_repeats[3]
Definition: vf_idet.h:55
w
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable Submitting the results to the FFmpeg result aggregation server ****************************************************************To submit your results to the server you should run fate through the shell script ‘tests fate sh’ from the FFmpeg sources This script needs to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ v’ options You should get detailed output concerning your SSH configuration and the authentication process The only thing left is to automate the execution of the fate sh script and the synchronisation of the samples directory Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo ug o o w
Definition: fate.txt:150
IDETContext::history
uint8_t history[HIST_SIZE]
Definition: vf_idet.h:59
avfilter.h
IDETContext::repeats
uint64_t repeats[3]
Definition: vf_idet.h:52
AVPixFmtDescriptor
Descriptor that unambiguously describes how the bits of a pixel are stored in the up to 4 data planes...
Definition: pixdesc.h:81
IDETContext::decay_coefficient
uint64_t decay_coefficient
Definition: vf_idet.h:48
IDETContext::progressive_threshold
float progressive_threshold
Definition: vf_idet.h:45
TFF
@ TFF
Definition: vf_idet.h:30
IDETContext::last_type
Type last_type
Definition: vf_idet.h:50
int
int
Definition: ffmpeg_filter.c:192
ff_idet_init_x86
void ff_idet_init_x86(IDETContext *idet, int for_16b)
Definition: vf_idet_init.c:69
ff_idet_filter_line_c_16bit
int ff_idet_filter_line_c_16bit(const uint16_t *a, const uint16_t *b, const uint16_t *c, int w)
Definition: vf_idet.c:100