- 21 Sep, 2013 1 commit
-
-
Michael Niedermayer authored
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 07 Aug, 2013 1 commit
-
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 24 Jan, 2013 1 commit
-
-
Martin Storsjö authored
In ff_rtp_get_payload_type, the AVFormatContext is used for checking whether the payload_type or rtpflags options are set. In rtpenc_chain, the rtpctx struct is a newly initialized struct where no options have been set yet, so no options can be fetched from there. All muxers that internally chain rtp muxers have the "rtpflags" field that allows passing such options on (which is how this worked before 8034130e), so this works just as intended. This makes it possible to produce H263 in RFC2190 format with chained RTP muxers. CC: libav-stable@libav.org Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 28 Nov, 2012 1 commit
-
-
Diego Biurrun authored
-
- 14 Nov, 2012 1 commit
-
-
Luca Barbato authored
Support multiple video/audio streams with different format in the same session. Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
-
- 26 May, 2012 2 commits
-
-
Martin Storsjö authored
Also check the return value in sapenc. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
If an URLContext is passed in, its ownership is given to this function, and is either owned by the returned AVFormatContext on a successful return, or freed on failure. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 28 Jan, 2012 1 commit
-
-
Alex Converse authored
-
- 13 Nov, 2011 1 commit
-
-
Martin Storsjö authored
There are a few more cases of chained demuxers, but they only use custom IO which don't do any blocking IO and thus don't need the callback.
-
- 19 Oct, 2011 1 commit
-
-
Anton Khirnov authored
Trivial replacements with sed are done in this commit: sed 's/av_new_stream(\([^)]*\), 0)/avformat_new_stream(\1, NULL)/'
-
- 12 Oct, 2011 1 commit
-
-
Anton Khirnov authored
-
- 16 Jun, 2011 1 commit
-
-
Anton Khirnov authored
It supports more convenient setting of AVOptions.
-
- 10 Jun, 2011 1 commit
-
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 19 May, 2011 1 commit
-
-
Martin Storsjö authored
-
- 03 Apr, 2011 3 commits
-
-
Anton Khirnov authored
The unbuffered URLContext API will be made private, so there's no point in this function being public.
-
Anton Khirnov authored
It doesn't look fit to be a part of the public API. Adding a temporary hack to ffserver to be able to use it, should be cleaned up when somebody is up for it.
-
Anton Khirnov authored
-
- 19 Mar, 2011 1 commit
-
-
Mans Rullgard authored
Signed-off-by: Mans Rullgard <mans@mansr.com>
-
- 23 Feb, 2011 2 commits
-
-
Anton Khirnov authored
Signed-off-by: Ronald S. Bultje <rsbultje@gmail.com> (cherry picked from commit 22a3212e)
-
Anton Khirnov authored
Signed-off-by: Ronald S. Bultje <rsbultje@gmail.com>
-
- 06 Feb, 2011 3 commits
-
-
Martin Storsjö authored
If required, the caller can do this itself. ff_write_chained rescales timestamps as necessary, and all current callers of rtpenc_chain use ff_write_chained, making this timebase copy unnecessary. Signed-off-by: Ronald S. Bultje <rsbultje@gmail.com> (cherry picked from commit 397ffde1)
-
Martin Storsjö authored
Signed-off-by: Ronald S. Bultje <rsbultje@gmail.com> (cherry picked from commit b22dbb29)
-
Martin Storsjö authored
This avoids having the chained AVStream->codec point to the same AVCodecContext owned by the outer AVStream. The downside is that changes to the AVCodecContext made after calling av_write_header cannot be detected automatically within the chained muxer. This avoids having to manually unlink the chained AVStream->codec by setting it to null before freeing the chained muxer via generic freeing functions. Signed-off-by: Ronald S. Bultje <rsbultje@gmail.com> (cherry picked from commit 1338dc08)
-
- 04 Feb, 2011 4 commits
-
-
Martin Storsjö authored
If required, the caller can do this itself. ff_write_chained rescales timestamps as necessary, and all current callers of rtpenc_chain use ff_write_chained, making this timebase copy unnecessary. Signed-off-by: Ronald S. Bultje <rsbultje@gmail.com>
-
Martin Storsjö authored
Signed-off-by: Ronald S. Bultje <rsbultje@gmail.com>
-
Martin Storsjö authored
This avoids having the chained AVStream->codec point to the same AVCodecContext owned by the outer AVStream. The downside is that changes to the AVCodecContext made after calling av_write_header cannot be detected automatically within the chained muxer. This avoids having to manually unlink the chained AVStream->codec by setting it to null before freeing the chained muxer via generic freeing functions. Signed-off-by: Ronald S. Bultje <rsbultje@gmail.com>
-
Martin Storsjö authored
This fixes memory leaks in the RTSP muxer and RTP hinting in the mov muxer present since SVN rev 25418. Signed-off-by: Luca Barbato <lu_zero@gentoo.org> (cherry picked from commit ce41c51b)
-
- 03 Feb, 2011 1 commit
-
-
Martin Storsjö authored
This fixes memory leaks in the RTSP muxer and RTP hinting in the mov muxer present since SVN rev 25418. Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
-
- 08 Oct, 2010 1 commit
-
-
Martin Storsjö authored
The new object file is added to the SDP demuxer in the makefile, since it is needed in both the RTSP muxer and demuxer and in the SDP demuxer, due to the current code coupling. Originally committed as revision 25410 to svn://svn.ffmpeg.org/ffmpeg/trunk
-