- From: Pierre-Yves Kerembellec <pierre-yves.kerembellec@dailymotion.com>
- Date: Thu, 15 Dec 2011 12:41:22 +0100
- To: Raphaël Troncy <raphael.troncy@eurecom.fr>
- Cc: Media Fragment <public-media-fragment@w3.org>
Le 15 déc. 2011 à 12:29, Raphaël Troncy a écrit : >> To be more specific, we synthetize an entire new document based on >> the requested time-range. We solely rely on the MP4 container (and >> AVC/AAC codecs) for Dailymotion (no support for OGG or Matroska >> containers), and the resulting document is a valid self-contained >> playable MP4 file. So this is not even what's described in section >> 2.2.2 "Server mapped byte ranges with corresponding binary data and >> codec setup data". > > I'm not sure I understand the differences between: > - your practice consisting in delivering a self-contained playable MP4 file ... > - ... and serving the codec setup data + the binary data corresponding to the time range requested ? > > If this is different, then perhaps we could add one more recipe on the document corresponding to your practice. For the ISO MP4 container (+ AVC/AAC codecs), serving the codecs setup data (AVC SPS/PPS and AAC setup) and the raw samples is not enough, since there is no DTS/PTS information in the raw samples area (samples are just ... well, raw data, sample after sample, audio and video samples interleaved in the file). You need to rebuild and provide some time/space index tables (namely stts/ctts/stsc/stsz/stco/stss atoms, see ISO 14496-10). So maybe you meant codecs setup data _and_ these index tables by "codec setup data". Otherwise these recipe won't work for ISO MP4. Cordialement, -- Pierre-Yves Kerembellec | Senior IT Expert Dailymotion | 49-51 rue Ganneron | 75018 Paris | France Tel : +33 1 77 35 11 09 | Mobile : +33 6 08 91 46 15
Received on Thursday, 15 December 2011 11:42:01 UTC