FFmpeg

2.4GB

Tree: a3a501df24

Author	SHA1	Message	Date
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.	11 years ago
Martin Storsjö	cf402d6fa8	rtpenc_mpegts: Set chain->rtp_ctx only after avformat_write_header succeeded By making sure we at each time only have one pointer set, either a local variable or one in the context, we avoid potential double frees in the cleanup routines. If chain->rtp_ctx is set, it is closed by calling avformat_write_trailer, but that shouldn't be called unless avformat_write_header succeeded. This issue was pointed out by Andreas Cadhalpun. Signed-off-by: Martin Storsjö <martin@martin.st>	11 years ago
Martin Storsjö	c83dd2d2a4	rtpenc_mpegts: Free the right ->pb in the error path in the init function This fixes a typo from `8e32b1f096`. Signed-off-by: Martin Storsjö <martin@martin.st>	11 years ago
Martin Storsjö	8e32b1f096	libavformat: Use ffio_free_dyn_buf where applicable Signed-off-by: Martin Storsjö <martin@martin.st>	11 years ago
Martin Storsjö	fc308b30bb	rtpenc_mpegts: Call write_trailer for the mpegts muxer even if no output buffer exists Since the mpegts muxer now can handle being called with a NULL AVIOContext, we don't need to try to allocate one before calling write_trailer. Signed-off-by: Martin Storsjö <martin@martin.st>	11 years ago
Martin Storsjö	8a70ef94b9	libavformat: Add a muxer wrapping mpegts encoding into RTP Since this structurally is quite different from normal RTP (multiple streams are muxed into one single mpegts stream, which is packetized into one single RTP session), it is kept as a separate muxer. Since this structurally also behaves differently than normal RTP, all of the other muxers that do chained RTP muxing (rtsp, sap, mp4) would need to be updated similarly to handle this - in particular, creating one single rtp_mpegts muxer for the whole presentation instead of one rtp muxer per stream. Signed-off-by: Martin Storsjö <martin@martin.st>	14 years ago

6 Commits (a3a501df240fa179fe12c2cf5dbbb4f1d9f650ca)