Go to the documentation of this file.
37 put_bits(&pb, 5,
s->avctx->time_base.den /
s->avctx->time_base.num);
44 put_bits(&pb, 1,
w->top_left_mv_flag = 0);
50 s->slice_height =
s->mb_height /
code;
83 s->dc_table_index = 1;
84 s->mv_table_index = 1;
85 s->per_mb_rl_table = 0;
101 if (!
s->per_mb_rl_table) {
108 s->inter_intra_pred = 0;
126 if (
w->per_mb_rl_bit)
129 if (!
s->per_mb_rl_table) {
131 s->rl_chroma_table_index =
s->rl_table_index;
136 s->inter_intra_pred = 0;
138 s->esc3_level_length = 0;
139 s->esc3_run_length = 0;
148 int motion_x,
int motion_y)
151 int cbp, coded_cbp,
i;
160 for (
i = 0;
i < 6;
i++)
161 if (
s->block_last_index[
i] >= 0)
178 for (
i = 0;
i < 6;
i++) {
180 val = (
s->block_last_index[
i] >= 1);
181 cbp |=
val << (5 -
i);
188 coded_cbp |=
val << (5 -
i);
200 if (
s->inter_intra_pred) {
209 for (
i = 0;
i < 6;
i++)
AVPixelFormat
Pixel format.
void ff_msmpeg4_encode_block(MpegEncContext *s, int16_t *block, int n)
static av_cold int init(AVCodecContext *avctx)
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 all references to the list are updated That means that if a filter requires that its input and output have the same format amongst a supported all it has to do is use a reference to the same list of formats query_formats can leave some formats unset and return AVERROR(EAGAIN) to cause the negotiation mechanism toagain later. That can be used by filters with complex requirements to use the format negotiated on one link to set the formats supported on another. Frame references ownership and permissions
int ff_wmv2_encode_picture_header(MpegEncContext *s, int picture_number)
static void init_put_bits(PutBitContext *s, uint8_t *buffer, int buffer_size)
Initialize the PutBitContext s.
static void put_bits(Jpeg2000EncoderContext *s, int val, int n)
put n times val bit
static int encode_ext_header(Wmv2Context *w)
av_cold void ff_wmv2_common_init(Wmv2Context *w)
static const AVClass wmv2_class
const uint16_t ff_msmp4_mb_i_table[64][2]
static av_cold int wmv2_encode_init(AVCodecContext *avctx)
const uint32_t(*const [WMV2_INTER_CBP_TABLE_COUNT] ff_wmv2_inter_table)[2]
int16_t * ff_h263_pred_motion(MpegEncContext *s, int block, int dir, int *px, int *py)
static double val(void *priv, double ch)
static av_always_inline int wmv2_get_cbp_table_index(MpegEncContext *s, int cbp_index)
int ff_mpv_encode_init(AVCodecContext *avctx)
#define av_assert0(cond)
assert() equivalent, that is always enabled.
int ff_mpv_encode_picture(AVCodecContext *avctx, AVPacket *pkt, const AVFrame *frame, int *got_packet)
static enum AVPixelFormat pix_fmts[]
void * av_mallocz(size_t size)
Allocate a memory block with alignment suitable for all memory accesses (including vectors if availab...
@ AV_PIX_FMT_YUV420P
planar YUV 4:2:0, 12bpp, (1 Cr & Cb sample per 2x2 Y samples)
#define LIBAVUTIL_VERSION_INT
Describe the class of an AVClass context structure.
const char * av_default_item_name(void *ptr)
Return the context name.
@ AV_PICTURE_TYPE_I
Intra.
#define NULL_IF_CONFIG_SMALL(x)
Return NULL if CONFIG_SMALL is true, otherwise the argument without modification.
const AVOption ff_mpv_generic_options[]
#define i(width, name, range_min, range_max)
and forward the test the status of outputs and forward it to the corresponding return FFERROR_NOT_READY If the filters stores internally one or a few frame for some it can consider them to be part of the FIFO and delay acknowledging a status change accordingly Example code
uint8_t * extradata
some codecs need / can use extradata like Huffman tables.
#define FF_CODEC_CAP_INIT_CLEANUP
The codec allows calling the close function for deallocation even if the init function returned a fai...
void ff_msmpeg4_handle_slices(MpegEncContext *s)
int ff_mpv_encode_end(AVCodecContext *avctx)
const char * name
Name of the codec implementation.
void ff_msmpeg4_encode_motion(MpegEncContext *s, int mx, int my)
static int get_bits_diff(MpegEncContext *s)
static const float pred[4]
const char * class_name
The name of the class; usually it is the same name as the context structure type to which the AVClass...
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
#define AV_INPUT_BUFFER_PADDING_SIZE
main external API structure.
const uint8_t ff_table_inter_intra[4][2]
void ff_msmpeg4_code012(PutBitContext *pb, int n)
static void flush_put_bits(PutBitContext *s)
Pad the end of the output stream with zeros.
The exact code depends on how similar the blocks are and how related they are to the block
void ff_wmv2_encode_mb(MpegEncContext *s, int16_t block[6][64], int motion_x, int motion_y)
int ff_msmpeg4_coded_block_pred(MpegEncContext *s, int n, uint8_t **coded_block_ptr)