Lines Matching refs:granulepos

7 ogg and the granulepos
10 An ogg stream contains pages with a serial number and a granulepos.
11 The granulepos is a 64 bit signed integer.  It is a value that in some way
16 ogg has no notion of time: it only knows about bytes and granulepos values
22 While logically a granulepos value can be constructed for every ogg packet,
23 the page is marked with only one granulepos value: the granulepos of the
26 theora and the granulepos
29 The granulepos in theora is an encoding of the frame number of the last
31 ("p frame").  The granulepos is constructed as the sum of the first number,
33 granulepos = (pframe << granuleshift) + iframe
36  the one and only granulepos for that page; several granulepos possibilities
39  However, given a granulepos, the theora codec can still map that to a
42  Note: currently theora stores the "presentation time" as the granulepos;
48 vorbis and granulepos
51 In Vorbis, the granulepos represents the number of samples that can be
55 - OFFSET is the time corresponding to the granulepos
57 - OFFSET_END is the granulepos of the produced vorbis buffer
68   - 3 header pages, with granulepos 0.
71   - granulepos is samplenumber of next page
77   - 3 header pages, with granulepos 0.
80   - granulepos is framenumber of last packet in page, where framenumber
192 An ogg demuxer can read pages and get the granulepos from them.
193 It can ask the decoder elements to convert a granulepos to time.
195 An ogg demuxer can also get the granulepos of the first and the last page of a
203 When asked to seek to a given granulepos, the ogg demuxer should always convert
206 granule pos or a granulepos with the same timestamp.
212 granulepos or a timestamp to the ogg demuxer.
214 In the case of a granulepos, the ogg demuxer will seek back to the beginning of
219 granulepos back to a timestamp. The ogg demuxer keeps on skipping pages until
223 granulepos into a timestamp or never seek on timestamp on the oggdemuxer.
226 granulepos of the packets, it is also the value of the OFFSET field in the
236 time represented by the valid (ie, not -1) granulepos values on those pages
241 granulepos represents for each ogg packet that it pushes to the ogg muxer.
242 This is ESSENTIAL: without this exact time representation of the granulepos,
257 with the timestamp that the granulepos in the header represents.
260 - ideally, every page queue has at least one page with a valid granulepos
273 The oggmuxer uses the offset fields to fill in the granulepos in the pages.
278 representation for each granulepos.  This needs to be provided by the encoder.
282    if the first audio sample has time 0.5, the granulepos in the vorbis encoder
286    granulepos cannot correctly represent this timestamp.
291 matching the granulepos, we need some way of communicating this time value
293 a granulepos and its time representation for each GstBuffer.
315   - abuse OFFSET to store the timestamp matching this granulepos
316   - abuse OFFSET_END to store the granulepos value
326     granulepos
327   - OFFSET_END is abused to be the granulepos of the encoded theora buffer
332   the granulepos of the encoded packet to take the delay into account as
335   than a frame period of the granulepos's time representation
337   the granulepos.  So in effect, the granulepos produced by the encoders