Hello, As far as I can see the 1st audio packet is a 12-byte header packet, followed by 4 byte header audio packets. The chunking performed in these packets looks completely borked in the ethereal dumps I've made, unlike the chunking for video packets. Let me explain: the 1st audio packet has a header of 0x04, which means 12 bytes channel 4. Subsequent packets have a header of 0x84 which means 4 bytes channel 4. These packets however don't make any sense, as at the 128 byte mark (nor anywhere in the vicinity) is a 0xC4 'continue' packet header, as expected and found for instance in the chunking of video packets (though they use channel 6, therefore 0x06 and chunked by 0xC6). Trying to stream audio packets in full 12 byte header packages leads to large leaking in the Flash player, but _only_ when audio is sent. Video doesn't exhibit this issue. The packages are properly formatted as they play just fine and both FMS and Red5 do not trigger exceptions on parsing and routing the input stream. Any explanation why, or how does this happen?
As a side note, and I don't mean to offend anyone really, this is hardly the first time I've sent a message to this list asking questions about how RTMP works that would eventually go unanswered, which I think it's a shame really, as it seems that the Red5 developers are not very keen on answering questions about the protocol. Considering that the RTMP protocol is proprietary and therefore the main obstacle in allowing someone to build apps based on it, I believe that making sure the protocol is understood and available to all parties interested should be the first and foremost concern of any OS project involving it. Thank you for your consideration, Kind regards, -- Radu-Adrian Popescu CSA,DBA,Programmer Generius Ltd. +40723335573 _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
