Go to the documentation of this file.
24 #if defined(TEMPLATE_8bit)
26 # define RENAME(N) N ## _8bit
30 #elif defined(TEMPLATE_10bit)
32 # define RENAME(N) N ## _10bit
34 # undef TEMPLATE_10bit
36 #elif defined(TEMPLATE_12bit)
38 # define RENAME(N) N ## _12bit
40 # undef TEMPLATE_12bit
52 b1[
i] -= (
unsigned)((
int)(
b0[
i] + (
unsigned)
b2[
i] + 2) >> 2);
59 for (
i = 0;
i < w2;
i++) {
68 const int w2 =
w >> 1;
73 for (
x = 1;
x < w2;
x++) {
85 const int w2 =
w >> 1;
90 for (
x = 1;
x < w2;
x++)
97 for (
x = 0;
x < w2;
x++) {
105 const int w2 =
w >> 1;
112 for (
x = 2;
x < w2-1;
x++)
120 for (
x = 0;
x < w2;
x++) {
129 const int w2 =
w >> 1;
132 for (
x = 0;
x < w2;
x++) {
156 const int w2 =
w >> 1;
162 for (
x = 0;
x < w2;
x++) {
163 for (
i = 0;
i < 8;
i++)
164 v[
i] =
b[av_clip(
x-3+
i, 0, w2-1)];
168 for (
x = 0;
x < w2;
x++) {
169 for (
i = 0;
i < 8;
i++)
170 v[
i] =
tmp[av_clip(
x-4+
i, 0, w2-1)];
179 const int w2 =
w >> 1;
185 for (
x = 1;
x < w2;
x++) {
193 b[0] = ~((~
b0) >> 1);
194 for (
x = 1;
x < w2;
x++) {
197 b[2*
x-1] = ~((~
b1) >> 1);
198 b[2*
x ] = ~((~
b2) >> 1);
347 for (
i = 0;
i < 6;
i++)
355 if(y-1<(
unsigned)
height) d->horizontal_compose(
b[0], d->temp,
width);
356 if(y+0<(
unsigned)
height) d->horizontal_compose(
b[1], d->temp,
width);
358 for (
i = 0;
i < 6;
i++)
377 if(y-1<(
unsigned)
height) d->horizontal_compose(
b[0], d->temp,
width);
378 if(y+0<(
unsigned)
height) d->horizontal_compose(
b[1], d->temp,
width);
393 for (
i = 0;
i < 8;
i++)
401 if(y-1<(
unsigned)
height) d->horizontal_compose(
b[0], d->temp,
width);
402 if(y+0<(
unsigned)
height) d->horizontal_compose(
b[1], d->temp,
width);
404 for (
i = 0;
i < 8;
i++)
413 int y = d->cs[
level].y;
418 d->horizontal_compose(
b0, d->temp,
width);
419 d->horizontal_compose(
b1, d->temp,
width);
433 for (y = 1; y <
height; y += 2) {
434 for (
i = 0;
i < 8;
i++)
439 for (y = 0; y <
height; y += 2) {
440 for (
i = 0;
i < 8;
i++)
445 for (y = 0; y <
height; y++)
446 d->horizontal_compose(d->buffer + y*
stride, d->temp,
width);
461 for (
i = 0;
i < 4;
i++)
471 if(y-1<(
unsigned)
height) d->horizontal_compose(
b[0], d->temp,
width);
472 if(y+0<(
unsigned)
height) d->horizontal_compose(
b[1], d->temp,
width);
474 for (
i = 0;
i < 4;
i++)
526 int hl = d->height >>
level;
527 int stride_l = d->stride <<
level;
static void RENAME() horizontal_compose_daub97i(uint8_t *_b, uint8_t *_temp, int w)
static void RENAME() spatial_compose_dd97i_init(DWTCompose *cs, uint8_t *buffer, int height, int stride)
#define COMPOSE_FIDELITYiH0(b0, b1, b2, b3, b4, b5, b6, b7, b8)
static void RENAME() vertical_compose_daub97iH1(uint8_t *_b0, uint8_t *_b1, uint8_t *_b2, int width)
static void RENAME() horizontal_compose_haar1i(uint8_t *_b, uint8_t *_temp, int w)
static void RENAME() vertical_compose_daub97iH0(uint8_t *_b0, uint8_t *_b1, uint8_t *_b2, int width)
#define COMPOSE_DIRAC53iH0(b0, b1, b2)
DWTCompose cs[MAX_DECOMPOSITIONS]
static void RENAME() vertical_compose_haar(uint8_t *_b0, uint8_t *_b1, int width)
uint8_t * b[MAX_DWT_SUPPORT]
static void RENAME() spatial_compose_dd137i_dy(DWTContext *d, int level, int width, int height, int stride)
static void RENAME() horizontal_compose_dd137i(uint8_t *_b, uint8_t *_tmp, int w)
static void RENAME() vertical_compose_dd97iH0(uint8_t *_b0, uint8_t *_b1, uint8_t *_b2, uint8_t *_b3, uint8_t *_b4, int width)
void(* vertical_compose_2tap)(uint8_t *b0, uint8_t *b1, int width)
static void RENAME() horizontal_compose_dirac53i(uint8_t *_b, uint8_t *_temp, int w)
static double b1(void *priv, double x, double y)
#define COMPOSE_DAUB97iL1(b0, b1, b2)
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 x
static void RENAME() vertical_compose_dirac53iH0(uint8_t *_b0, uint8_t *_b1, uint8_t *_b2, int width)
it s the only field you need to keep assuming you have a context There is some magic you don t need to care about around this just let it vf type
#define COMPOSE_53iL0(b0, b1, b2)
static double b3(void *priv, double x, double y)
#define COMPOSE_DAUB97iL0(b0, b1, b2)
static void RENAME() spatial_compose97i_init(DWTCompose *cs, uint8_t *buffer, int height, int stride)
static void RENAME() spatial_compose53i_init(DWTCompose *cs, uint8_t *buffer, int height, int stride)
static void RENAME() vertical_compose_daub97iL0(uint8_t *_b0, uint8_t *_b1, uint8_t *_b2, int width)
static void RENAME() spatial_compose_fidelity(DWTContext *d, int level, int width, int height, int stride)
#define COMPOSE_DAUB97iH1(b0, b1, b2)
static av_always_inline void RENAME() horizontal_compose_haari(TYPE *b, TYPE *temp, int w, int shift)
static void RENAME() spatial_compose_dd137i_init(DWTCompose *cs, uint8_t *buffer, int height, int stride)
void(* vertical_compose_l0)(void)
static int RENAME() ff_spatial_idwt_init(DWTContext *d, enum dwt_type type)
static void RENAME() horizontal_compose_haar0i(uint8_t *_b, uint8_t *_temp, int w)
void(* vertical_compose_5tap)(uint8_t *b0, uint8_t *b1, uint8_t *b2, uint8_t *b3, uint8_t *b4, int width)
static void RENAME() horizontal_compose_fidelityi(uint8_t *_b, uint8_t *_tmp, int w)
static av_always_inline av_const int avpriv_mirror(int x, int w)
static void RENAME() horizontal_compose_dd97i(uint8_t *_b, uint8_t *_tmp, int w)
void(* vertical_compose)(void)
one set of lowpass and highpass combined
#define COMPOSE_DD97iH0(b0, b1, b2, b3, b4)
void(* vertical_compose_l1)(void)
#define COMPOSE_FIDELITYiL0(b0, b1, b2, b3, b4, b5, b6, b7, b8)
static void RENAME() spatial_compose_daub97i_dy(DWTContext *d, int level, int width, int height, int stride)
static double b2(void *priv, double x, double y)
static void RENAME() spatial_compose_haari_dy(DWTContext *d, int level, int width, int height, int stride)
static void RENAME() vertical_compose_fidelityiL0(uint8_t *_dst, uint8_t *_b[8], int width)
static av_always_inline void RENAME() interleave(TYPE *dst, TYPE *src0, TYPE *src1, int w2, int add, int shift)
void(* vertical_compose_9tap)(uint8_t *dst, uint8_t *b[8], int width)
#define i(width, name, range_min, range_max)
void(* vertical_compose_3tap)(uint8_t *b0, uint8_t *b1, uint8_t *b2, int width)
static void RENAME() vertical_compose_daub97iL1(uint8_t *_b0, uint8_t *_b1, uint8_t *_b2, int width)
#define COMPOSE_DD137iL0(b0, b1, b2, b3, b4)
static void RENAME() spatial_compose_dirac53i_dy(DWTContext *d, int level, int width, int height, int stride)
static void RENAME() vertical_compose_dd137iL0(uint8_t *_b0, uint8_t *_b1, uint8_t *_b2, uint8_t *_b3, uint8_t *_b4, int width)
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
static void RENAME() vertical_compose53iL0(uint8_t *_b0, uint8_t *_b1, uint8_t *_b2, int width)
the frame and frame reference mechanism is intended to as much as expensive copies of that data while still allowing the filters to produce correct results The data is stored in buffers represented by AVFrame structures Several references can point to the same frame buffer
#define COMPOSE_DAUB97iH0(b0, b1, b2)
static int shift(int a, int b)
void(* vertical_compose_h0)(void)
void(* vertical_compose_h1)(void)
#define AVERROR_INVALIDDATA
Invalid data found when processing input.
static double b0(void *priv, double x, double y)
static void RENAME() spatial_compose_dd97i_dy(DWTContext *d, int level, int width, int height, int stride)
static void RENAME() vertical_compose_fidelityiH0(uint8_t *_dst, uint8_t *_b[8], int width)
#define COMPOSE_HAARiH0(b0, b1)
#define COMPOSE_HAARiL0(b0, b1)