Go to the source code of this file.
|
static void | v210_planar_unpack_c (const uint32_t *src, uint16_t *y, uint16_t *u, uint16_t *v, int width) |
|
av_cold void | ff_v210dec_init (V210DecContext *s) |
|
static av_cold int | decode_init (AVCodecContext *avctx) |
|
static int | v210_decode_slice (AVCodecContext *avctx, void *arg, int jobnr, int threadnr) |
|
static int | decode_frame (AVCodecContext *avctx, void *data, int *got_frame, AVPacket *avpkt) |
|
◆ READ_PIXELS
#define READ_PIXELS |
( |
|
a, |
|
|
|
b, |
|
|
|
c |
|
) |
| |
Value: do { \
*
b++ = (
val >> 10) & 0x3FF; \
*
c++ = (
val >> 20) & 0x3FF; \
} while (0)
Definition at line 33 of file v210dec.c.
◆ V210DEC_FLAGS
◆ v210_planar_unpack_c()
static void v210_planar_unpack_c |
( |
const uint32_t * |
src, |
|
|
uint16_t * |
y, |
|
|
uint16_t * |
u, |
|
|
uint16_t * |
v, |
|
|
int |
width |
|
) |
| |
|
static |
◆ ff_v210dec_init()
◆ decode_init()
◆ v210_decode_slice()
◆ decode_frame()
◆ v210dec_options
◆ v210dec_class
Initial value:= {
.class_name = "V210 Decoder",
}
Definition at line 210 of file v210dec.c.
◆ ff_v210_decoder
static const AVOption v210dec_options[]
static av_cold int init(AVCodecContext *avctx)
static av_cold int decode_init(AVCodecContext *avctx)
static double val(void *priv, double ch)
static void decode(AVCodecContext *dec_ctx, AVPacket *pkt, AVFrame *frame, FILE *outfile)
#define AV_CODEC_CAP_FRAME_THREADS
Codec supports frame-level multithreading.
#define LIBAVUTIL_VERSION_INT
const char * av_default_item_name(void *ptr)
Return the context name.
static int decode_frame(AVCodecContext *avctx, void *data, int *got_frame, AVPacket *avpkt)
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
#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.
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
#define AV_CODEC_CAP_SLICE_THREADS
Codec supports slice-based (or partition-based) multithreading.
static const AVClass v210dec_class