Marvin Scholz c6f4e10111 avformat: do not use AVIO_FLAG_* with avio_alloc_context ... The documentation states that here 0 should be used for read-only and 1 for a writable buffer. AVIO_FLAG_WRITE however is 2, while it works due to the way the flag is handled internally, it is still wrong according to the documentation. Additionally it makes it seem as if the AVIO_FLAG_* values could be used here, which is actually not true, as when AVIO_FLAG_READ would be used here it would create a writable buffer as AVIO_FLAG_READ is defined as 1. Signed-off-by: Anton Khirnov <anton@khirnov.net>		2021-12-04 14:06:30 +01:00
..
.gitignore	avformat/tests/gitignore: add fifo_muxer entry	2016-10-18 03:38:37 +02:00
fifo_muxer.c	Remove unnecessary avassert.h inclusions	2021-07-22 15:02:30 +02:00
movenc.c	avformat: do not use AVIO_FLAG_* with avio_alloc_context	2021-12-04 14:06:30 +01:00
noproxy.c
rtmpdh.c	Merge commit '537b5b773b'	2017-04-04 15:56:36 -03:00
seek.c	lav*,tests: remove several register_all calls	2018-04-02 03:26:22 +01:00
srtp.c
url.c	avformat/url: add ff_make_absolulte_url2 to be able to test windows path cases	2021-04-07 22:14:56 +02:00