Ogg embedding, problem with spec and/or bugs in speexenc
piman at sacredchao.net
Sat Jul 15 12:17:22 PDT 2006
(Sending again after subscribing, I guess the moderator is on vacation.)
I'm working on support for tagging Speex files for Mutagen and part
of the specification at  is confusing me. It says the first page
should have granulepos 0 and packetno 0. Does this really mean page
sequence number 0, since the Ogg format doesn't number packets?
If it doesn't mean page sequence number, what does it mean?
If it does really mean packet, does that mean there are no guarantees
about page/packet boundries? e.g. Vorbis guarantees the first page
contains only, and entirely, the first packet. speexenc breaks pages
after the info and comment packets, which again suggests "pages" rather
than "packets" is meant.
Later it says that the audio data starts at packetno 2. Does this really
mean page number 2? If so, does that mean the comment packet cannot span
multiple pages? I can force speexenc to write a multipage comment
packet, which would indicate either speexenc is wrong or the spec is
It says the comment packet should have granulepos 0. However, when I
force a multipage comment packet, all but the last page have granulepos
-1. Regardless of the above, I believe this is a speexenc bug. Either it
should mark all these pages 0, or only allow one page.
Joe Wreschnig <piman at sacredchao.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20060715/dc5414b9/attachment.pgp
More information about the Speex-dev