search for: group__seek__semantics

Hi, I have a question about seeking. In fact, it's more or less a kind of rambling and thinking aloud, circling around a question. I've been wondering how to deal with seeking in a stream, and what to do when seeking in the middle of a set of active events (eg, when several bits of text are supposed to be shown, but you seek after the time when they are first shown, and before the time

...>time mapping for the logical bitstreams in the file. That's why all the timestamp-related info is crammed into granulepos rather than being placed in packet data, where it is no longer visible in the container.. Assumptions about seeking in Ogg: http://www.annodex.net/software/liboggz/html/group__seek__semantics.html which quotes from a mail from Monty in 2002 explaining the seek algorithm. Ralph's recent talk at LCA, "Seeking is hard: Ogg design internals": http://linux.conf.au/programme/friday Hope that clarifies things a little bit. The answer may simply be that what you want to do isn&...

...have anyway since Ogg had to seek to it beforehand. (*) or can it ? Is this the bit I'm missing ? I'm 99% sure it can't, but I'd be happy to be proved wrong as it would resolve the conendrum. > Assumptions about seeking in Ogg: > http://www.annodex.net/software/liboggz/html/group__seek__semantics.html > > which quotes from a mail from Monty in 2002 explaining the seek algorithm. Ah, quite interesting. That last solution Monty mentions would "fix" the double seek problems. > Ralph's recent talk at LCA, "Seeking is hard: Ogg design internals": > http://li...