Go to the documentation of this file.
24 #ifndef AVCODEC_INTERNAL_H
25 #define AVCODEC_INTERNAL_H
40 #define FF_CODEC_CAP_INIT_THREADSAFE (1 << 0)
48 #define FF_CODEC_CAP_INIT_CLEANUP (1 << 1)
55 #define FF_CODEC_CAP_SETS_PKT_DTS (1 << 2)
60 #define FF_CODEC_CAP_SKIP_FRAME_FILL_PARAM (1 << 3)
66 #define FF_CODEC_CAP_EXPORTS_CROPPING (1 << 4)
70 #define FF_CODEC_CAP_SLICE_THREAD_HAS_MF (1 << 5)
75 #define FF_CODEC_CAP_ALLOCATE_PROGRESS (1 << 6)
80 #define FF_CODEC_TAGS_END -1
84 # define ff_tlog(ctx, ...) av_log(ctx, AV_LOG_TRACE, __VA_ARGS__)
86 # define ff_tlog(ctx, ...) do { } while(0)
90 #define FF_DEFAULT_QUANT_BIAS 999999
92 #define FF_QSCALE_TYPE_MPEG1 0
93 #define FF_QSCALE_TYPE_MPEG2 1
94 #define FF_QSCALE_TYPE_H264 2
95 #define FF_QSCALE_TYPE_VP56 3
97 #define FF_SANE_NB_CHANNELS 512U
99 #define FF_SIGNBIT(x) ((x) >> CHAR_BIT * sizeof(x) - 1)
101 #if HAVE_SIMD_ALIGN_64
102 # define STRIDE_ALIGN 64
103 #elif HAVE_SIMD_ALIGN_32
104 # define STRIDE_ALIGN 32
105 #elif HAVE_SIMD_ALIGN_16
106 # define STRIDE_ALIGN 16
108 # define STRIDE_ALIGN 8
223 #define FF_MAX_EXTRADATA_SIZE ((1 << 28) - AV_INPUT_BUFFER_PADDING_SIZE)
271 if (-126 <=
x &&
x <= 128)
291 #define FF_REGET_BUFFER_FLAG_READONLY 1
374 void **
data,
size_t *sei_size);
392 const int * array_valid_values,
int default_value);
396 #if defined(_WIN32) && CONFIG_SHARED && !defined(BUILDING_avcodec)
397 # define av_export_avcodec __declspec(dllimport)
399 # define av_export_avcodec
int64_t ff_guess_coded_bitrate(AVCodecContext *avctx)
Get an estimated video bitrate based on frame size, frame rate and coded bits per pixel.
int avpriv_bprint_to_extradata(AVCodecContext *avctx, struct AVBPrint *buf)
Finalize buf into extradata and set its size appropriately.
AVPixelFormat
Pixel format.
int sample_rate
samples per second
int ff_thread_can_start_frame(AVCodecContext *avctx)
int skip_samples
Number of audio samples to skip at the start of the next decoded frame.
static av_cold int end(AVCodecContext *avctx)
This structure describes decoded (raw) audio or video data.
unsigned int avpriv_toupper4(unsigned int x)
void * frame_thread_encoder
size_t compat_decode_consumed
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 samples
const uint8_t * avpriv_find_start_code(const uint8_t *p, const uint8_t *end, uint32_t *state)
size_t compat_decode_partial_size
AVCPBProperties * ff_add_cpb_side_data(AVCodecContext *avctx)
Add a CPB properties side data to an encoding context.
The bitstream filter state.
uint64_t initial_channel_layout
int is_copy
Whether the parent AVCodecContext is a copy of the context which had init() called on it.
int ff_match_2uint16(const uint16_t(*tab)[2], int size, int a, int b)
Return the index into tab at which {a,b} match elements {[0],[1]} of tab.
int showed_multi_packet_warning
static av_always_inline float av_int2float(uint32_t i)
Reinterpret a 32-bit integer as a float.
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 const struct twinvq_data tab
static double val(void *priv, double ch)
int ff_reget_buffer(AVCodecContext *avctx, AVFrame *frame, int flags)
Identical in function to ff_get_buffer(), except it reuses the existing buffer if available.
int ff_get_buffer(AVCodecContext *avctx, AVFrame *frame, int flags)
Get a buffer for a frame.
static av_always_inline int64_t ff_samples_to_time_base(AVCodecContext *avctx, int64_t samples)
Rescale from sample rate to AVCodecContext.time_base.
static av_always_inline float ff_exp2fi(int x)
2^(x) for integer x
void ff_color_frame(AVFrame *frame, const int color[4])
AVPacket * buffer_pkt
buffers for using new encode/decode API through legacy API
AVFrame * compat_decode_frame
int64_t av_rescale_q(int64_t a, AVRational bq, AVRational cq)
Rescale a 64-bit integer by 2 rational numbers.
int ff_alloc_a53_sei(const AVFrame *frame, size_t prefix_len, void **data, size_t *sei_size)
Check AVFrame for A53 side data and allocate and fill SEI message with A53 info.
This structure describes the bitrate properties of an encoded bitstream.
int changed_frames_dropped
int ff_get_format(AVCodecContext *avctx, const enum AVPixelFormat *fmt)
Select the (possibly hardware accelerated) pixel format.
Rational number (pair of numerator and denominator).
int skip_samples_multiplier
AVPacket * last_pkt_props
Properties (timestamps+side data) extracted from the last packet passed for decoding.
AVRational time_base
This is the fundamental unit of time (in seconds) in terms of which frame timestamps are represented.
const OptionDef options[]
int ff_codec_open2_recursive(AVCodecContext *avctx, const AVCodec *codec, AVDictionary **options)
Call avcodec_open2 recursively by decrementing counter, unlocking mutex, calling the function and the...
void * hwaccel_priv_data
hwaccel-specific private data
void ff_dvdsub_parse_palette(uint32_t *palette, const char *p)
#define AV_NOPTS_VALUE
Undefined timestamp value.
uint8_t * byte_buffer
temporary buffer used for encoders to store their bitstream
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
unsigned int byte_buffer_size
int last_audio_frame
An audio frame with less than required samples has been submitted and padded with silence.
these buffered frames must be flushed immediately if a new input produces new the filter must not call request_frame to get more It must just process the frame or queue it The task of requesting more frames is left to the filter s request_frame method or the application If a filter has several the filter must be ready for frames arriving randomly on any input any filter with several inputs will most likely require some kind of queuing mechanism It is perfectly acceptable to have a limited queue and to drop frames when the inputs are too unbalanced request_frame For filters that do not use the this method is called when a frame is wanted on an output For a it should directly call filter_frame on the corresponding output For a if there are queued frames already one of these frames should be pushed If the filter should request a frame on one of its repeatedly until at least one frame has been pushed Return or at least make progress towards producing a frame
int ff_set_sar(AVCodecContext *avctx, AVRational sar)
Check that the provided sample aspect ratio is valid and set it on the codec context.
main external API structure.
int ff_decode_frame_props(AVCodecContext *avctx, AVFrame *frame)
Set various frame properties from the codec context / packet data.
const uint8_t ff_log2_run[41]
int draining
checks API usage: after codec draining, flush is required to resume operation
int ff_side_data_update_matrix_encoding(AVFrame *frame, enum AVMatrixEncoding matrix_encoding)
Add or update AV_FRAME_DATA_MATRIXENCODING side data.
int ff_set_dimensions(AVCodecContext *s, int width, int height)
Check that the provided frame dimensions are valid and set them on the codec context.
A reference to a data buffer.
int ff_alloc_packet2(AVCodecContext *avctx, AVPacket *avpkt, int64_t size, int64_t min_size)
Check AVPacket size and/or allocate data.
This structure stores compressed data.
#define flags(name, subs,...)
int avpriv_h264_has_num_reorder_frames(AVCodecContext *avctx)
int avpriv_codec_get_cap_skip_frame_fill_param(const AVCodec *codec)
int ff_int_from_list_or_default(void *ctx, const char *val_name, int val, const int *array_valid_values, int default_value)
Check if a value is in the list.