<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Thanks for the specific suggestions, Ross. <br>
<br>
One question, though: Why SimpleRTPSource
vs. MPEG1or2VideoRTPSource? <br>
<br>
We don't yet have the VBRICK mpeg2 appliance in hand, but I believe
that it does put out mpeg2 encoded data, and may offer a multicast or
unicast stream option. We should be able to find out more once we can
command it using their web or SNMP interfaces, and and can look on the
wire.<br>
<br>
It seems to have an option to do SAP, but i have heard that the VBRICK
SAP is somewhat proprietary and is only intended for other vbrick
devices. Does this mean we will need to hand code a local sdp file for
each video source?<br>
<br>
BTW, OpenRTSP does support a rich set of options which just about meet
our other requirements.<br>
<br>
Thanks for the example programs and the tips on which ones apply to our
situation.<br>
<br>
<br>
Regards,<br>
<br>
Mike<br>
<br>
<br>
<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:live-devel-request@ns.live555.com">live-devel-request@ns.live555.com</a> wrote:
<blockquote
cite="mid:mailman.14508.1228318608.846.live-devel@lists.live555.com"
type="cite">
<pre wrap="">Send live-devel mailing list submissions to
        <a class="moz-txt-link-abbreviated" href="mailto:live-devel@lists.live555.com">live-devel@lists.live555.com</a>
To subscribe or unsubscribe via the World Wide Web, visit
        <a class="moz-txt-link-freetext" href="http://lists.live555.com/mailman/listinfo/live-devel">http://lists.live555.com/mailman/listinfo/live-devel</a>
or, via email, send a message with subject or body 'help' to
        <a class="moz-txt-link-abbreviated" href="mailto:live-devel-request@lists.live555.com">live-devel-request@lists.live555.com</a>
You can reach the person managing the list at
        <a class="moz-txt-link-abbreviated" href="mailto:live-devel-owner@lists.live555.com">live-devel-owner@lists.live555.com</a>
When replying, please edit your Subject line so it is more specific
than "Re: Contents of live-devel digest..."
Today's Topics:
1. Re: Recording an mp2 rtp stream for playback by Live555 media
server (Ross Finlayson)
2. Re: Multicast session question (Yedidia Amit)
3. HTTP Tunnelling (Anita Rajan)
4. How can I stream g711(ulaw PCM) audio via RTP? There        is no
demo application for this. (srinivasa rao)
5. Re: How can I stream g711(ulaw PCM) audio via RTP? There is
no demo application for this. (Ross Finlayson)
6. problems with New FramedSource creation (anand meher)
7. Re: problems with New FramedSource creation (Ross Finlayson)
8. Re: problems with New FramedSource creation (anand meher)
----------------------------------------------------------------------
Message: 1
Date: Mon, 1 Dec 2008 17:05:49 -0800
From: Ross Finlayson <a class="moz-txt-link-rfc2396E" href="mailto:finlayson@live555.com"><finlayson@live555.com></a>
Subject: Re: [Live-devel] Recording an mp2 rtp stream for playback by
        Live555 media server
To: LIVE555 Streaming Media - development & use
        <a class="moz-txt-link-rfc2396E" href="mailto:live-devel@ns.live555.com"><live-devel@ns.live555.com></a>
Message-ID: <a class="moz-txt-link-rfc2396E" href="mailto:f06240817c55a38b87154@[66.80.62.44]"><f06240817c55a38b87154@[66.80.62.44]></a>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
</pre>
<blockquote type="cite">
<pre wrap="">Given video encoded as mpeg2 transported over RTP from a Vbrick
appliance ( model 9110-4200), we need to record data as a series of
mpege2 TS chapter files of fixed duration that may subsequently be
played back using Live555 media server. We hope to support trick
mode, as well.
Before realizing that the Vbrick mp2 appliance does not apparently
support RTSP ( although their mpeg4 device does) we had thought to
use OpenRTSP as a ( nearly complete) starting point for recording.
</pre>
</blockquote>
<pre wrap=""><!---->
If your server doesn't support RTSP, then there seems to be little
point in using "openRTSP" as a model for your client, because RTSP is
most of what "openRTSP" does.
Instead, you can just use "testMPEG1or2VideoReceiver" as a model.
Just use a "SimpleRTPSource" instead of a "MPEG1or2VideoRTPSource".
See line 751 of "liveMedia/MediaSession.cpp" for an example of how to
use this.
</pre>
</blockquote>
<br>
</body>
</html>