Go to the documentation of this file.
51 #define PREAMBLE_SIZE 4096
64 for (
i = 0;
i < 2;
i++) {
65 for (j = 0; j < 256; j++) {
66 for (k = 0; k < 8; k++) {
67 gdv->
frame[
i * 2048 + j * 8 + k] = j;
78 for (
x = 0;
x <
w - 7;
x+=8) {
80 dst[
x + 1] =
src[(
x>>1) + 0];
82 dst[
x + 3] =
src[(
x>>1) + 1];
84 dst[
x + 5] =
src[(
x>>1) + 2];
86 dst[
x + 7] =
src[(
x>>1) + 3];
97 for (
x =
w - 1; (
x+1) & 7;
x--) {
100 for (
x -= 7;
x >= 0;
x -= 8) {
102 dst[
x + 7] =
src[(
x>>1) + 3];
104 dst[
x + 5] =
src[(
x>>1) + 2];
106 dst[
x + 3] =
src[(
x>>1) + 1];
108 dst[
x + 1] =
src[(
x>>1) + 0];
115 for (
x = 0;
x <
w - 7;
x+=8) {
116 dst[
x + 0] =
src[2*
x + 0];
117 dst[
x + 1] =
src[2*
x + 2];
118 dst[
x + 2] =
src[2*
x + 4];
119 dst[
x + 3] =
src[2*
x + 6];
120 dst[
x + 4] =
src[2*
x + 8];
121 dst[
x + 5] =
src[2*
x +10];
122 dst[
x + 6] =
src[2*
x +12];
123 dst[
x + 7] =
src[2*
x +14];
139 for (j = 0; j <
h; j++) {
147 for (j = 0; j <
h; j++) {
151 memcpy(dst1,
src1,
w);
155 if (scale_h && scale_v) {
156 for (y = 0; y < (
h>>1); y++) {
161 }
else if (scale_h) {
162 for (y = 0; y < (
h>>1); y++) {
165 memcpy(dst1,
src1,
w);
167 }
else if (scale_v) {
168 for (y = 0; y <
h; y++) {
182 if (
bits->fill == 0) {
183 bits->queue |= bytestream2_get_byte(gb);
186 res =
bits->queue >> 6;
195 bits->queue = bytestream2_get_le32(gb);
201 int res =
bits->queue & ((1 << nbits) - 1);
203 bits->queue >>= nbits;
205 if (
bits->fill <= 16) {
206 bits->queue |= bytestream2_get_le16(gb) <<
bits->fill;
221 c = bytestream2_get_byte(g2);
222 for (
i = 0;
i <
len;
i++) {
223 bytestream2_put_byte(pb,
c);
229 for (
i = 0;
i <
len;
i++) {
230 bytestream2_put_byte(pb, bytestream2_get_byte(g2));
236 for (
i = 0;
i <
len;
i++) {
237 bytestream2_put_byte(pb, bytestream2_get_byte(g2));
254 for (
c = 0;
c < 256;
c++) {
255 for (
i = 0;
i < 16;
i++) {
263 bytestream2_put_byte(pb, bytestream2_get_byte(gb));
264 }
else if (
tag == 1) {
265 int b = bytestream2_get_byte(gb);
266 int len = (
b & 0xF) + 3;
267 int top = (
b >> 4) & 0xF;
268 int off = (bytestream2_get_byte(gb) << 4) + top - 4096;
270 }
else if (
tag == 2) {
271 int len = (bytestream2_get_byte(gb)) + 2;
300 bytestream2_put_byte(pb, bytestream2_get_byte(gb));
301 }
else if (
tag == 1) {
302 int b = bytestream2_get_byte(gb);
303 int len = (
b & 0xF) + 3;
305 int off = (bytestream2_get_byte(gb) << 4) + top - 4096;
307 }
else if (
tag == 2) {
309 int b = bytestream2_get_byte(gb);
316 len = bytestream2_get_le16(gb);
320 int b = bytestream2_get_byte(gb);
321 int len = (
b & 0x3) + 2;
322 int off = -(
b >> 2) - 1;
348 bytestream2_put_byte(pb, bytestream2_get_byte(gb));
358 if (
val != ((1 << lbits) - 1)) {
364 for (
i = 0;
i <
len;
i++) {
365 bytestream2_put_byte(pb, bytestream2_get_byte(gb));
368 }
else if (
tag == 1) {
375 int bb = bytestream2_get_byte(gb);
376 if ((bb & 0x80) == 0) {
379 int top = (bb & 0x7F) << 8;
380 len = top + bytestream2_get_byte(gb) + 146;
384 }
else if (
tag == 2) {
389 int offs = top + bytestream2_get_byte(gb);
390 if ((subtag != 0) || (offs <= 0xF80)) {
391 int len = (subtag) + 3;
400 real_off = ((offs >> 4) & 0x7) + 1;
401 len = ((offs & 0xF) + 2) * 2;
404 for (
i = 0;
i <
len/2;
i++) {
405 bytestream2_put_byte(pb,
c1);
406 bytestream2_put_byte(pb,
c2);
410 int b = bytestream2_get_byte(gb);
411 int off = ((
b & 0x7F)) + 1;
412 int len = ((
b & 0x80) == 0) ? 2 : 3;
420 int q,
b = bytestream2_get_byte(gb);
421 if ((
b & 0xC0) == 0xC0) {
422 len = ((
b & 0x3F)) + 8;
424 off = (q << 8) + (bytestream2_get_byte(gb)) + 1;
427 if ((
b & 0x80) == 0) {
428 len = ((
b >> 4)) + 6;
431 len = ((
b & 0x3F)) + 14;
434 off = (ofs1 << 8) + (bytestream2_get_byte(gb)) - 4096;
437 int ofs1,
b = bytestream2_get_byte(gb);
439 if ((
b >> 4) == 0xF) {
440 len = bytestream2_get_byte(gb) + 21;
445 off = (ofs1 << 8) + bytestream2_get_byte(gb) - 4096;
464 int ret,
i, pal_size;
473 flags = bytestream2_get_le32(gb);
474 compression =
flags & 0xF;
476 if (compression == 4 || compression == 7 || compression > 8)
489 switch (compression) {
493 for (
i = 0;
i < 256;
i++) {
494 unsigned r = bytestream2_get_byte(gb);
495 unsigned g = bytestream2_get_byte(gb);
496 unsigned b = bytestream2_get_byte(gb);
497 gdv->
pal[
i] = 0xFF
U << 24 |
r << 18 |
g << 10 |
b << 2;
521 dst =
frame->data[0];
527 for (y = 0; y < avctx->
height; y++) {
528 memcpy(dst + didx, gdv->
frame + sidx, avctx->
width);
529 sidx += avctx->
width;
530 didx +=
frame->linesize[0];
536 for (y = 0; y < avctx->
height; y++) {
538 memcpy(dst + didx, gdv->
frame + sidx, avctx->
width);
545 if (!gdv->
scale_h || ((y & 1) == 1)) {
548 didx +=
frame->linesize[0];
#define FF_CODEC_CAP_INIT_THREADSAFE
The codec does not modify any global variables in the init function, allowing to call the init functi...
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
static int decompress_2(AVCodecContext *avctx)
This structure describes decoded (raw) audio or video data.
static av_always_inline int bytestream2_seek(GetByteContext *g, int offset, int whence)
@ AV_PKT_DATA_PALETTE
An AV_PKT_DATA_PALETTE side data packet contains exactly AVPALETTE_SIZE bytes worth of palette.
static int decompress_68(AVCodecContext *avctx, unsigned skip, unsigned use8)
static av_always_inline int bytestream2_tell_p(PutByteContext *p)
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 double val(void *priv, double ch)
static void scaleup(uint8_t *dst, const uint8_t *src, int w)
static av_always_inline int bytestream2_get_bytes_left_p(PutByteContext *p)
static av_always_inline void bytestream2_init_writer(PutByteContext *p, uint8_t *buf, int buf_size)
static void decode(AVCodecContext *dec_ctx, AVPacket *pkt, AVFrame *frame, FILE *outfile)
static int read_bits2(Bits8 *bits, GetByteContext *gb)
#define av_assert0(cond)
assert() equivalent, that is always enabled.
static av_cold int gdv_decode_init(AVCodecContext *avctx)
static void lz_copy(PutByteContext *pb, GetByteContext *g2, int offset, unsigned len)
uint8_t * av_packet_get_side_data(const AVPacket *pkt, enum AVPacketSideDataType type, int *size)
Get side information from packet.
static av_cold int gdv_decode_close(AVCodecContext *avctx)
Undefined Behavior In the C some operations are like signed integer dereferencing freed accessing outside allocated Undefined Behavior must not occur in a C it is not safe even if the output of undefined operations is unused The unsafety may seem nit picking but Optimizing compilers have in fact optimized code on the assumption that no undefined Behavior occurs Optimizing code based on wrong assumptions can and has in some cases lead to effects beyond the output of computations The signed integer overflow problem in speed critical code Code which is highly optimized and works with signed integers sometimes has the problem that often the output of the computation does not c
static av_always_inline int bytestream2_get_bytes_left(GetByteContext *g)
int ff_get_buffer(AVCodecContext *avctx, AVFrame *frame, int flags)
Get a buffer for a frame.
#define AV_CODEC_CAP_DR1
Codec uses get_buffer() for allocating buffers and supports custom allocators.
#define NULL_IF_CONFIG_SMALL(x)
Return NULL if CONFIG_SMALL is true, otherwise the argument without modification.
static void rescale(GDVContext *gdv, uint8_t *dst, int w, int h, int scale_v, int scale_h)
static void fill_bits32(Bits32 *bits, GetByteContext *gb)
it s the only field you need to keep assuming you have a context There is some magic you don t need to care about around this just let it vf offset
#define i(width, name, range_min, range_max)
static void scaledown(uint8_t *dst, const uint8_t *src, int w)
static av_always_inline void bytestream2_skip_p(PutByteContext *p, unsigned int size)
static int gdv_decode_frame(AVCodecContext *avctx, void *data, int *got_frame, AVPacket *avpkt)
const char * name
Name of the codec implementation.
enum AVPixelFormat pix_fmt
Pixel format, see AV_PIX_FMT_xxx.
@ AV_PIX_FMT_PAL8
8 bits with AV_PIX_FMT_RGB32 palette
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
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
static void scaleup_rev(uint8_t *dst, const uint8_t *src, int w)
main external API structure.
void * av_calloc(size_t nmemb, size_t size)
Non-inlined equivalent of av_mallocz_array().
static int decompress_5(AVCodecContext *avctx, unsigned skip)
This structure stores compressed data.
int width
picture width / height.
static av_always_inline void bytestream2_init(GetByteContext *g, const uint8_t *buf, int buf_size)
#define flags(name, subs,...)
#define AVERROR_INVALIDDATA
Invalid data found when processing input.
static int read_bits32(Bits32 *bits, GetByteContext *gb, int nbits)