- From: Thomas Steiner <tomac@google.com>
- Date: Thu, 24 Nov 2011 09:48:12 +0100
- To: Erik Mannens <erik.mannens@ugent.be>
- Cc: Yunjia Li <yl2@ecs.soton.ac.uk>, Media Fragment <public-media-fragment@w3.org>
Hi Erik, all, Please find my replies inline… > - TC0021-UA (SMPTE) 0%, as the parser has no information on the actual framerate. > - TC0025-UA (clock) 0%, as clock times are inapplicable to <video> / <audio> > - TC0026-UA (clock) 0%, as clock times are inapplicable to <video> / <audio> > - TC0056-UA (track) 0%, as track data are unavailable with <video> / <audio> > - TC0057-UA (track) 0%, as track data are unavailable with <video> / <audio> > - TC0060-UA (track) 0%, as track data are unavailable with <video> / <audio> > - TC0096-UA (track) 0%, as track data are unavailable with <video> / <audio> > - TC0023-UA (SMPTE) (if TC gets approved) 0%, as the parser has no information on the actual framerate. > - TC0099-UA (SMPTE) (if TC gets approved) 0%, as the parser has no information on the actual framerate. > - TC0100-UA (SMPTE) (if TC gets approved) 0%, as the parser has no information on the actual framerate. > - TC0101-UA (id) (if TC gets approved) 0%, as id data are unavailable with <video> / <audio> > - TC0102-UA (id) (if TC gets approved) 0%, as id data are unavailable with <video> / <audio> Sorry for the 0% replies :-( mediafragments.js is a high-level library that can correctly parse all media fragment URIs, however, in order to put some of them in practice, needed low-level access to the media resources, which, given the current state of <video> / <audio> is impossible. Best, Tom -- Thomas Steiner, Research Scientist, Google Inc. http://blog.tomayac.com, http://twitter.com/tomayac
Received on Thursday, 24 November 2011 08:49:09 UTC