<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-2">
<META content="MSHTML 6.00.2900.2180" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Each packet passed
to ProcessSpecialHeader() is prefixed with 001 but I noticed that
for this functions the first byte in a packet is always a NAL type, so it always
reads NAL of type 0. I'm not sure but it doesn't look like RFC 3984.
Maybe is this a some separate standard of streaming, which is not
supported by LiveMedia ? </FONT></DIV>
<DIV><FONT face=Arial size=2>Why 224.0.0.x multicast addresses dont work in
LiveMedia ? This camera has a default multicast address in 224.0.0.x
group, which is, for some unknown reasons, blocked out in LiveMedia. I've
made changes to IsMulticastAddress(), and now it is working fine, but I don't
know if this modification won't have some side
effects. </FONT></DIV>
<DIV><FONT face=Arial size=2>And a one more general question, what would be the
best way to transform the unit h264 stream ( without prefixes ) into a byte
stream ( with NAL prefixes ) without parsing a whole media stream. Is there any
requirement that one rtp packet can contain at most one NAL unit ? If
not, how to detect a packets which contains more than one NAL unit ? How to find
NAL unit boundaries in such packets ?</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Regards,</FONT></DIV>
<DIV><FONT face=Arial size=2>Kamil </FONT></DIV></BODY></HTML>