FFmpeg  4.3
Macros | Functions
vp8dsp.h File Reference
#include "libavcodec/vp8dsp.h"

Go to the source code of this file.

Macros

#define VP8_LF_Y(hv, inner, opt)
 
#define VP8_LF_UV(hv, inner, opt)
 
#define VP8_LF_SIMPLE(hv, opt)
 
#define VP8_LF_HV(inner, opt)
 
#define VP8_LF(opt)
 
#define VP8_MC(n, opt)
 
#define VP8_EPEL(w, opt)
 
#define VP8_BILIN(w, opt)
 

Functions

void ff_vp78dsp_init_armv6 (VP8DSPContext *dsp)
 
void ff_vp78dsp_init_neon (VP8DSPContext *dsp)
 
void ff_vp8dsp_init_armv6 (VP8DSPContext *dsp)
 
void ff_vp8dsp_init_neon (VP8DSPContext *dsp)
 

Macro Definition Documentation

◆ VP8_LF_Y

#define VP8_LF_Y (   hv,
  inner,
  opt 
)
Value:
void ff_vp8_##hv##_loop_filter16##inner##_##opt(uint8_t *dst, \
ptrdiff_t stride, \
int flim_E, int flim_I, \
int hev_thresh)

Definition at line 29 of file vp8dsp.h.

◆ VP8_LF_UV

#define VP8_LF_UV (   hv,
  inner,
  opt 
)
Value:
void ff_vp8_##hv##_loop_filter8uv##inner##_##opt(uint8_t *dstU, \
uint8_t *dstV, \
ptrdiff_t stride, \
int flim_E, int flim_I, \
int hev_thresh)

Definition at line 35 of file vp8dsp.h.

◆ VP8_LF_SIMPLE

#define VP8_LF_SIMPLE (   hv,
  opt 
)
Value:
void ff_vp8_##hv##_loop_filter16_simple_##opt(uint8_t *dst, \
ptrdiff_t stride, \
int flim)

Definition at line 42 of file vp8dsp.h.

◆ VP8_LF_HV

#define VP8_LF_HV (   inner,
  opt 
)
Value:
VP8_LF_Y(h, inner, opt); \
VP8_LF_Y(v, inner, opt); \
VP8_LF_UV(h, inner, opt); \
VP8_LF_UV(v, inner, opt)

Definition at line 47 of file vp8dsp.h.

◆ VP8_LF

#define VP8_LF (   opt)
Value:
VP8_LF_HV(, opt); \
VP8_LF_HV(_inner, opt); \
VP8_LF_SIMPLE(h, opt); \
VP8_LF_SIMPLE(v, opt)

Definition at line 53 of file vp8dsp.h.

◆ VP8_MC

#define VP8_MC (   n,
  opt 
)
Value:
void ff_put_vp8_##n##_##opt(uint8_t *dst, ptrdiff_t dststride, \
uint8_t *src, ptrdiff_t srcstride, \
int h, int x, int y)

Definition at line 59 of file vp8dsp.h.

◆ VP8_EPEL

#define VP8_EPEL (   w,
  opt 
)
Value:
VP8_MC(pixels ## w, opt); \
VP8_MC(epel ## w ## _h4, opt); \
VP8_MC(epel ## w ## _h6, opt); \
VP8_MC(epel ## w ## _v4, opt); \
VP8_MC(epel ## w ## _h4v4, opt); \
VP8_MC(epel ## w ## _h6v4, opt); \
VP8_MC(epel ## w ## _v6, opt); \
VP8_MC(epel ## w ## _h4v6, opt); \
VP8_MC(epel ## w ## _h6v6, opt)

Definition at line 64 of file vp8dsp.h.

◆ VP8_BILIN

#define VP8_BILIN (   w,
  opt 
)
Value:
VP8_MC(bilin ## w ## _h, opt); \
VP8_MC(bilin ## w ## _v, opt); \
VP8_MC(bilin ## w ## _hv, opt)

Definition at line 75 of file vp8dsp.h.

Function Documentation

◆ ff_vp78dsp_init_armv6()

void ff_vp78dsp_init_armv6 ( VP8DSPContext dsp)

Definition at line 43 of file vp8dsp_init_armv6.c.

Referenced by ff_vp78dsp_init_arm().

◆ ff_vp78dsp_init_neon()

void ff_vp78dsp_init_neon ( VP8DSPContext dsp)

Definition at line 42 of file vp8dsp_init_neon.c.

Referenced by ff_vp78dsp_init_arm().

◆ ff_vp8dsp_init_armv6()

void ff_vp8dsp_init_armv6 ( VP8DSPContext dsp)

Definition at line 101 of file vp8dsp_init_armv6.c.

Referenced by ff_vp8dsp_init_arm().

◆ ff_vp8dsp_init_neon()

void ff_vp8dsp_init_neon ( VP8DSPContext dsp)

Definition at line 98 of file vp8dsp_init_neon.c.

Referenced by ff_vp8dsp_init_arm().

stride
int stride
Definition: mace.c:144
VP8_LF_Y
#define VP8_LF_Y(hv, inner, opt)
Definition: vp8dsp.h:29
x
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
Definition: fate.txt:150
VP8_MC
#define VP8_MC(n, opt)
Definition: vp8dsp.h:59
VP8_LF_HV
#define VP8_LF_HV(inner, opt)
Definition: vp8dsp.h:47
src
#define src
Definition: vp8dsp.c:254
uint8_t
uint8_t
Definition: audio_convert.c:194
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
_
#define _
h
h
Definition: vp9dsp_template.c:2038