<br><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> More generally, I would like to suggest for audio/ogg with oga and<br>> video/ogg with ogv extensions that skeleton SHOULD be used for the
<br>> same simple reason of being able to identify the codecs inside.<br><br>This I'm not so sure. AFAIK, there's still no official or<br>non-official tools out there (except a few simple SVN projects) that<br>
deal with Skeleton. There's no Skeleton RFC either. We have to push<br>for both urgently.</blockquote><div><br>Hi,<br><br>Just so people are aware, liboggplay deals with skeleton tracks, and also forms a nice simple basis for implementing a (video/audio/whatever) player that can deal with pretty much any Ogg-compliant file that is thrown at it. There'll be a big
1.0 release of liboggplay in January - liboggplay is also in use within the already-released ogg/annodex plugin for firefox; and is being incorporated by Cris Double into some builds of firefox 3 for native ogg support purposes. So it's not true that there's nothing out there that deals with skeleton tracks.
<br><br>As for skeleton track creation, a three-line script on top of libannodex would do it, hogg does it, I can probably get it into oogg (ocaml ogg) pretty quickly, and at any rate, we're talking about a new conceptual file-type with a new extension - whether or not the tool support exists *right now* is less important than whether (a) the tool is easy to create and (b) the skeleton track makes sense in the context of audio/ogg and video/ogg files.
<br></div><br></div>Cheers,<br> -Shane<br>