On 6/2/06, Radu-Adrian Popescu <[EMAIL PROTECTED]> wrote:
Well, AFAIK there's another type of RTMP packet to control the actual chunk size whose default value is 128 bytes.
Red5 does not parse any of the video data. During streaming, it simply extracts the content from FLV (stripping the header) and sends to client.
Luke Hubbard wrote:
> Hi,
>
Hi Luke,
> Couple of things.. first dont read the MM spec.
> If you do you cannot create server or client. So you are limited to tools.
> http://www.osflash.org/flv has info on flv format.
>
Thanks, I've read the license agreement and decided not to read it. You can create clients
as far as I understood, though.
> The size difference is likely to be the chunking bytes.
> This is described in the documentation joachim pointed you to.
> Only where it says "The AMF", mick was talking about RTMP.
> RTMP packets are split into 128 byte chunks (by default).
> In between each chunk there is another header.
> Normally this is a 1 byte continue header, but it can be longer.
>
Right, thing is I can't seem to find any relation between bytes located at 128 offset
increments. Are they supposed to be the same byte?
Well, AFAIK there's another type of RTMP packet to control the actual chunk size whose default value is 128 bytes.
What does Red5 do when dealing with video data? Does it parse it back into FLV, i.e.
without the chunking bytes? If so could you point out relevant code in Red5?
Red5 does not parse any of the video data. During streaming, it simply extracts the content from FLV (stripping the header) and sends to client.
> Hope that helps.
> - Luke
>
Thank you very much,
--
Radu-Adrian Popescu
CSA, DBA, Developer
Aldrapay MD
Aldratech Ltd.
+40213212372
_______________________________________________
Red5 mailing list
Red5@osflash.org
http://osflash.org/mailman/listinfo/red5_osflash.org
--
Best Regards
Steven Gong
_______________________________________________ Red5 mailing list Red5@osflash.org http://osflash.org/mailman/listinfo/red5_osflash.org
