- From: Davy Van Deursen <davy.vandeursen@ugent.be>
- Date: Thu, 05 Jan 2012 13:29:11 +0100
- To: Raphaël Troncy <raphael.troncy@eurecom.fr>
- CC: Media Fragment <public-media-fragment@w3.org>
On 4/01/2012 12:15, Raphaël Troncy wrote: > Dear all, > > For the record, the minutes of today's phone telecon is at > http://www.w3.org/2012/01/04-mediafrag-minutes.html (and in text format > below). [[SNIP]] > Raphael: Should we clarify what are the setup data we send? > ... see message from Pierre Yves, > [16]http://lists.w3.org/Archives/Public/public-media-fragment/2011De > c/0023.html > ... so in the recipes, by "codec setup data", do we meant codecs > setup data _and_ the time/space index tables (e.g. > stts/ctts/stsc/stsz/stco/stss atoms, in ISO 14496-10)? > > [16] > http://lists.w3.org/Archives/Public/public-media-fragment/2011Dec/0023.html > > Erik: I can ask Davy for clarifications in his implementations As Pierre-Yves correctly indicates in the mail mentioned above, the term 'codec setup data' is not well defined in our spec I think. In particular, 'codec setup data' from a media fragments point of view consists of - setup data for the decoder (such as resolution, quantification parameter, ...); - timing information (i.e., when to display a certain frame); - track information (i.e., which tracks are present and how does the raw samples relate to these tracks). Note that this is independent of the MP4 container format (e.g., a WebM file also contains these three kinds of information). Should we find another term or should we just clarify this in the text (e.g., by means of a definition for 'codec setup data')? Best regards, Davy -- Davy Van Deursen Ghent University - IBBT Department of Electronics and Information Systems - Multimedia Lab URL: http://multimedialab.elis.ugent.be/dvdeurse
Received on Thursday, 5 January 2012 12:29:37 UTC