- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Wed, 30 Jun 2010 19:53:59 +1000
- To: Raphaël Troncy <raphael.troncy@eurecom.fr>
- Cc: Jack Jansen <Jack.Jansen@cwi.nl>, Davy Van Deursen <davy.vandeursen@ugent.be>, public-media-fragment@w3.org
2010/6/30 Raphaël Troncy <raphael.troncy@eurecom.fr>: > Hi all, > >> I agree with all of your examples (thanks!), except one: >> >>> Re (1): In RTSP, temporal fragment URIs are provided through the >>> PLAY method: >>> >>> a url such as >>> >>> rtsp://example.com/media#t=10,20 >>> >>> will be executed as a series of the following methods (all >>> shortened for readability), data selection provided in the PLAY >>> method: >>> >>> * C->S: DESCRIBE rtsp://example.com/media * S->C: RTSP/1.0 200 OK >>> (with an SDP description, see wiki) * C->S: SETUP >>> rtsp://example.com/media/video * S->C: RTSP/1.0 200 OK * C->S: >>> SETUP rtsp://example.com/media/audio * S->C: RTSP/1.0 200 OK * >>> C->S: PLAY rtsp://example.com/media Range: npt=10-20 * S->C: >>> RTSP/1.0 200 OK Range: npt=9.5-20.1 >> >> >> Why do you use two SETUP commands for separate tracks here? Shouldn't >> you simply do a single "SETUP rtsp://example.com/media"? > > Good question! Silvia? See section "14.2 Streaming of a Container file" - the example also uses all tracks for setup and not the combined format, even though it is dealing with a container format. I just followed that example. I couldn't find out from the spec whether a single SETUP is actually possible (it seemed to me that not), but if it is, I'm more than happy to change that. Cheers, Silvia.
Received on Wednesday, 30 June 2010 09:54:51 UTC