#include <inttypes.h>
#include <stdio.h>
#include <stdlib.h>
#include <libcrystalhd/bc_dts_types.h>
#include <libcrystalhd/bc_dts_defs.h>
#include <libcrystalhd/libcrystalhd_if.h>
#include "avcodec.h"
#include "decode.h"
#include "internal.h"
#include "libavutil/imgutils.h"
#include "libavutil/intreadwrite.h"
#include "libavutil/opt.h"
Go to the source code of this file.
|
static BC_MEDIA_SUBTYPE | id2subtype (CHDContext *priv, enum AVCodecID id) |
|
static void | print_frame_info (CHDContext *priv, BC_DTS_PROC_OUT *output) |
|
static uint64_t | opaque_list_push (CHDContext *priv, uint64_t reordered_opaque) |
|
static OpaqueList * | opaque_list_pop (CHDContext *priv, uint64_t fake_timestamp) |
|
static void | flush (AVCodecContext *avctx) |
|
static av_cold int | uninit (AVCodecContext *avctx) |
|
static av_cold int | init (AVCodecContext *avctx) |
|
static CopyRet | copy_frame (AVCodecContext *avctx, BC_DTS_PROC_OUT *output, AVFrame *frame, int *got_frame) |
|
static CopyRet | receive_frame (AVCodecContext *avctx, AVFrame *frame, int *got_frame) |
|
static int | crystalhd_decode_packet (AVCodecContext *avctx, const AVPacket *avpkt) |
|
static int | crystalhd_receive_frame (AVCodecContext *avctx, AVFrame *frame) |
|
◆ _XOPEN_SOURCE
#define _XOPEN_SOURCE 600 |
◆ OUTPUT_PROC_TIMEOUT
#define OUTPUT_PROC_TIMEOUT 50 |
Timeout parameter passed to DtsProcOutput() in us.
Definition at line 69 of file crystalhd.c.
◆ TIMESTAMP_UNIT
#define TIMESTAMP_UNIT 100000 |
Step between fake timestamps passed to hardware in units of 100ns.
Definition at line 71 of file crystalhd.c.
◆ DEFINE_CRYSTALHD_DECODER
#define DEFINE_CRYSTALHD_DECODER |
( |
|
x, |
|
|
|
X, |
|
|
|
bsf_name |
|
) |
| |
Value: static const AVClass x##_crystalhd_class = { \
.class_name = #
x "_crystalhd", \
}; \
AVCodec ff_##
x##_crystalhd_decoder = { \
.name = #
x "_crystalhd", \
.priv_class = &
x##_crystalhd_class, \
.bsfs = bsf_name, \
.wrapper_name = "crystalhd", \
};
Definition at line 770 of file crystalhd.c.
◆ CopyRet
Enumerator |
---|
RET_ERROR | |
RET_OK | |
RET_COPY_AGAIN | |
Definition at line 78 of file crystalhd.c.
◆ id2subtype()
◆ print_frame_info()
static void print_frame_info |
( |
CHDContext * |
priv, |
|
|
BC_DTS_PROC_OUT * |
output |
|
) |
| |
|
inlinestatic |
◆ opaque_list_push()
static uint64_t opaque_list_push |
( |
CHDContext * |
priv, |
|
|
uint64_t |
reordered_opaque |
|
) |
| |
|
static |
◆ opaque_list_pop()
◆ flush()
◆ uninit()
◆ init()
◆ copy_frame()
◆ receive_frame()
◆ crystalhd_decode_packet()
◆ crystalhd_receive_frame()
◆ options
Initial value:= {
{ "crystalhd_downscale_width",
"Turn on downscaling to the specified width",
}
Definition at line 106 of file crystalhd.c.
static const AVOption options[]
AVPixelFormat
Pixel format.
#define AV_OPT_FLAG_VIDEO_PARAM
#define AV_CODEC_CAP_HARDWARE
Codec is backed by a hardware implementation.
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 enum AVPixelFormat pix_fmts[]
#define LIBAVUTIL_VERSION_INT
Describe the class of an AVClass context structure.
@ AV_PIX_FMT_YUYV422
packed YUV 4:2:2, 16bpp, Y0 Cb Y1 Cr
static CopyRet receive_frame(AVCodecContext *avctx, AVFrame *frame, int *got_frame)
const char * av_default_item_name(void *ptr)
Return the context name.
static av_cold int init(AVCodecContext *avctx)
#define NULL_IF_CONFIG_SMALL(x)
Return NULL if CONFIG_SMALL is true, otherwise the argument without modification.
#define AV_OPT_FLAG_DECODING_PARAM
a generic parameter which can be set by the user for demuxing or decoding
#define AV_CODEC_CAP_DELAY
Encoder or decoder requires flushing with NULL input at the end in order to give the complete and cor...
static int crystalhd_receive_frame(AVCodecContext *avctx, AVFrame *frame)
static void flush(AVCodecContext *avctx)
#define AV_CODEC_CAP_AVOID_PROBING
Decoder is not a preferred choice for probing.
static av_cold int uninit(AVCodecContext *avctx)