Go to the documentation of this file.
27 #undef HAVE_AV_CONFIG_H
41 ((x) == AV_PIX_FMT_GRAY8 || \
42 (x) == AV_PIX_FMT_YA8 || \
43 (x) == AV_PIX_FMT_GRAY16BE || \
44 (x) == AV_PIX_FMT_GRAY16LE || \
45 (x) == AV_PIX_FMT_YA16BE || \
46 (x) == AV_PIX_FMT_YA16LE)
47 #define hasChroma(x) \
49 (x) == AV_PIX_FMT_MONOBLACK || \
50 (x) == AV_PIX_FMT_MONOWHITE))
52 ((x) == AV_PIX_FMT_BGR32 || \
53 (x) == AV_PIX_FMT_BGR32_1 || \
54 (x) == AV_PIX_FMT_RGB32 || \
55 (x) == AV_PIX_FMT_RGB32_1 || \
56 (x) == AV_PIX_FMT_YUVA420P)
59 int stride1,
int stride2,
int w,
int h)
64 for (y = 0; y <
h; y++) {
65 for (
x = 0;
x <
w;
x++) {
66 int d =
src1[
x + y * stride1] - src2[
x + y * stride2];
85 int srcW,
int srcH,
int dstW,
int dstH,
int flags,
92 static int cur_srcW, cur_srcH;
94 static int srcStride[4];
97 int dstStride[4] = {0};
99 uint64_t ssdY, ssdU = 0, ssdV = 0, ssdA = 0;
108 for (p = 0; p < 4; p++)
113 fprintf(stderr,
"av_image_fill_linesizes failed\n");
116 for (p = 0; p < 4; p++) {
117 srcStride[p] =
FFALIGN(srcStride[p], 16);
120 if (srcStride[p] && !
src[p]) {
129 fprintf(stderr,
"Failed to get %s ---> %s\n",
146 fprintf(stderr,
"av_image_fill_linesizes failed\n");
150 for (
i = 0;
i < 4;
i++) {
157 dstStride[
i] =
FFALIGN(dstStride[
i], 16);
160 if (dstStride[
i] && !dst[
i]) {
171 fprintf(stderr,
"Failed to get %s ---> %s\n",
177 printf(
" %s %dx%d -> %s %3dx%3d flags=%2d",
185 for (
i = 0;
i < 4 && dstStride[
i];
i++)
187 dstStride[
i] *
dstH);
189 if (
r && crc ==
r->crc) {
195 for (
i = 0;
i < 4;
i++) {
196 refStride[
i] =
FFALIGN(refStride[
i], 16);
199 if (refStride[
i] && !
out[
i]) {
209 fprintf(stderr,
"Failed to get %s ---> %s\n",
211 desc_yuva420p->
name);
221 ssdU =
getSSD(
ref[1],
out[1], refStride[1], refStride[1],
222 (
w + 1) >> 1, (
h + 1) >> 1);
223 ssdV =
getSSD(
ref[2],
out[2], refStride[2], refStride[2],
224 (
w + 1) >> 1, (
h + 1) >> 1);
236 for (
i = 0;
i < 4;
i++)
241 printf(
" CRC=%08x SSD=%5"PRId64
",%5"PRId64
",%5"PRId64
",%5"PRId64
"\n",
242 crc, ssdY, ssdU, ssdV, ssdA);
247 for (
i = 0;
i < 4;
i++)
290 for (k = 0;
flags[k] && !res; k++)
291 for (
i = 0;
dstW[
i] && !res;
i++)
292 for (j = 0;
dstH[j] && !res; j++)
306 int w,
int h, FILE *
fp,
312 while (fgets(buf,
sizeof(buf),
fp)) {
316 int srcW = 0, srcH = 0;
319 int dstW = 0, dstH = 0;
324 " %20s %dx%d -> %20s %dx%d flags=%d CRC=%x"
325 " SSD=%"SCNu64
", %"SCNu64
", %"SCNu64
", %"SCNu64
"\n",
326 srcStr, &srcW, &srcH, dstStr, &dstW, &dstH,
327 &
flags, &
r.crc, &
r.ssdY, &
r.ssdU, &
r.ssdV, &
r.ssdA);
329 srcStr[0] = dstStr[0] = 0;
330 ret = sscanf(buf,
"%20s -> %20s\n", srcStr, dstStr);
337 srcW > 8192
U || srcH > 8192
U || dstW > 8192
U || dstH > 8192
U) {
338 fprintf(stderr,
"malformed input file\n");
350 srcFormat, dstFormat,
351 srcW, srcH, dstW, dstH,
flags,
361 int main(
int argc,
char **argv)
367 int rgb_stride[4] = { 4 *
W, 0, 0, 0 };
378 if (!rgb_data || !
data)
381 for (
i = 1;
i < argc;
i += 2) {
382 if (argv[
i][0] !=
'-' ||
i + 1 == argc)
384 if (!strcmp(argv[
i],
"-ref")) {
385 fp = fopen(argv[
i + 1],
"r");
387 fprintf(stderr,
"could not open '%s'\n", argv[
i + 1]);
390 }
else if (!strcmp(argv[
i],
"-cpuflags")) {
394 fprintf(stderr,
"invalid cpu flags %s\n", argv[
i + 1]);
398 }
else if (!strcmp(argv[
i],
"-src")) {
401 fprintf(stderr,
"invalid pixel format %s\n", argv[
i + 1]);
404 }
else if (!strcmp(argv[
i],
"-dst")) {
407 fprintf(stderr,
"invalid pixel format %s\n", argv[
i + 1]);
412 fprintf(stderr,
"bad option or argument missing (%s)\n", argv[
i]);
422 for (y = 0; y <
H; y++)
423 for (
x = 0;
x <
W * 4;
x++)
static void error(const char *err)
void av_force_cpu_flags(int arg)
Disables cpu detection and forces the specified flags.
#define sws_isSupportedOutput(x)
AVPixelFormat
Pixel format.
#define sws_isSupportedInput(x)
int dstW
Width of destination luma/alpha planes.
av_cold void av_lfg_init(AVLFG *c, unsigned int seed)
static void selfTest(const uint8_t *const ref[4], int refStride[4], int w, int h, enum AVPixelFormat srcFormat_in, enum AVPixelFormat dstFormat_in)
const AVPixFmtDescriptor * av_pix_fmt_desc_get(enum AVPixelFormat pix_fmt)
static av_cold int end(AVCodecContext *avctx)
int attribute_align_arg sws_scale(struct SwsContext *c, const uint8_t *const srcSlice[], const int srcStride[], int srcSliceY, int srcSliceH, uint8_t *const dst[], const int dstStride[])
swscale wrapper, so we don't need to export the SwsContext.
int av_get_cpu_flags(void)
Return the flags which specify extensions supported by the CPU.
@ AV_PIX_FMT_NB
number of pixel formats, DO NOT USE THIS if you want to link with shared libav* because the number of...
#define SWS_FAST_BILINEAR
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
int av_parse_cpu_caps(unsigned *flags, const char *s)
Parse CPU caps from a string and update the given AV_CPU_* flags based on that.
enum AVPixelFormat srcFormat
Source pixel format.
int av_image_fill_linesizes(int linesizes[4], enum AVPixelFormat pix_fmt, int width)
Fill plane linesizes for an image with pixel format pix_fmt and width width.
@ AV_PIX_FMT_YUVA420P
planar YUV 4:2:0, 20bpp, (1 Cr & Cb sample per 2x2 Y & A samples)
static unsigned int av_lfg_get(AVLFG *c)
Get the next random unsigned 32-bit number using an ALFG.
void * av_mallocz(size_t size)
Allocate a memory block with alignment suitable for all memory accesses (including vectors if availab...
static uint64_t getSSD(const uint8_t *src1, const uint8_t *src2, int stride1, int stride2, int w, int h)
enum AVPixelFormat dstFormat
Destination pixel format.
static int doTest(const uint8_t *const ref[4], int refStride[4], int w, int h, enum AVPixelFormat srcFormat, enum AVPixelFormat dstFormat, int srcW, int srcH, int dstW, int dstH, int flags, struct Results *r)
Context structure for the Lagged Fibonacci PRNG.
struct SwsContext * sws_getContext(int srcW, int srcH, enum AVPixelFormat srcFormat, int dstW, int dstH, enum AVPixelFormat dstFormat, int flags, SwsFilter *srcFilter, SwsFilter *dstFilter, const double *param)
Allocate and return an SwsContext.
int srcH
Height of source luma/alpha planes.
printf("static const uint8_t my_array[100] = {\n")
const AVCRC * av_crc_get_table(AVCRCId crc_id)
Get an initialized standard CRC table.
int srcW
Width of source luma/alpha planes.
#define i(width, name, range_min, range_max)
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
enum AVPixelFormat av_get_pix_fmt(const char *name)
Return the pixel format corresponding to name.
int main(int argc, char **argv)
void sws_freeContext(struct SwsContext *swsContext)
Free the swscaler context swsContext.
uint32_t av_crc(const AVCRC *ctx, uint32_t crc, const uint8_t *buffer, size_t length)
Calculate the CRC of a block.
static int ref[MAX_W *MAX_W]
Descriptor that unambiguously describes how the bits of a pixel are stored in the up to 4 data planes...
#define flags(name, subs,...)
static int fileTest(const uint8_t *const ref[4], int refStride[4], int w, int h, FILE *fp, enum AVPixelFormat srcFormat_in, enum AVPixelFormat dstFormat_in)
int dstH
Height of destination luma/alpha planes.