Extended timestamp field may be present in type 3 chunk headers
commit79459a2b43f41ac44a2ec001139bcb7b1b8f7497
authorMartin Panter <vadmium à gmail·com>
Wed, 18 Sep 2013 01:58:01 +0000 (18 11:58 +1000)
committerMartin Storsjo <martin@martin.st>
Sun, 2 Mar 2014 18:20:23 +0000 (2 20:20 +0200)
tree731e5fa2bf53dbce7e6e2c4c8d6a4b4ae77d123c
parentdc76f0a8461e6c8f1277eba58eae201b2dc1d06a
Extended timestamp field may be present in type 3 chunk headers

As described in Adobe’s RTMP specification dated 21 Dec 2012; also:

* RTMPY ticket #107, “Compressed headers also can have an extended
  timestamp”,
  http://web.archive.org/web/20120624031323/http://dev.rtmpy.org/ticket/107
* https://rarut.wordpress.com/2012/03/21/announcing-nginx-rtmp-module/

This resolves intermittent hangs, segfaults and crashes I was seeing when
starting ABC News 24 streams, e.g.:

rtmpdump -r rtmp://cp81899.live.edgefcs.net/live/news24-med@28772 --live

Some of the packets seemed to contain junk timestamp fields, which often
required the extended field.
librtmp/rtmp.c