Re: Pages with granulepos = -1 while encoding..

On Thu, Feb 5, 2009 at 7:20 AM, Romain Beauxis <[email protected]> wrote:

> Following my recent issued with my encoder, I've narrowed the issue to the
> fact that, when encoding, for some returned pages, the granulepos returned by
> the libogg is -1.

Technically speaking, I think you can also use a greedy algorithm and
always write out granulepos=-1 pages as soon as you get them, since by
definition all you know is that they must come between two marked
pages from that same logical stream. The delay-until-the next
timestamp suggestion ogg.k made is more likely to be optimal in the
future though, if we ever block the packed+spanning packets case.

 -r