FFmpeg

Commit Graph

Author	SHA1	Message	Date
Andreas Rheinhardt	d92f38c179	avdevice: Constify all devices This is possible now that the next-API is gone. Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com> Signed-off-by: James Almer <jamrial@gmail.com>	4 years ago
Jun Zhao	3aeb681f07	libavdevice: Update the class name as uniform style Update the class name to uniform indev/outdev style. Reviewed-by: Paul B Mahol <onemda@gmail.com> Signed-off-by: Jun Zhao <barryjzhao@tencent.com>	5 years ago
Marton Balint	4bb0409820	avdevice: migrate to AVFormatContext->url Signed-off-by: Marton Balint <cus@passwd.hu>	7 years ago
Diego Biurrun	8e7e042d41	Remove all output devices The libavformat API is not suitable for exporting output devices as muxers. Some practical problems are e.g. lack of timing/synchronization mechanisms or interaction with output-specific features.	7 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
Diego Biurrun	8d26c193fb	avdevice: Apply a more consistent file naming scheme	10 years ago
Nidhi Makhijani	d6e1d37100	oss_audio: Split muxer and demuxer Signed-off-by: Diego Biurrun <diego@biurrun.de>	10 years ago
Lukasz Marek	f607767d93	lavd: add categories to device implementations Signed-off-by: Lukasz Marek <lukasz.m.luki@gmail.com>	11 years ago
Anton Khirnov	36ef5369ee	Replace all CODEC_ID_* with AV_CODEC_ID_*	12 years ago
Reimar Döffinger	c673c90515	oss,sndio: simplify by using FFMIN. Signed-off-by: Anton Khirnov <anton@khirnov.net>	14 years ago
Stefano Sabatini	6b899e16de	lavdev: prefer the inclusion of avdevice.h over that of libavformat/avformat.h	14 years ago
Reimar Döffinger	e76c0c6a00	Simplify: Use FFMIN.	14 years ago
Stefano Sabatini	e93d97156d	sndio: prefer "FFmpeg" over "Libav" in the license header	14 years ago
Brad	15d59d2cea	sndio support for playback and record Signed-off-by: Anton Khirnov <anton@khirnov.net>	14 years ago

8 Commits (b4e7fc4b4b4aa71ae6806b57ebe1293239497f71)