Go to the documentation of this file.
19 #ifndef AVFILTER_VAAPI_VPP_H
20 #define AVFILTER_VAAPI_VPP_H
23 #include <va/va_vpp.h>
32 return (uintptr_t)
frame->data[3];
36 #define VAAPI_VPP_BACKGROUND_BLACK 0xff000000
81 VAProcPipelineParameterBuffer *params,
92 VAProcPipelineParameterBuffer *params,
96 VAProcPipelineParameterBuffer *params_list,
static VASurfaceID ff_vaapi_vpp_get_surface_id(const AVFrame *frame)
AVPixelFormat
Pixel format.
AVBufferRef * input_frames_ref
int ff_vaapi_vpp_init_params(AVFilterContext *avctx, VAProcPipelineParameterBuffer *params, const AVFrame *input_frame, AVFrame *output_frame)
void ff_vaapi_vpp_ctx_init(AVFilterContext *avctx)
int ff_vaapi_vpp_make_param_buffers(AVFilterContext *avctx, int type, const void *data, size_t size, int count)
The exact code depends on how similar the blocks are and how related they are to the and needs to apply these operations to the correct inlink or outlink if there are several Macros are available to factor that when no extra processing is inlink
This structure describes decoded (raw) audio or video data.
AVHWFramesContext * input_frames
A link between two filters.
int(* build_filter_params)(AVFilterContext *avctx)
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 type
void ff_vaapi_vpp_ctx_uninit(AVFilterContext *avctx)
enum AVPixelFormat output_format
AVVAAPIDeviceContext * hwctx
Describe the class of an AVClass context structure.
int ff_vaapi_vpp_config_input(AVFilterLink *inlink)
void ff_vaapi_vpp_pipeline_uninit(AVFilterContext *avctx)
static int output_frame(H264Context *h, AVFrame *dst, H264Picture *srcp)
int ff_vaapi_vpp_config_output(AVFilterLink *outlink)
int ff_vaapi_vpp_render_pictures(AVFilterContext *avctx, VAProcPipelineParameterBuffer *params_list, int count, AVFrame *output_frame)
VABufferID filter_buffers[VAProcFilterCount]
This struct describes a set or pool of "hardware" frames (i.e.
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
void(* pipeline_uninit)(AVFilterContext *avctx)
A reference to a data buffer.
int ff_vaapi_vpp_query_formats(const AVFilterContext *avctx, AVFilterFormatsConfig **cfg_in, AVFilterFormatsConfig **cfg_out)
int ff_vaapi_vpp_render_picture(AVFilterContext *avctx, VAProcPipelineParameterBuffer *params, AVFrame *output_frame)
VAAPI connection details.