FFmpeg

Commit Graph

Author	SHA1	Message	Date
Mateusz	a4743d2574	avformat/yuv4mpeg: add gray9/10/12 support Signed-off-by: Mateusz Brzostek <mateuszb@poczta.onet.pl>	7 years ago
Lou Logan	06eef96b69	fix some a/an typos Signed-off-by: Lou Logan <lou@lrcd.com>	9 years ago
Anton Khirnov	9200514ad8	lavf: replace AVStream.codec with AVStream.codecpar Currently, AVStream contains an embedded AVCodecContext instance, which is used by demuxers to export stream parameters to the caller and by muxers to receive stream parameters from the caller. It is also used internally as the codec context that is passed to parsers. In addition, it is also widely used by the callers as the decoding (when demuxer) or encoding (when muxing) context, though this has been officially discouraged since Libav 11. There are multiple important problems with this approach: - the fields in AVCodecContext are in general one of * stream parameters * codec options * codec state However, it's not clear which ones are which. It is consequently unclear which fields are a demuxer allowed to set or a muxer allowed to read. This leads to erratic behaviour depending on whether decoding or encoding is being performed or not (and whether it uses the AVStream embedded codec context). - various synchronization issues arising from the fact that the same context is used by several different APIs (muxers/demuxers, parsers, bitstream filters and encoders/decoders) simultaneously, with there being no clear rules for who can modify what and the different processes being typically delayed with respect to each other. - avformat_find_stream_info() making it necessary to support opening and closing a single codec context multiple times, thus complicating the semantics of freeing various allocated objects in the codec context. Those problems are resolved by replacing the AVStream embedded codec context with a newly added AVCodecParameters instance, which stores only the stream parameters exported by the demuxers or read by the muxers.	9 years ago
Derek Buitenhuis	21f9468402	avutil: Rename FF_CEIL_COMPAT to AV_CEIL_COMPAT Libav, for some reason, merged this as a public API function. This will aid in future merges. A define is left for backwards compat, just in case some person used it, since it is in a public header. Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com>	9 years ago
Vittorio Giovara	e80307140f	yuv4mpegenc: Use AV_CEIL_RSHIFT where needed	9 years ago
Luca Barbato	d00a8fd417	yuv4mpeg: Use the wrapped avframe pseudo-encoder	9 years ago
Paul B Mahol	5233f2534c	avformat/yuv4mpegenc: use avio_printf() Signed-off-by: Paul B Mahol <onemda@gmail.com>	10 years ago
Michael Niedermayer	d5999b7f28	avformat/yuv4mpegenc: Use AVFormatContext strict_std_compliance instead of AVCodecContext Signed-off-by: Michael Niedermayer <michaelni@gmx.at>	10 years ago
Anton Khirnov	650d384048	yuv4mpegenc: do not access AVCodecContext.coded_frame Its contents are meaningful only if the stream codec context is the one actually used for encoding, which is often not the case (and is discouraged). Use AVCodecContext.field_order instead.	11 years ago
Anton Khirnov	194be1f43e	lavf: switch to AVStream.time_base as the hint for the muxer timebase Previously, AVStream.codec.time_base was used for that purpose, which was quite confusing for the callers. This change also opens the path for removing AVStream.codec. The change in the lavf-mkv test is due to the native timebase (1/1000) being used instead of the default one (1/90000), so the packets are now sent to the crc muxer in the same order in which they are demuxed (previously some of them got reordered because of inexact timestamp conversion).	11 years ago
Anton Khirnov	e4dc1000d7	yuv4mpeg: split the demuxer and muxer into separate files	11 years ago

17 Commits (6a1be7561c870a8cd3cee86a57aabdffb19e3870)