Go to the documentation of this file.
59 const char *filename =
h->filename;
65 for (
i = 0;
i <
sizeof(
md5);
i++)
73 &
h->interrupt_callback,
NULL,
74 h->protocol_whitelist,
h->protocol_blacklist,
h);
80 if (fwrite(
buf, 1,
i*2+1, stdout) <
i*2+1)
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
int ffurl_close(URLContext *h)
int ffurl_open_whitelist(URLContext **puc, const char *filename, int flags, const AVIOInterruptCB *int_cb, AVDictionary **options, const char *whitelist, const char *blacklist, URLContext *parent)
Create an URLContext for accessing to the resource indicated by url, and open it.
static int md5_close(URLContext *h)
#define AVIO_FLAG_WRITE
write-only
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
int av_strstart(const char *str, const char *pfx, const char **ptr)
Return non-zero if pfx is a prefix of str.
void av_md5_init(AVMD5 *ctx)
Initialize MD5 hashing.
static int md5_open(URLContext *h, const char *filename, int flags)
#define i(width, name, range_min, range_max)
void av_md5_final(AVMD5 *ctx, uint8_t *dst)
Finish hashing and output digest value.
void av_md5_update(AVMD5 *ctx, const uint8_t *src, int len)
Update hash value.
const URLProtocol ff_md5_protocol
struct AVMD5 * av_md5_alloc(void)
Allocate an AVMD5 context.
int ffurl_write(URLContext *h, const unsigned char *buf, int size)
Write size bytes from buf to the resource accessed by h.
static int md5_write(URLContext *h, const unsigned char *buf, int size)
#define flags(name, subs,...)