<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1" style="">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 13px;">
<div style="">The containers using RTSP already define stream types for meta data beyond Video and Audio. Often used for analytics data for security camera video for example. Is this what we are talking about?<br>
</div>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF884861"><font color="#000000" face="Tahoma" size="2"><b>From:</b> live-devel-bounces@ns.live555.com [live-devel-bounces@ns.live555.com] on behalf of Ross Finlayson [finlayson@live555.com]<br>
<b>Sent:</b> Wednesday, January 16, 2013 9:04 AM<br>
<b>To:</b> LIVE555 Streaming Media - development & use<br>
<b>Subject:</b> Re: [Live-devel] RTP header extension<br>
</font><br>
</div>
<div></div>
<div>
<div>
<blockquote type="cite">
<div style="" lang="FR">
<div class="Section1" style="">
<div style=""><span style="font-size:11pt; font-family:Calibri,sans-serif; color:rgb(31,73,125)">I guess this could be interesting to carry information inside the stream independandly of codec used.</span></div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>That might be "interesting", but not necessarily appropriate. It depends on what sort of 'information' this is. The use of a RTP header extension is appropriate ***only if*** the information is directly related to the RTP packets (not just the stream
as a whole). For example, one can imagine some RTP packets carrying an extra timestamp (e.g., a 'decoding timestamp'), in addition to the usual RTP timestamp (from which a 'presentation timestamp' is derived). </div>
<div><br>
</div>
If the 'information' is static, and unchanging, then it could be put in the stream's SDP description (e.g., the 'info' or 'description' SDP lines). There are (optional) parameters to "ServerMediaSession::createNew()" to provide this information, and also -
at the receiving end - member functions of "MediaSession" to get this information:</div>
<div><span class="Apple-tab-span" style="white-space:pre"></span>sessionName();</div>
<div><span class="Apple-tab-span" style="white-space:pre"></span>sessionDescription();</div>
<div><br>
</div>
<div>Another way to get information that's static (or doesn't change much) is to use the RTSP "GET_PARAMETER" command, as you've done.</div>
<div><br>
</div>
<div>For information that is time-based - i.e., changes over time - but is not directly related to an existing media stream (i.e., the audio or video stream) - then the information could itself be its own RTP media stream - e.g., using the "text" media type.
Note, for example, that we support time-varying T.140 text streams over RTP, using the class "T140TextRTPSink". (That's used for transmitting text over RTP; for receiving such streams, we just use "SimpleRTPSource".) We use such streams to transmit the 'subtitle'
tracks from Matroska files (and VLC, when used as a RTP receiver, will also display these as subtitles).</div>
<br>
<br>
<div><span class="Apple-style-span" style=""><span class="Apple-style-span" style="">Ross Finlayson<br>
Live Networks, Inc.<br>
<a href="http://www.live555.com/" target="_blank">http://www.live555.com/</a></span></span>
</div>
<br>
</div>
</div>
</div>
</body>
</html>