summaryrefslogtreecommitdiff
path: root/libavformat/rtpdec_h263_rfc2190.c
Commit message (Collapse)AuthorAgeFilesLines
* Replace all CODEC_ID_* with AV_CODEC_ID_*Anton Khirnov2012-08-071-1/+1
|
* rtpdec: Don't require frames to start with a Mode A packetMartin Storsjö2012-06-141-1/+1
| | | | | | | | While there is no reason for starting a frame with anything else than a Mode A packet, some senders seem to consistently use Mode B packets for everything. This fixes depacketization of such streams. Signed-off-by: Martin Storsjö <martin@martin.st>
* rtpdec: Identify incorrectly signalled H263Martin Storsjö2012-02-181-1/+23
| | | | | | | | | | | | | 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>
* rtpdec: Support H263 in RFC 2190 formatMartin Storsjö2012-02-141-0/+184
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>