<div dir="ltr"><div dir="ltr">better description is our "server process" embeds "rtsp server" and "video player".<br>another process on the same machine acts as a "rtsp client" for "playback control" without receiving rtp packets.<br>because "rtsp server" and "video player" code runs in the same process no need to send the packets over a socket.<br>if a "local video sink" implementation handles "rtcp reception reports" (session timeout prevention) this can work?<br><br>thanks,<br>gerald<br></div><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jun 15, 2020 at 9:00 PM <<a href="mailto:live-devel-request@us.live555.com">live-devel-request@us.live555.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send live-devel mailing list submissions to<br>
<a href="mailto:live-devel@lists.live555.com" target="_blank">live-devel@lists.live555.com</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.live555.com/mailman/listinfo/live-devel" rel="noreferrer" target="_blank">http://lists.live555.com/mailman/listinfo/live-devel</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:live-devel-request@lists.live555.com" target="_blank">live-devel-request@lists.live555.com</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:live-devel-owner@lists.live555.com" target="_blank">live-devel-owner@lists.live555.com</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of live-devel digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. local rtsp client playback control only (Gerald Hansink)<br>
2. Re: local rtsp client playback control only (Ross Finlayson)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 15 Jun 2020 13:53:54 +0200<br>
From: Gerald Hansink <<a href="mailto:gerald.hansink@ieee.org" target="_blank">gerald.hansink@ieee.org</a>><br>
To: <a href="mailto:live-devel@us.live555.com" target="_blank">live-devel@us.live555.com</a><br>
Subject: [Live-devel] local rtsp client playback control only<br>
Message-ID:<br>
<CANfiUfdue7k9Rk=<a href="mailto:np16xV8ZWzvNMqBpuXDO7zeuPUjaWBBe2WA@mail.gmail.com" target="_blank">np16xV8ZWzvNMqBpuXDO7zeuPUjaWBBe2WA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
hi ross,<br>
<br>
for the use case where client is only used as "playback controller" without<br>
consuming video and the rtsp server acts as a "local video player".<br>
do you think this can be "easily" supported by implementing own "video<br>
sink" / "media session"?<br>
<br>
thanks,<br>
gerald<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.live555.com/pipermail/live-devel/attachments/20200615/2d5c2ecf/attachment-0001.htm" rel="noreferrer" target="_blank">http://lists.live555.com/pipermail/live-devel/attachments/20200615/2d5c2ecf/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 16 Jun 2020 03:59:38 +1200<br>
From: Ross Finlayson <<a href="mailto:finlayson@live555.com" target="_blank">finlayson@live555.com</a>><br>
To: LIVE555 Streaming Media - development & use<br>
<<a href="mailto:live-devel@us.live555.com" target="_blank">live-devel@us.live555.com</a>><br>
Subject: Re: [Live-devel] local rtsp client playback control only<br>
Message-ID: <<a href="mailto:187BB12D-F1DA-40D3-9548-FD0499614A44@live555.com" target="_blank">187BB12D-F1DA-40D3-9548-FD0499614A44@live555.com</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
<br>
<br>
> On Jun 15, 2020, at 11:53 PM, Gerald Hansink <<a href="mailto:gerald.hansink@ieee.org" target="_blank">gerald.hansink@ieee.org</a>> wrote:<br>
> <br>
> hi ross,<br>
> <br>
> for the use case where client is only used as "playback controller" without consuming video and the rtsp server acts as a "local video player".<br>
<br>
I?m not sure what you mean by 'rtsp server acts as a "local video player??. The RTSP server is the thing that responds to RTSP commands. It is usually the thing that transmits outgoing RTP (i.e., media) packets. In contrast, a ?video player? is the thing that renders/displays incoming media packets.<br>
<br>
However, the first part of your statement makes sense. It is possible for the RTSP client to just send RTSP commands (to the RTSP server), without actually receiving incoming RTP (i.e., media) packets from the server. (In this case, a separate process - running on the same computer - would usually receive the incoming RTP packets.)<br>
<br>
To do this, your client would need to specify which UDP port number (on the same computer) would be used to receive the incoming RTP packets. (I?m assuming a unicast stream here; for a multicast stream, it?s usually the server that chooses the port number (and destination IP multicast address).) To do this, look at how our ?openRTSP? application implements the<br>
-r (?don?t receive?)<br>
and<br>
-p <startingPortNumber><br>
options; see<br>
<a href="http://live555.com/openRTSP/#no-receive" rel="noreferrer" target="_blank">http://live555.com/openRTSP/#no-receive</a><br>
<br>
<br>
Ross Finlayson<br>
Live Networks, Inc.<br>
<a href="http://www.live555.com/" rel="noreferrer" target="_blank">http://www.live555.com/</a><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
live-devel mailing list<br>
<a href="mailto:live-devel@lists.live555.com" target="_blank">live-devel@lists.live555.com</a><br>
<a href="http://lists.live555.com/mailman/listinfo/live-devel" rel="noreferrer" target="_blank">http://lists.live555.com/mailman/listinfo/live-devel</a><br>
<br>
<br>
------------------------------<br>
<br>
End of live-devel Digest, Vol 199, Issue 3<br>
******************************************<br>
</blockquote></div></div>