[ogg-dev] How Ogg mappings translate into the codecs parameter in Ogg media types
silviapfeiffer1 at gmail.com
Thu Jun 5 21:08:12 PDT 2008
I am trying to set up the codecs table in the wiki and we have played
a bit with Dirac to find out what existing tools write into the
The Schroedinger implementation by Fluendo uses (or used to use)
"KW-DIRAC" as the identifier in the Ogg header.
"BBCD" is the identifier of each of the Dirac data packages.
More recently, I read that the Dirac Sequence header will be used as
the Ogg BOS packet directly.
I'm not sure this is the best solution and I'm not sure this is a
final decision either.
I believe it has to be sorted out properly and would suggest that
until such time we take the Dirac "codecs" specification out of this
On Sat, May 31, 2008 at 2:20 AM, Ivo Emanuel Gonçalves
<justivo at gmail.com> wrote:
> I received the following comment regarding the table:
>> The table contains a mix of octal and hexadecimal 'escape sequences'
>> for non-printable / non-ASCII octets.
>> I strongly suggest to only use a single kind of numerical escapes.
> Is this feasible or even desired, or should we leave things as they are?
> For reference, this is how the table looks right now:
> Codec Identifier | Codecs Parameter
> char: 'BBCD\0' | dirac
> char: '\177FLAC' | flac
> char: '\x80theora' | theora
> char: '\x01vorbis' | vorbis
> char: 'Speex ' | speex
> char: 'OggMIDI\0' | midi
> char: 'CMML\0\0\0\0' | cmml
> char: '\211PNG\r\n\032\n' | png
> char: '\212MNG\r\n\032\n' | mng
> char: '\213JNG\r\n\032\n' | jng
> char: 'CELT ' | celt
> char: 'PCM ' | pcm
> char: '\x80kate\0\0\0\0' | kate
> char: 'YUV4MPEG2' | yuv4mpeg
> (Don't expect it to look pretty without a monospaced font)
> ogg-dev mailing list
> ogg-dev at xiph.org
More information about the ogg-dev