I agree. Is it both in the code and in the documentation? I shall look at the documentation over easter.<br>Cheers,<br>Silvia.<br><br><div class="gmail_quote">On Wed, Mar 12, 2008 at 1:51 PM, Ivo Emanuel Gonçalves <<a href="mailto:justivo@gmail.com">justivo@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I noticed this first in vorbis-tools and later in ffmpeg2theora. The<br>
Skeleton bitstream contains a header called Content-Type. It lists<br>
the media types of all the data in Ogg.<br>
<br>
In vorbis-tools and ffmpeg2theora the output is normally Vorbis and<br>
Theora. The Skeleton implementation there reports those media types<br>
as video/x-theora and audio/x-vorbis.<br>
<br>
I would like to suggest that it would be better to use video/theora<br>
and audio/vorbis as those media types are in the middle of being<br>
registered through their respective RTP RFCs.<br>
<br>
Why urge this change instead of waiting? Because of interoperability<br>
as the Skeleton parsers will be expecting one media type for each of<br>
those codecs and not two (the x- and non x- versions). It would be<br>
pretty bad if there were two kinds of Ogg+Skeleton files out there.<br>
It's already bad that there are those with and without Skeleton as it<br>
is.<br>
<br>
The less confusion the better for everyone and, considering the media<br>
types are used internally, no one's going to complain.<br>
<br>
-Ivo<br>
_______________________________________________<br>
ogg-dev mailing list<br>
<a href="mailto:ogg-dev@xiph.org">ogg-dev@xiph.org</a><br>
<a href="http://lists.xiph.org/mailman/listinfo/ogg-dev" target="_blank">http://lists.xiph.org/mailman/listinfo/ogg-dev</a><br>
</blockquote></div><br>