<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Re: [Live-devel] RTP Extension</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<STYLE type=text/css>BLOCKQUOTE {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
DL {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
UL {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
OL {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
LI {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px
}
</STYLE>
<META content="MSHTML 6.00.2900.3268" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=039390709-30102008><FONT face=Arial color=#0000ff size=2>I mean
to RTP Header Extension. and thank you for your answer.</FONT></SPAN></DIV>
<DIV><SPAN class=039390709-30102008><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=039390709-30102008><FONT face=Arial color=#0000ff size=2>what I
am trying to do is adding meta data per frame to a H264 RFC3984
stream.</FONT></SPAN></DIV>
<DIV><SPAN class=039390709-30102008><FONT face=Arial color=#0000ff
size=2>another way which cross my mind is to put this meta data in NAL with
unspecified NAL type (24-31).</FONT></SPAN></DIV>
<DIV><SPAN class=039390709-30102008><FONT face=Arial color=#0000ff size=2>But I
need it to interop with clients which dont support my meta data. (they just need
to ignore this data)</FONT></SPAN></DIV>
<DIV><SPAN class=039390709-30102008><FONT face=Arial color=#0000ff size=2>Do you
think it will do the job?</FONT></SPAN></DIV>
<DIV> </DIV><!-- Converted from text/rtf format -->
<P dir=ltr><SPAN lang=en-us><FONT face=Arial
size=2>Regards,</FONT></SPAN></P><BR>
<P dir=ltr><SPAN lang=en-us><FONT face=Arial size=2>Amit
Yedidia</FONT></SPAN></P>
<P dir=ltr><SPAN lang=en-us><FONT face=Arial size=2>Elbit System
Ltd.</FONT></SPAN></P>
<P dir=ltr><SPAN lang=en-us><FONT face=Arial size=2>Email:
amit.yedidia@elbitsystems.com</FONT></SPAN></P>
<P dir=ltr><SPAN lang=en-us><FONT face=Arial size=2>Tel:
972-4-8318905</FONT></SPAN></P>
<P dir=ltr><SPAN lang=en-us><FONT face=Arial
size=2>----------------------------------------------------------</FONT></SPAN></P>
<P dir=ltr><SPAN lang=en-us></SPAN><SPAN lang=he></SPAN></P>
<DIV> </DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> live-devel-bounces@ns.live555.com
[mailto:live-devel-bounces@ns.live555.com] <B>On Behalf Of </B>Ross
Finlayson<BR><B>Sent:</B> Thursday, October 30, 2008 10:47 AM<BR><B>To:</B>
LIVE555 Streaming Media - development & use<BR><B>Subject:</B> Re:
[Live-devel] RTP Extension<BR></FONT><BR></DIV>
<DIV></DIV>
<BLOCKQUOTE cite="" type="cite"><FONT face=Arial size=-1>What is the proper
way to imlement adding RTP extension in Live555?</FONT></BLOCKQUOTE>
<DIV><BR>it depends what you mean by "RTP extension".</DIV>
<DIV><BR></DIV>
<DIV>If you're referring to just implementing a new RTP payload format, then
this is easy - just define and implement your own subclasses of
"MultiFramedRTPSink" (for sending) and "MultiFramedRTPSource" (for
receiving).</DIV>
<DIV><BR></DIV>
<DIV>If, however, you're referring to implementing RTP *header* extensions (as
defined in RFC 3550, section 5.3.1), then there's currently no clean way to do
this; instead, you would need to modify the existing "MultiFramedRTPS*.cpp"
code to support this.</DIV><X-SIGSEP><PRE>--
</PRE></X-SIGSEP>
<DIV><BR>Ross Finlayson<BR>Live Networks,
Inc.<BR>http://www.live555.com/</DIV></BLOCKQUOTE>
<DIV><STRONG><FONT color=#000080 size=2></FONT></STRONG> </DIV>
<DIV align=left><STRONG><FONT face=Arial color=#000080 size=2>The information in
this e-mail transmission contains proprietary and business <BR>sensitive
information. Unauthorized interception of this e-mail may constitute <BR>a
violation of law. If you are not the intended recipient, you are hereby
<BR>notified that any review, dissemination, distribution or duplication of this
<BR>communication is strictly prohibited. You are also asked to contact the
sender <BR>by reply email and immediately destroy all copies of the original
message.<BR></FONT></STRONG></DIV>
</BODY></HTML>