- 05 Mar, 2015 1 commit
-
-
Thomas Volkert authored
The code was tested with live555 server. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 24 Feb, 2015 2 commits
-
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 22 Feb, 2015 1 commit
-
-
Thomas Volkert authored
(tested with live555 RTSP server) Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 21 Feb, 2015 3 commits
-
-
Gilles Chanteperdrix authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
Gilles Chanteperdrix authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 15 Feb, 2015 2 commits
-
-
Thomas Volkert authored
Tested with live555 RTSP server Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
Thomas Volkert authored
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 14 Feb, 2015 2 commits
-
-
Gilles Chanteperdrix authored
Signed-off-by: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> Reviewed-by: Thomas Volkert <silvo@gmx.net> Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
Gilles Chanteperdrix authored
Reviewed-by: Thomas Volkert <silvo@gmx.net> Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 18 Dec, 2014 1 commit
-
-
Thomas Volkert authored
The packetizer only supports splitting at GOB headers - if such aren't available frequently enough, it splits at any random byte offset (not at a macroblock boundary either, which would be allowed by the spec) and sends a payload header pretend that it starts with a GOB header. As long as a receiver doesn't try to handle such cases cleverly but just drops broken frames, this shouldn't matter too much in practice. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 24 Sep, 2014 1 commit
-
-
Vittorio Giovara authored
The RFC spec draft only specifies the "H265" name - there is no specification saying how to interpret "HEVC" (if such a packet format is specified it could be an entirely different format). Since this is a very new standard (still a draft), there is little need for compatibility with existing, broken implementations. Therefore remove the extra alias, to avoid the risk of encouraging incorrect usage. Intentionally keeping the ff_hevc_dynamic_handler name for the handler, to use "hevc" consistently as name for the codec instead of "h265" within the library internals as long as there only is one single variant in actual use. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 03 Sep, 2014 1 commit
-
-
Thomas Volkert authored
As specified in draft-ietf-payload-rtp-h265-06. Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
-
- 26 Aug, 2014 1 commit
-
-
ThomasVolkert authored
-
- 24 Aug, 2014 1 commit
-
-
ThomasVolkert authored
-
- 20 Jan, 2013 2 commits
-
-
Martin Storsjö authored
This also adds checking of mallocs. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This gets rid of a number of special cases from the common rtpdec code. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 21 Dec, 2012 1 commit
-
-
Martin Storsjö authored
This allows depacketizers to figure out if packets have been lost. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 23 Sep, 2012 1 commit
-
-
Dmitry Samonenko authored
RTPDynamicProtocolHandler for speex is added. Initial support for speex depacketization from RTP stream comes with it. Currently, only codec audio rate can be applied based on sdp: * Narrowband ( 8K) * Wideband (16K) * Ultrawideband (32K) Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 09 Sep, 2012 1 commit
-
-
Samuel Pitoiset authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 18 Jun, 2012 1 commit
-
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 18 Feb, 2012 1 commit
-
-
Martin Storsjö authored
H263 in RTP can be packetized in two formats (RFC 2190, RFC 2429/4629). The former normally uses the static payload type 34, while the latter normally uses dynamic payload types with the SDP format names H263-1998 or H263-2000. Look for packets that don't look like proper RFC 2190 packets and switch to depacketizing them according to the new format if they match some heuristic criteria. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 14 Feb, 2012 1 commit
-
-
Martin Storsjö authored
This is different from the "modern" RTP payload formats for H263 as defined by RFC 4629, 2429 and 3555. According to the newer RFCs, this old one is to be considered deprecated and only be used for interoperating with legacy systems. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 30 Nov, 2011 1 commit
-
-
Miroslav Slugeň authored
This requires using a separate init function, since there isn't necessarily any fmtp lines for this codec, so parse_sdp_a_line won't be called. Incorporating it with the alloc function wouldn't do either, since it is called before the full rtpmap line is parsed (where the sample rate is extracted). Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 07 Nov, 2011 1 commit
-
-
Miroslav Slugeň authored
Fixes Ticket611 Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 19 Mar, 2011 1 commit
-
-
Mans Rullgard authored
Signed-off-by: Mans Rullgard <mans@mansr.com>
-
- 05 Dec, 2010 1 commit
-
-
Martin Storsjö authored
This fixes roundup issue 2390. Originally committed as revision 25889 to svn://svn.ffmpeg.org/ffmpeg/trunk
-
- 06 Oct, 2010 1 commit
-
-
Martin Storsjö authored
Originally committed as revision 25371 to svn://svn.ffmpeg.org/ffmpeg/trunk
-
- 16 Aug, 2010 1 commit
-
-
Josh Allmann authored
Patch by Josh Allmann, joshua dot allmann at gmail Originally committed as revision 24798 to svn://svn.ffmpeg.org/ffmpeg/trunk
-
- 12 Aug, 2010 1 commit
-
-
Martin Storsjö authored
Originally committed as revision 24790 to svn://svn.ffmpeg.org/ffmpeg/trunk
-
- 30 Jul, 2010 1 commit
-
-
Martin Storsjö authored
Originally committed as revision 24596 to svn://svn.ffmpeg.org/ffmpeg/trunk
-