Go to the source code of this file.
|
#define | CHECK_VIDEO_PARAM_CHANGE(s, c, width, height, format, pts) |
|
#define | CHECK_AUDIO_PARAM_CHANGE(s, c, srate, ch_layout, ch_count, format, pts) |
|
#define | OFFSET(x) offsetof(BufferSourceContext, x) |
|
#define | A AV_OPT_FLAG_FILTERING_PARAM|AV_OPT_FLAG_AUDIO_PARAM |
|
#define | V AV_OPT_FLAG_FILTERING_PARAM|AV_OPT_FLAG_VIDEO_PARAM |
|
memory buffer source filter
Definition in file buffersrc.c.
◆ CHECK_VIDEO_PARAM_CHANGE
Value:
av_log(
s,
AV_LOG_INFO,
"filter context - w: %d h: %d fmt: %d, incoming frame - w: %d h: %d fmt: %d pts_time: %s\n",\
av_log(
s,
AV_LOG_WARNING,
"Changing video frame properties on the fly is not supported by all filters.\n");\
}
Definition at line 70 of file buffersrc.c.
◆ CHECK_AUDIO_PARAM_CHANGE
#define CHECK_AUDIO_PARAM_CHANGE |
( |
|
s, |
|
|
|
c, |
|
|
|
srate, |
|
|
|
ch_layout, |
|
|
|
ch_count, |
|
|
|
format, |
|
|
|
pts |
|
) |
| |
Value: if (
c->sample_fmt !=
format ||
c->sample_rate != srate ||\
c->channel_layout != ch_layout ||
c->channels != ch_count) {\
av_log(
s,
AV_LOG_INFO,
"filter context - fmt: %s r: %d layout: %"PRIX64
" ch: %d, incoming frame - fmt: %s r: %d layout: %"PRIX64
" ch: %d pts_time: %s\n",\
av_log(
s,
AV_LOG_ERROR,
"Changing audio frame properties on the fly is not supported.\n");\
}
Definition at line 77 of file buffersrc.c.
◆ OFFSET
◆ av_buffersrc_add_frame_internal()
◆ push_frame()
◆ init_video()
◆ AVFILTER_DEFINE_CLASS() [1/2]
AVFILTER_DEFINE_CLASS |
( |
buffer |
| ) |
|
◆ AVFILTER_DEFINE_CLASS() [2/2]
AVFILTER_DEFINE_CLASS |
( |
abuffer |
| ) |
|
◆ init_audio()
◆ uninit()
◆ query_formats()
◆ config_props()
◆ request_frame()
◆ buffer_options
◆ abuffer_options
◆ avfilter_vsrc_buffer_outputs
Initial value:= {
{
.name = "default",
},
}
Definition at line 453 of file buffersrc.c.
◆ ff_vsrc_buffer
Initial value:= {
.name = "buffer",
.description =
NULL_IF_CONFIG_SMALL(
"Buffer video frames, and make them accessible to the filterchain."),
.priv_class = &buffer_class,
}
Definition at line 463 of file buffersrc.c.
◆ avfilter_asrc_abuffer_outputs
Initial value:= {
{
.name = "default",
},
}
Definition at line 477 of file buffersrc.c.
◆ ff_asrc_abuffer
Initial value:= {
.name = "abuffer",
.description =
NULL_IF_CONFIG_SMALL(
"Buffer audio frames, and make them accessible to the filterchain."),
.priv_class = &abuffer_class,
}
Definition at line 487 of file buffersrc.c.
#define AV_LOG_WARNING
Something somehow does not look correct.
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 av_cold void uninit(AVFilterContext *ctx)
#define AV_LOG_ERROR
Something went wrong and cannot losslessly be recovered.
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 format(the sample packing is implied by the sample format) and sample rate. The lists are not just lists
static const AVFilterPad avfilter_vsrc_buffer_outputs[]
static const AVFilterPad outputs[]
static enum AVPixelFormat pix_fmt
const char * av_get_sample_fmt_name(enum AVSampleFormat sample_fmt)
Return the name of sample_fmt, or NULL if sample_fmt is not recognized.
@ AV_OPT_TYPE_IMAGE_SIZE
offset must point to two consecutive integers
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 inputs
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_ts2timestr(ts, tb)
Convenience macro, the return value should be used only directly in function arguments but never stan...
#define NULL_IF_CONFIG_SMALL(x)
Return NULL if CONFIG_SMALL is true, otherwise the argument without modification.
static int config_props(AVFilterLink *link)
static int request_frame(AVFilterLink *link)
static av_cold int init_audio(AVFilterContext *ctx)
#define AV_LOG_INFO
Standard information.
static int query_formats(AVFilterContext *ctx)
static av_cold int init_video(AVFilterContext *ctx)
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 const AVFilterPad avfilter_asrc_abuffer_outputs[]