<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
FYI, <br>
I don't know what he has but it is possible that the data is encoded
in a separate stream in SMPTE KLV format. This data format is the
standard used by MISB (Motion Industry Standards Board) which is an
off shoot of military UAV programs. <br>
They have a standard for encoding KLV (Key Length Value) meta-data
(GPS, heading, platform attitude, etc) in MPEG2 transport streams.
They also have a draft standard for sending this this meta data as a
RTP stream (<a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-arbeiter-rtp-klv-00">http://tools.ietf.org/html/draft-arbeiter-rtp-klv-00</a>). <br>
<br>
I've done some work in this area, i.e. I'm sending KLV meta-data in
a RTP stream with my video but it's not according to the MISB
standard (I did mine before they wrote their standard) however my
video source is a live camera not a MPEG2 transport stream so I
haven't done the transport stream de-muxing part. <br>
<br>
In the near future I hope to update our code to use the draft
standard and at that time I'd like to push the code back to the
LiveMedia code base but I don't know when that work will happen. <br>
<br>
Regards, <br>
Matt S. <br>
<br>
On 8/8/2011 10:21 PM, Ross Finlayson wrote:
<blockquote
cite="mid:A8903638-51F1-41EA-9478-7001EAE6D0DF@live555.com"
type="cite"><base href="x-msg://6611/"><br>
<div>
<div>On Aug 8, 2011, at 7:45 PM, Pardridge, Robert wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><span class="Apple-style-span"
style="border-collapse: separate; font-family: Helvetica;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px;
-webkit-border-vertical-spacing: 0px;
-webkit-text-decorations-in-effect: none;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width:
0px; font-size: medium; ">
<div link="blue" vlink="purple" lang="EN-US">
<div class="WordSection1" style="page: WordSection1; ">
<div style="margin-top: 0in; margin-right: 0in;
margin-left: 0in; margin-bottom: 0.0001pt; font-size:
11pt; font-family: Calibri, sans-serif; ">I want to
stream video via RTSP, where the container has 2
streams, one is video and the other is data. I can
stream just fine with live555 a video with just video,
but if there is a data stream I get the message “Saw
unexpected code” which I traced back to
MPEG1or2VideoStreamFramer.cpp<o:p></o:p></div>
<div style="margin-top: 0in; margin-right: 0in;
margin-left: 0in; margin-bottom: 0.0001pt; font-size:
11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div>
<div style="margin-top: 0in; margin-right: 0in;
margin-left: 0in; margin-bottom: 0.0001pt; font-size:
11pt; font-family: Calibri, sans-serif; ">I was
wondering how I could modify the live555 library to
send the data stream as well as the video stream.</div>
</div>
</div>
</span></blockquote>
</div>
<br>
<div>There are a couple of issues here:</div>
<div><br>
</div>
<div>1/ How is the metadata stored within the MPEG Program Stream
file? If it's stored in PES packets - with a well-defined
stream_id for 'metadata' - then it could probably be extracted
in the same way that audio and video is extracted, by modifying
the "MPEG1or2Demux" code. If, however, the metadata is stored
within the video stream (which is suggested by the "Saw
unexpected code" error), then extracting it would be harder.</div>
<div><br>
</div>
<div>2/ (The big issue) What RTP payload format would you use to
stream this metadata? There probably isn't one defined, which
means that you'd need to define your own. But then you'd have
the problem of no standard receiver being able to understand the
metadata stream.</div>
<div><br>
</div>
<div>In any case, it would be useful to see an example file that
contains 'metadata'. Please put an example on a web server, and
send a link to it, so we can download and test it for ourselves.</div>
<br>
<br>
<div>
<span class="Apple-style-span" style="border-collapse: separate;
color: rgb(0, 0, 0); font-family: Helvetica; font-style:
normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: 2;
text-align: -webkit-auto; text-indent: 0px; text-transform:
none; white-space: normal; widows: 2; word-spacing: 0px;
-webkit-border-horizontal-spacing: 0px;
-webkit-border-vertical-spacing: 0px;
-webkit-text-decorations-in-effect: none;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width:
0px; font-size: medium; "><span class="Apple-style-span"
style="border-collapse: separate; color: rgb(0, 0, 0);
font-family: Helvetica; font-style: normal; font-variant:
normal; font-weight: normal; letter-spacing: normal;
line-height: normal; orphans: 2; text-align: -webkit-auto;
text-indent: 0px; text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px;
-webkit-border-horizontal-spacing: 0px;
-webkit-border-vertical-spacing: 0px;
-webkit-text-decorations-in-effect: none;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width:
0px; font-size: medium; ">Ross Finlayson<br>
Live Networks, Inc.<br>
<a moz-do-not-send="true" href="http://www.live555.com/">http://www.live555.com/</a></span></span>
</div>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
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>