[rtmpdump] patch: Stream does not start with requested frame, ignoring data

Peter Miller pmiller at opensource.org.au
Sat Apr 9 11:34:14 CEST 2011

On Fri, 2011-04-08 at 19:56 -0700, Howard Chu wrote:
> Peter Miller wrote:
> It turns out that the server is sending RTMP_PACKET_TYPE_AUDIO
> > and RTMP_PACKET_TYPE_VIDEO packets (and the video packets *do* contain a
> > key frame), rather than librtmp/rtmp.c Read_1_packet()'s expectation of
> >
> > Howard, what would be your preferred way to handle this case?
> Sorry, your problem description makes no sense. Regular video/audio packets 
> are checked for the keyframe already, line 3837. Explain first why this check 
> failed, don't go mucking with everything afterward, that's irrelevant.

The server does send the expected packet type
(r->m_read.initialFrameType == RTMP_PACKET_TYPE_VIDEO) but it does not
send the expected packet size (r->m_read.nInitialFrameSize = 17957,
nPacketLen = 592).  This causes it to fall into the code that expects a

Peter Miller <pmiller at opensource.org.au>
/\/\*        http://miller.emu.id.au/pmiller/

PGP public key ID: 1024D/D0EDB64D
fingerprint = AD0A C5DF C426 4F03 5D53  2BDB 18D8 A4E2 D0ED B64D
See http://www.keyserver.net or any PGP keyserver for public key.

"C++: an octopus made by nailing extra legs onto a dog." -- Steve Taylor

More information about the rtmpdump mailing list