- From: Henri Sivonen <hsivonen@iki.fi>
- Date: Fri, 8 Aug 2008 16:49:17 +0300
On Aug 8, 2008, at 13:42, Tim Starling wrote: > Jeremy Doig wrote: >> how would this work (say) for different avc profile levels and >> features (eg: PAFF support) ? The main problem with AVC levels is that J. Random Author has no idea what AVC level his/her tool emitted. > I don't think that's our problem. The details of determining a type > name > for a given file should be in another standard, it should not be in > HTML > 5. All HTML 5 has to do is delegate responsibility for type > assignment. HTML5 needs to delegate it to something that is implementable given the APIs QuickTime, GStreamer, DirectShow and Phonon provide. A standard doesn't help if it doesn't match the APIs. Does what HTML5 says now match the framework APIs? The MIME codecs parameter seems to confuse both WebKit and Minefield, for instance: http://hsivonen.iki.fi/test/moz/video-selection/source-mp4-ogg.html vs. http://hsivonen.iki.fi/test/moz/video-selection/source-mp4-ogg-params.html -- Henri Sivonen hsivonen at iki.fi http://hsivonen.iki.fi/
Received on Friday, 8 August 2008 06:49:17 UTC