[rtmpdump] patch: Stream does not start with requested frame, ignoring data
pmiller at opensource.org.au
Sat Apr 9 12:38:53 CEST 2011
On Sat, 2011-04-09 at 02:45 -0700, Howard Chu wrote:
> Peter Miller wrote:
> > 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
> > RTMP_PACKET_TYPE_FLASH_VIDEO frame.
> Then the server is lying to you about something. I don't believe your video
> keyframe can be only 592 bytes, especially not if the actual last keyframe in
> the file was 17KB.
Something is definitely strange, however my browser manages to play it
without difficulty. However, that's what's happening, now the code has
to cope. Just got to figure out how.
Peter Miller <pmiller at opensource.org.au>
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.
Real computer scientists despise the idea of actual hardware. Hardware
has limitations, software doesn't. It's a real shame that Turing
machines are so poor at I/O.
More information about the rtmpdump