ogg dev - May 2008 - How Ogg mappings translate into the codecs parameter in Ogg media types

On 5/26/08, ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at googlemail.com>
wrote:
>>           char[8]: 'kate\0\0\0\0'    | kate
>
> This is incorrect, should be:
>
>             char[9]: '\x80kate\0\0\0\0'    | kate
The last one is how it's listed on ogginfo code, but the first one
(char[8]) is how it's described in the wiki page.  I thought the
latter would be more correct.  If not, you should revise the wiki
page.

Thanks for the help, everyone.  I'm committing changes based on this
thread to the draft.

-Ivo

I was just having a thought this morning: we should probably include
the version information into the codec identification bits. It will
make it easier to then re-use the table for mime-types for codecs as
we go and do RTP/RTSP specifications.

Cheers,
Silvia.

On Tue, May 27, 2008 at 2:11 AM, Ivo Emanuel Gon?alves
<justivo at gmail.com> wrote:
> On 5/26/08, ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at
googlemail.com> wrote:
>>>           char[8]: 'kate\0\0\0\0'    | kate
>>
>> This is incorrect, should be:
>>
>>             char[9]: '\x80kate\0\0\0\0'    | kate
>
> The last one is how it's listed on ogginfo code, but the first one
> (char[8]) is how it's described in the wiki page.  I thought the
> latter would be more correct.  If not, you should revise the wiki
> page.
>
> Thanks for the help, everyone.  I'm committing changes based on this
> thread to the draft.
>
> -Ivo
> _______________________________________________
> ogg-dev mailing list
> ogg-dev at xiph.org
> http://lists.xiph.org/mailman/listinfo/ogg-dev
>

Silvia,

I don't think I follow your line of thought.

On 5/27/08, Silvia Pfeiffer <silviapfeiffer1 at gmail.com>
wrote:
> I was just having a thought this morning: we should probably include
> the version information into the codec identification bits.
What version information?  Like libvorbis 1.2.1?  If so, I can't see
much of a point in that.
> It will make it easier to then re-use the table for mime-types for codecs
as
> we go and do RTP/RTSP specifications.
How?  RTP specifications are using their own media types, sometimes
coupled with "side-kick"  (e.g. audio/vorbis-config).  And what good
there would be in using a version information here?  All Vorbis
streams for instance are (hopefully) supposed to work in past and
future decoders.

-Ivo