W3C home > Mailing lists > Public > public-media-fragment@w3.org > November 2008

RE: Review of RTSP description

From: Davy Van Deursen <davy.vandeursen@ugent.be>
Date: Wed, 12 Nov 2008 17:34:36 +0100
To: "'Jack Jansen'" <Jack.Jansen@cwi.nl>
Cc: "'Media Fragment'" <public-media-fragment@w3.org>
Message-ID: <004601c944e4$8d0224d0$a7066e70$@vandeursen@ugent.be>

Hi Jack,

thanks for your comments! Some answers are provided inline.

>-----Original Message-----
>From: public-media-fragment-request@w3.org [mailto:public-media-
>fragment-request@w3.org] On Behalf Of Jack Jansen
>Sent: Wednesday, November 12, 2008 10:33 AM
>To: Media Fragment
>Subject: Review of RTSP description
>Pretty good description, but there's a few things I miss that may be
>relevant in our context:
>- How does rtsp seek work? That's relevant to our temporal fragmenting.
This is basically a combination of PAUSE and PLAY, where the PLAY method
contains the Range header pointing to the new temporal location. I have
added this explanation to the page.

>- Does rtsp have a way to say that streaming should stop at some
>point? Again relevant to temporal fragmenting.
Yes it has. The Range header can also be used with the PAUSE command (on
condition that a time point is given, instead of a time range). The
streaming server will stop sending the media content at this time point when
it receives such a PAUSE command. I have added an example to the wiki page.

>- Does rtsp have a way to do spatial croppping?
No, not to my knowledge. In the last section of the document
g_RTSP), a possible way to add such functionality to RTSP (i.e., by defining
a new RTSP header) is described.

Best regards,


Davy Van Deursen

Ghent University - IBBT
Department of Electronics and Information Systems Multimedia Lab
URL: http://multimedialab.elis.ugent.be
Received on Wednesday, 12 November 2008 16:35:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:52:41 UTC