Jump to: navigation, search


2,000 bytes added, 20:50, 13 November 2008
updated ident header
| Version major | Version minor | 8-11
| Field offset Offset to message header fields | 8-11 | Num headers | Granuleshift +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Reserved Number of header packets |1216-1519
| Granulerate numerator | 16-19
| | 32-35
| Granuleshift | Padding / future use |12-15
| Text type code | 36-39
Version major & minor are fields that are used by the text codec to define the version of its mapping.
* Field Offsetto message header fields:A 4 Byte unsigned integer that contains the number of Bytes used in this packet before the message header fields. * Number of header packets:Offset A 4 Byte unsigned integer that contains the number of header packets of that particular logical bitstream consisting of the bos page and the secondary header pages. * Granulerate numerator & denominatorTwo 8 Bytes signed integer each. They represent the temporal resolution of the logical bitstream in Hz given as a rational number in the same way as the basetime attribute above. * GranuleshiftA 1 Byte unsigned integer describing whether to partition the granule_position into two for that logical bitstream, and how many of the lower bits to use for the partitioning. The upper bits signify a time-continuous granule position for an independently decodeable and presentable data granule. The lower bits are generally used to specify the relative offset of dependent packets, such as predicted frames of a video. Hence these can be addressed, though not decoded without tracing back to the last fully decodeable data granule.This is the case with Ogg Theora; the general procedure is given in section 3.2. * Padding/future useThe 3 Bytes padding data that may be used for future requirements and are mandated to message zero in this revision. * Message header fieldsThe number of header fields, following the generic Internet Message Format defined in RFC 2822 [Headers]. Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive. The field value MAY be preceded by any amount of LWS, though a single SP is preferred. Header fieldscan be extended over multiple lines by preceding each extra line with at least one SP or HT.
=== The format of the Skeleton Fisbone ===

Navigation menu