From c7e8639c70ec25be2c0afdcea61d992de5f1928e Mon Sep 17 00:00:00 2001 From: Martin Storsjö Date: Fri, 17 Feb 2012 10:27:41 +0200 Subject: rtpdec: Identify incorrectly signalled H263 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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ö --- libavformat/rtpdec_formats.h | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'libavformat/rtpdec_formats.h') diff --git a/libavformat/rtpdec_formats.h b/libavformat/rtpdec_formats.h index 7f18ca4104..60edecb4ed 100644 --- a/libavformat/rtpdec_formats.h +++ b/libavformat/rtpdec_formats.h @@ -31,6 +31,10 @@ */ int ff_wms_parse_sdp_a_line(AVFormatContext *s, const char *p); +int ff_h263_handle_packet(AVFormatContext *ctx, PayloadContext *data, + AVStream *st, AVPacket *pkt, uint32_t *timestamp, + const uint8_t *buf, int len, int flags); + extern RTPDynamicProtocolHandler ff_amr_nb_dynamic_handler; extern RTPDynamicProtocolHandler ff_amr_wb_dynamic_handler; extern RTPDynamicProtocolHandler ff_g726_16_dynamic_handler; -- cgit v1.2.3