[Tremor] Lacing values not as per standard

[Jindal]

Thanks Mike. You are spot on.

Is there a way that we can decode the Vorbis only stream without information
about the packets size from OGG header ?
I am assuming that Vorbis stream is individually decodable *without any
information from OGG header*.
Please correct me if i am wrong.

thanks,
Pankaj





On Tue, Aug 10, 2010 at 10:55 AM, Michael Smith <msmith at xiph.org> wrote:

> On Tue, Aug 10, 2010 at 10:52 AM, Jindal <jindal25 at gmail.com> wrote:
> > Hi,
> >
> >  I am trying to take off the ogg header processing from the Vorbis
> decoder.
> >
> > During analysis of some streams i found that the lacing values are not
> > following as described in document OGG logical bitstream framing.
> > http://xiph.org/vorbis/doc/framing.html.
> > Now as the document says that lacing values are 255 and then followed by
> a
> > value < 255 which marks the end of packet in normal case.
> >
> > Now i have seen stream with header specifying lacing values less then
> > 255 before the packet ends.
>
> I suspect you're misinterpreting that - it's definitely not possible
> for any decoder to decode a vorbis stream where the packets are split
> like this.
>
> Perhaps you're confusing packets and pages? There are typically many
> packets in a single ogg page - each of them follows the rule you've
> quoted.
>
> Mike
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.xiph.org/pipermail/tremor/attachments/20100810/4655f919/attachment.htm