<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
What's wrong with putting your meta-data in another stream that is time
synchronized with the H264 stream. I believe that is the intended way
to do such a thing in RTP. <br>
<br>
Just curious,<br>
Matt S. <br>
<br>
Yedidia Amit wrote:
<blockquote
cite="mid:EB34B5A39CF26E408490ED9279BF10A71D3641@mailesl5.esl.corp.elbit.co.il"
type="cite">
<title>Re: [Live-devel] RTP Extension</title>
<meta http-equiv="Content-Type" content="text/html; ">
<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">
<div><span class="039390709-30102008"><font color="#0000ff"
face="Arial" size="2">I mean to RTP Header Extension. and thank you
for your answer.</font></span></div>
<div><span class="039390709-30102008"></span> </div>
<div><span class="039390709-30102008"><font color="#0000ff"
face="Arial" 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 color="#0000ff"
face="Arial" 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 color="#0000ff"
face="Arial" 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 color="#0000ff"
face="Arial" 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:
<a class="moz-txt-link-abbreviated" href="mailto:amit.yedidia@elbitsystems.com">amit.yedidia@elbitsystems.com</a></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="border-left: 2px solid rgb(0, 0, 255); padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div class="OutlookMessageHeader" dir="ltr" align="left"
lang="en-us">
<hr tabindex="-1"> <font face="Tahoma" size="2"><b>From:</b>
<a class="moz-txt-link-abbreviated" href="mailto:live-devel-bounces@ns.live555.com">live-devel-bounces@ns.live555.com</a>
[<a class="moz-txt-link-freetext" href="mailto:live-devel-bounces@ns.live555.com">mailto:live-devel-bounces@ns.live555.com</a>] <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>
<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></X-SIGSEP>
<pre>--
</pre>
<div><br>
Ross Finlayson<br>
Live Networks, Inc.<br>
<a class="moz-txt-link-freetext" href="http://www.live555.com/">http://www.live555.com/</a></div>
</blockquote>
<div><strong></strong> </div>
<div align="left"><strong><font color="#000080" face="Arial" 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>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
live-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:live-devel@lists.live555.com">live-devel@lists.live555.com</a>
<a class="moz-txt-link-freetext" href="http://lists.live555.com/mailman/listinfo/live-devel">http://lists.live555.com/mailman/listinfo/live-devel</a>
</pre>
</blockquote>
</body>
</html>