Go to the documentation of this file.
21 #ifndef AVUTIL_AVUTIL_H
22 #define AVUTIL_AVUTIL_H
225 #define FF_LAMBDA_SHIFT 7
226 #define FF_LAMBDA_SCALE (1<<FF_LAMBDA_SHIFT)
227 #define FF_QP2LAMBDA 118
228 #define FF_LAMBDA_MAX (256*128-1)
230 #define FF_QUALITY_SCALE FF_LAMBDA_SCALE //FIXME maybe remove
248 #define AV_NOPTS_VALUE ((int64_t)UINT64_C(0x8000000000000000))
254 #define AV_TIME_BASE 1000000
260 #define AV_TIME_BASE_Q (AVRational){1, AV_TIME_BASE}
310 return (
void *)(intptr_t)(p ? p :
x);
331 #define av_int_list_length(list, term) \
332 av_int_list_length_for_size(sizeof(*(list)), list, term)
346 #define AV_FOURCC_MAX_STRING_SIZE 32
348 #define av_fourcc2str(fourcc) av_fourcc_make_string((char[AV_FOURCC_MAX_STRING_SIZE]){0}, fourcc)
const char * av_version_info(void)
Return an informative version string.
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
unsigned avutil_version(void)
Return the LIBAVUTIL_VERSION_INT constant.
FILE * av_fopen_utf8(const char *path, const char *mode)
Open a file using a UTF-8 filename.
unsigned av_int_list_length_for_size(unsigned elsize, const void *list, uint64_t term) av_pure
Compute the length of an integer list.
@ AVMEDIA_TYPE_DATA
Opaque data information usually continuous.
const char * avutil_configuration(void)
Return the libavutil build-time configuration.
Rational number (pair of numerator and denominator).
@ AV_PICTURE_TYPE_SI
Switching Intra.
@ AV_PICTURE_TYPE_I
Intra.
Filter the word “frame” indicates either a video frame or a group of audio as stored in an AVFrame structure Format for each input and each output the list of supported formats For video that means pixel format For audio that means channel sample they are references to shared objects When the negotiation mechanism computes the intersection of the formats supported at each end of a all references to both lists are replaced with a reference to the intersection And when a single format is eventually chosen for a link amongst the remaining list
@ AV_PICTURE_TYPE_SP
Switching Predicted.
AVRational av_get_time_base_q(void)
Return the fractional representation of the internal time base.
char * av_fourcc_make_string(char *buf, uint32_t fourcc)
Fill the provided buffer with a string containing a FourCC (four-character code) representation.
@ AVMEDIA_TYPE_UNKNOWN
Usually treated as AVMEDIA_TYPE_DATA.
@ AV_PICTURE_TYPE_NONE
Undefined.
const char * avutil_license(void)
Return the libavutil license.
char av_get_picture_type_char(enum AVPictureType pict_type)
Return a single letter to describe the given picture type pict_type.
@ AVMEDIA_TYPE_ATTACHMENT
Opaque data information usually sparse.
const char * av_get_media_type_string(enum AVMediaType media_type)
Return a string describing the media_type enum, NULL if media_type is unknown.
@ AV_PICTURE_TYPE_B
Bi-dir predicted.
@ AV_PICTURE_TYPE_P
Predicted.
@ AV_PICTURE_TYPE_BI
BI type.
@ AV_PICTURE_TYPE_S
S(GMC)-VOP MPEG-4.
static void * av_x_if_null(const void *p, const void *x)
Return x default pointer in case p is NULL.