Go to the documentation of this file.
80 switch (bpp * 2 +
be) {
83 return bytestream2_get_byte(gb);
85 return bytestream2_get_le16(gb);
87 return bytestream2_get_be16(gb);
89 return bytestream2_get_le32(gb);
91 return bytestream2_get_be32(gb);
99 const int bpp =
c->bpp2;
101 uint16_t *dst16 = (uint16_t *)
c->curbits;
102 uint32_t *dst32 = (uint32_t *)
c->curbits;
104 for (j = 0; j <
c->cur_h; j++) {
105 for (
i = 0;
i <
c->cur_w;
i++) {
116 dst16 = (uint16_t*)
c->curmask;
117 dst32 = (uint32_t*)
c->curmask;
118 for (j = 0; j <
c->cur_h; j++) {
119 for (
i = 0;
i <
c->cur_w;
i++) {
136 if (
c->width <
c->cur_x +
c->cur_w)
137 w =
c->width -
c->cur_x;
139 if (
c->height <
c->cur_y +
c->cur_h)
140 h =
c->height -
c->cur_y;
152 if ((
w < 1) || (
h < 1))
157 uint8_t *cd =
c->curbits, *msk =
c->curmask;
158 for (j = 0; j <
h; j++) {
159 for (
i = 0;
i <
w;
i++)
160 dst[
i] = (dst[
i] & cd[
i]) ^ msk[
i];
165 }
else if (
c->bpp2 == 2) {
166 uint16_t *cd = (uint16_t*)
c->curbits, *msk = (uint16_t*)
c->curmask;
168 for (j = 0; j <
h; j++) {
169 dst2 = (uint16_t*)dst;
170 for (
i = 0;
i <
w;
i++)
171 dst2[
i] = (dst2[
i] & cd[
i]) ^ msk[
i];
176 }
else if (
c->bpp2 == 4) {
177 uint32_t *cd = (uint32_t*)
c->curbits, *msk = (uint32_t*)
c->curmask;
179 for (j = 0; j <
h; j++) {
180 dst2 = (uint32_t*)dst;
181 for (
i = 0;
i <
w;
i++)
182 dst2[
i] = (dst2[
i] & cd[
i]) ^ msk[
i];
196 dst += dx * bpp + dy *
stride;
198 for (j = 0; j <
h; j++) {
202 }
else if (bpp == 2) {
204 for (j = 0; j <
h; j++) {
205 dst2 = (uint16_t*)dst;
206 for (
i = 0;
i <
w;
i++)
210 }
else if (bpp == 4) {
212 for (j = 0; j <
h; j++) {
213 dst2 = (uint32_t*)dst;
214 for (
i = 0;
i <
w;
i++)
226 for (j = 0; j <
h; j++) {
227 for (
i = 0;
i <
w;
i++) {
234 ((uint16_t*)dst)[
i] = p;
237 ((uint32_t*)dst)[
i] = p;
249 int bg = 0, fg = 0, rects,
color,
flags, xy, wh;
250 const int bpp =
c->bpp2;
252 int bw = 16, bh = 16;
254 for (j = 0; j <
h; j += 16) {
259 for (
i = 0;
i <
w;
i += 16, dst2 += 16 * bpp) {
266 flags = bytestream2_get_byte(gb);
280 rects = bytestream2_get_byte(gb);
289 for (k = 0; k < rects; k++) {
290 int rect_x, rect_y, rect_w, rect_h;
293 xy = bytestream2_get_byte(gb);
294 wh = bytestream2_get_byte(gb);
298 rect_w = (wh >> 4) + 1;
299 rect_h = (wh & 0xF) + 1;
301 if (rect_x + rect_w >
w -
i || rect_y + rect_h >
h - j) {
307 rect_w, rect_h, fg, bpp,
stride);
321 c->cur_w =
c->cur_h = 0;
322 c->cur_hx =
c->cur_hy = 0;
330 int buf_size = avpkt->
size;
334 int dx, dy,
w,
h, depth, enc, chunks, res, size_left,
ret;
338 chunks = bytestream2_get_be16(gb);
345 c->pic->key_frame = 0;
352 if (
c->width <
c->cur_x +
w)
353 w =
c->width -
c->cur_x;
355 if (
c->height <
c->cur_y +
h)
356 h =
c->height -
c->cur_y;
367 if ((
w > 0) && (
h > 0)) {
368 outptr =
c->pic->data[0] + dx *
c->bpp2 + dy *
c->pic->linesize[0];
369 for (
i = 0;
i <
h;
i++) {
370 memcpy(outptr,
c->screendta +
i *
c->cur_w *
c->bpp2,
372 outptr +=
c->pic->linesize[0];
382 dx = bytestream2_get_be16(gb);
383 dy = bytestream2_get_be16(gb);
384 w = bytestream2_get_be16(gb);
385 h = bytestream2_get_be16(gb);
386 enc = bytestream2_get_be32(gb);
387 if ((dx +
w >
c->width) || (dy +
h >
c->height)) {
389 "Incorrect frame size: %ix%i+%ix%i of %ix%i\n",
390 w,
h, dx, dy,
c->width,
c->height);
393 outptr =
c->pic->data[0] + dx *
c->bpp2 + dy *
c->pic->linesize[0];
397 if (
w*(int64_t)
h*
c->bpp2 > INT_MAX/2 - 2) {
401 if (size_left < 2 + w * h * c->bpp2 * 2) {
403 "Premature end of data! (need %i got %i)\n",
404 2 +
w *
h *
c->bpp2 * 2, size_left);
412 if ((
c->cur_hx >
c->cur_w) || (
c->cur_hy >
c->cur_h)) {
414 "Cursor hot spot is not in image: "
415 "%ix%i of %ix%i cursor size\n",
416 c->cur_hx,
c->cur_hy,
c->cur_w,
c->cur_h);
417 c->cur_hx =
c->cur_hy = 0;
419 if (
c->cur_w *
c->cur_h >= INT_MAX /
c->bpp2) {
423 int screen_size =
c->cur_w *
c->cur_h *
c->bpp2;
437 c->cur_x = dx -
c->cur_hx;
438 c->cur_y = dy -
c->cur_hy;
447 c->pic->key_frame = 1;
449 depth = bytestream2_get_byte(gb);
450 if (depth !=
c->bpp) {
452 "Depth mismatch. Container %i bpp, "
453 "Frame data: %i bpp\n",
457 c->bigendian = bytestream2_get_byte(gb);
458 if (
c->bigendian & (~1)) {
460 "Invalid header: bigendian flag = %i\n",
c->bigendian);
470 if (size_left < w * h * c->bpp2) {
472 "Premature end of data! (need %i got %i)\n",
473 w *
h *
c->bpp2, size_left);
477 c->pic->linesize[0]);
493 if (
c->width <
c->cur_x +
w)
494 w =
c->width -
c->cur_x;
496 if (
c->height <
c->cur_y +
h)
497 h =
c->height -
c->cur_y;
508 if ((
w > 0) && (
h > 0)) {
509 outptr =
c->pic->data[0] + dx *
c->bpp2 + dy *
c->pic->linesize[0];
510 for (
i = 0;
i <
h;
i++) {
511 memcpy(
c->screendta +
i *
c->cur_w *
c->bpp2, outptr,
513 outptr +=
c->pic->linesize[0];
515 outptr =
c->pic->data[0];
554 c->bpp2 =
c->bpp / 8;
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 be(in the first position) for now. Options ------- Then comes the options array. This is what will define the user accessible options. For example
static av_always_inline void paint_rect(uint8_t *dst, int dx, int dy, int w, int h, int color, int bpp, int stride)
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
void av_frame_free(AVFrame **frame)
Free the frame and any dynamically allocated objects in it, e.g.
This structure describes decoded (raw) audio or video data.
static av_cold int decode_end(AVCodecContext *avctx)
static av_cold int decode_init(AVCodecContext *avctx)
static av_always_inline void bytestream2_skip(GetByteContext *g, unsigned int size)
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
AVFrame * av_frame_alloc(void)
Allocate an AVFrame and set its fields to default values.
static int decode_frame(AVCodecContext *avctx, void *data, int *got_frame, AVPacket *avpkt)
static int decode_hextile(VmncContext *c, uint8_t *dst, GetByteContext *gb, int w, int h, int stride)
#define AV_LOG_ERROR
Something went wrong and cannot losslessly be recovered.
static void decode(AVCodecContext *dec_ctx, AVPacket *pkt, AVFrame *frame, FILE *outfile)
@ AV_PICTURE_TYPE_I
Intra.
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)
static av_always_inline void paint_raw(uint8_t *dst, int w, int h, GetByteContext *gb, int bpp, int be, int stride)
#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.
int av_frame_ref(AVFrame *dst, const AVFrame *src)
Set up a new reference to the data described by the source frame.
static const uint32_t color[16+AV_CLASS_CATEGORY_NB]
int av_reallocp(void *ptr, size_t size)
Allocate, reallocate, or free a block of memory through a pointer to a pointer.
#define AV_LOG_INFO
Standard information.
int bits_per_coded_sample
bits per sample/pixel from the demuxer (needed for huffyuv).
#define i(width, name, range_min, range_max)
static av_always_inline int vmnc_get_pixel(GetByteContext *gb, int bpp, int be)
#define AV_PIX_FMT_RGB555
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
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.
#define AV_PIX_FMT_0RGB32
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 put_cursor(uint8_t *dst, int stride, VmncContext *c, int dx, int dy)
main external API structure.
static void reset_buffers(VmncContext *c)
@ AV_PICTURE_TYPE_P
Predicted.
static void load_cursor(VmncContext *c)
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.