summaryrefslogtreecommitdiff
path: root/libavformat/rtpdec_formats.h
diff options
context:
space:
mode:
authorMartin Storsjö <martin@martin.st>2012-02-17 10:27:41 +0200
committerMartin Storsjö <martin@martin.st>2012-02-18 17:31:55 +0200
commitc7e8639c70ec25be2c0afdcea61d992de5f1928e (patch)
treeda775477a4893a730b9da3a361840b5d20f78eb1 /libavformat/rtpdec_formats.h
parentb1af4e9c27e2cd4a7deab26b88feae8490d673ba (diff)
rtpdec: Identify incorrectly signalled H263
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>
Diffstat (limited to 'libavformat/rtpdec_formats.h')
-rw-r--r--libavformat/rtpdec_formats.h4
1 files changed, 4 insertions, 0 deletions
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;