dany/libwebp
1
0
Fork 0
mirror of https://github.com/webmproject/libwebp.git synced 2024-12-26 13:48:21 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Restore (most) emphasis; add emphasis to normative

Browse Source 
RFC 2119 terms (MUST, etc.)

Change-Id: Ia07a64dd4eadebfe9ba8a98a4eef613d1b5d614a
This commit is contained in:
Lou Quillio 2011-10-04 11:02:15 -07:00
parent 428674dad1
commit 2678d819a4
2 changed files with 111 additions and 104 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/README
View File

@ -1,5 +1,5 @@
Generate HTML Container Spec from Text Source
============================================= Generate HTML Container Spec Doc from Text Source
=================================================
$ kramdown doc/webp-container-spec.txt --template doc/template.html > doc/output/webp-container-spec.html $ kramdown doc/webp-container-spec.txt --template doc/template.html > doc/output/webp-container-spec.html

209
doc/webp-container-spec.txt
View File

@ -9,7 +9,9 @@ end of this file.
--> -->
# WebP Container Specification
WebP Container Specification
============================
_Working Draft, v0.1, 20110926_ _Working Draft, v0.1, 20110926_
@ -18,111 +20,111 @@ _Working Draft, v0.1, 20110926_
{:toc} {:toc}
## Introduction Introduction
------------
WebP is a still image format that uses the VP8 key frame encoding (and, possibly, other codecs in the future) to compress image data in a lossy way. The VP8 encoding should make it more efficient than currently used formats. It is optimized for fast image transfer over the network (e.g., for WWW sites). However, it also aims for feature parity (like Color profile, XMP Metadata, Animation etc) with other formats. This document describes the structure of such a file. WebP is a still image format that uses the VP8 key frame encoding (and, possibly, other codecs in the future) to compress image data in a lossy way. The VP8 encoding should make it more efficient than currently used formats. It is optimized for fast image transfer over the network (e.g., for WWW sites). However, it also aims for feature parity (like Color profile, XMP Metadata, Animation etc) with other formats. This document describes the structure of such a file.
The first version of WebP handled only the basic use-case - a file having a single image (being one VP8 key frame) with no metadata. However, the use of a RIFF container allowed to extend it. This document extends it by additionally introducing support for: The first version of WebP handled only the basic use-case -- a file having a single image (being one VP8 key frame) with no metadata. However, the use of a RIFF container allowed to extend it. This document extends it by additionally introducing support for:
* Metadata and color profiles. We specify chunks that can contain this information, like can * **Metadata and color profiles.** We specify chunks that can contain this information, like can
other popular formats. other popular formats.
* Tiling. A single VP8 frame has an inherent limitation for width or height of 2^14 pixels and * **Tiling.** A single VP8 frame has an inherent limitation for width or height of 2^14 pixels and a 512kB limit on the size of first compressed partition. To support larger images, we support images that are composed of multiple tiles, each encoded as a separate VP8 frame. All tiles form logically a single image -- they have common metadata, color profile etc. Tiling may also improve efficiency for larger images -- grass can be encoded differently than sky.
a 512kB limit on the size of first compressed partition. To support larger images, we support
images that are composed of multiple tiles, each encoded as a separate VP8 frame. All tiles
form logically a single image - they have common metadata, color profile etc. Tiling may also
improve efficiency for larger images - grass can be encoded differently than sky.
* Animation. An image may have pauses between frames, making it an animation. * **Animation.** An image may have pauses between frames, making it an animation. Files not using these new features are backward compatible with the original format. Using these features will produce files that are not compatible with older programs.
Files not using these new features are backward compatible with the original format. Using these
features will produce files that are not compatible with older programs.
## Terminology Terminology
-----------
A WebP file contains either a still image (i.e. an encoded matrix of pixels) or an animation (see below) with, possibly, a color profile, metadata etc. In case we need to refer only to the matrix of pixels, we will call is the canvas of the image. A WebP file contains either a still image (i.e. an encoded matrix of pixels) or an animation (see below) with, possibly, a color profile, metadata etc. In case we need to refer only to the matrix of pixels, we will call is the **_canvas_** of the image.
The canvas of an image is built from one or multiple tiles. Each tile is a separately encoded VP8 key frame (other codec are possible in the future). Building an image from several tiles allows to overcome the size limitations of a single VP8 frame. Tiling is supposed to be an internal detail of the file - they are not supposed to be exposed to the user. The canvas of an image is built from one or multiple tiles. Each tile is a separately encoded VP8 key frame (other codec are possible in the future). Building an image from several tiles allows to overcome the size limitations of a single VP8 frame. Tiling is supposed to be an internal detail of the file -- they are not supposed to be exposed to the user.
## Basics Basics
------
This section introduces basic terms used throughout the document. This section introduces basic terms used throughout the document.
Code reading WebP files will be referred to as readers, while code writing them will be referred as writers. Code reading WebP files will be referred to as **_readers_**, while code writing them will be referred as **_writers_**.
A 16-bit, little-endian, unsigned integer will be denoted as uint16. A 16-bit, little-endian, unsigned integer will be denoted as **_uint16_**.
A 32-bit, little-endian, unsigned integer will be denoted as uint32. A 32-bit, little-endian, unsigned integer will be denoted as **_uint32_**.
The basic element of a RIFF file is a chunk. It consist of: The basic element of a RIFF file is a **_chunk_**. It consists of:
* 4 ASCII characters that will be called the chunk tag. * 4 ASCII characters that will be called the **_chunk tag_**.
* uint32 with the size of the chunk content (that will be denoted as ckSize). * uint32 with the size of the chunk content (that will be denoted as **_ckSize_**).
* ckSize bytes of content. * _ckSize_ bytes of content.
* If ckSize is odd, a single padding byte that SHOULD be 0. * If _ckSize_ is odd, a single padding byte that **SHOULD** be 0.
A chunk with a tag "ABCD" will be also called a chunk of type "ABCD". Note that, in this specification, all chunk tag characters are in file order, not in byte order of an uint32 of any particular architecture. A chunk with a tag "ABCD" will be also called a **_chunk of type_** "ABCD". Note that, in this specification, all chunk tag characters are in file order, not in byte order of an uint32 of any particular architecture.
Note that the padding MUST be also added to the last chunk of the file. Note that the padding **MUST** be also added to the last chunk of the file.
A list of chunks is a concatenation of multiple chunks. We will call the first chunk as having position 0, the second as position 1 etc. By chunk with index 0 among "ABCD" we will mean the first chunk among the chunks of type "ABCD" in the list, the chunk with index 1 among "ABCD" is the second such chunk, etc. A **_list of chunks_** is a concatenation of multiple chunks. We will call the first chunk as having _position_ 0, the second as position 1 etc. By _chunk with index 0 among "ABCD"_ we mean the first chunk among the chunks of type "ABCD" in the list, the _chunk with index 1 among "ABCD"_ is the second such chunk, etc.
A WebP file MUST begin with a single chunk with a tag "RIFF". All other defined chunks are within this chunk. It SHOULD NOT contain anything after it. A WebP file **MUST** begin with a single chunk with a tag "RIFF". All other defined chunks are within this chunk. It **SHOULD NOT** contain anything after it.
The maximum size of RIFF's ckSize is 2^32 -- 10 bytes (i.e. the size of the whole file is at most 4GiB -- 2 bytes). The maximum size of RIFF's _ckSize_ is 2^32 -- 10 bytes (i.e. the size of the whole file is at most 4GiB -- 2 bytes).
Note: some RIFF libraries are said to have bugs when handling files larger than 1GiB or 2GiB. If you are using an existing library, check that it handles large files correctly. **Note:** some RIFF libraries are said to have bugs when handling files larger than 1GiB or 2GiB. If you are using an existing library, check that it handles large files correctly.
The first four bytes of the RIFF chunk contents (i.e. bytes 8-11 of the file) MUST be the ASCII string "WEBP". They are followed by a list of chunks. Note that as the size of any chunk is even, the size of the RIFF chunk is also even. The first four bytes of the RIFF chunk contents (i.e. bytes 8-11 of the file) **MUST** be the ASCII string "WEBP". They are followed by a list of chunks. Note that as the size of any chunk is even, the size of the RIFF chunk is also even.
The content of the chunks in that list will be described in the following sections. The content of the chunks in that list will be described in the following sections.
Note: RIFF has a convention that all-uppercase chunks are standard chunks that apply to any RIFF file format, while chunks specific for a file format are all-lowercase. WebP doesn't follow this convention. Note: RIFF has a convention that all-uppercase chunks are standard chunks that apply to any RIFF file format, while chunks specific for a file format are all-lowercase. WebP doesn't follow this convention.
## Single-image WebP Files Single-image WebP Files
-----------------------
First, we will describe a subset of WebP files -- files containing only one image (later, we will use it to define multi-image files - file having several different images). First, we will describe a subset of WebP files -- files containing only one image (later, we will use it to define multi-image files -- file having several different images).
### Chunks Layout ### Chunks Layout
This section describes what chunks and in what order may appear in a single-image WebP file. The content of these chunks will be described in subsequent sections. This section describes what chunks and in what order may appear in a single-image WebP file. The content of these chunks will be described in subsequent sections.
The first chunk inside the RIFF chunk MUST be with a tag of "VP8 " (note the space as the last character) or "VP8X". Other tags for the first chunk MAY be introduced by future specifications if we add new codecs. This tag of the first chunk determines which of the two possible layouts is used. The first chunk inside the RIFF chunk **MUST** be with a tag of "VP8 " (note the space as the last character) or "VP8X". Other tags for the first chunk **MAY** be introduced by future specifications if we add new codecs. This tag of the first chunk determines which of the two possible layouts is used.
Rationale: we fix the possible tags of the first chunk so that it is possible to introduce other codecs, to keep the "WEBP" signature at the beginning of RIFF chunk, while still being able to check the codec used by the image by inspecting the byte stream at a fixed position. **Rationale:** we fix the possible tags of the first chunk so that it is possible to introduce other codecs, to keep the "WEBP" signature at the beginning of RIFF chunk, while still being able to check the codec used by the image by inspecting the byte stream at a fixed position.
The two possible layouts will be called images without special layout and images with special layout. The two possible layouts will be called _images without special layout_ and _images with special layout_.
#### Images without special layout #### Images Without Special Layout
If the first subchunk of RIFF has the tag "VP8", the file contains an image without special layout. If the first subchunk of RIFF has the tag "VP8 ", the file contains an _image without special layout_.
This layout SHOULD be used if the image doesn't require advanced features: color profiles, XMP metadata, animation or tiling. Files with this layout are smaller and supported by older software. This layout **SHOULD** be used if the image doesn't require advanced features: color profiles, XMP metadata, animation or tiling. Files with this layout are smaller and supported by older software.
Such images consist of: Such images consist of:
* A "VP8 " chunk with the bitstream of the single tile. * A "VP8 " chunk with the bitstream of the single tile.
Example: An example layout of such a file looks as follows: **Example:** An example layout of such a file looks as follows:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
RIFF/WEBP RIFF/WEBP
+- VP8 (bitstream of the single tile of the image) +- VP8 (bitstream of the single tile of the image)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#### Images with special layout #### Images With Special Layout
If the first subchunk of RIFF has the tag "VP8X" (other tags may be introduced by future specifications, if new codecs are added), the file contains an image with special layout. If the first subchunk of RIFF has the tag "VP8X" (other tags may be introduced by future specifications, if new codecs are added), the file contains an _image with special layout_.
Note: older readers are not supporting images with special layout and will fail for images having them. **Note:** older readers are not supporting images with special layout and will fail for images having them.
Such an image consists: Such an image consists of:
* A "VP8X" chunk with information about features used in this file. * A "VP8X" chunk with information about features used in this file.
@ -138,21 +140,19 @@ Such an image consists:
As will be described in the "VP8X" chunk description, by checking a flag one can distinguish animated and non-animated images. A non-animated image has exactly one frame. An animated one may have multiple frames. Data for each frame consists of: As will be described in the "VP8X" chunk description, by checking a flag one can distinguish animated and non-animated images. A non-animated image has exactly one frame. An animated one may have multiple frames. Data for each frame consists of:
* An optional "FRM " (note the space as the last character) chunk with animation frame * An optional "FRM " (note the space as the last character) chunk with animation frame metadata. It **MUST** be present in animated images at the beginning of data for that frame. It **MUST NOT** be present in non-animated images.
metadata. It MUST be present in animated images at the beginning of data for that frame. It
MUST NOT be present in non-animated images.
* An optional "TILE" chunk with tile position metadata. It MUST be present at the beginning of * An optional "TILE" chunk with tile position metadata. It **MUST** be present at the beginning of data of image that's represented as multiple tile images.
data of image that's represented as multiple tile images.
* A "VP8 " chunk with the bitstream of the tile. * A "VP8 " chunk with the bitstream of the tile.
All chunks MUST be placed in the same order as listed above (except for unknown chunks, that MAY appear anywhere). If a chunk appears in a wrong place, the file is invalid, but readers MAY parse the file ignoring the chunks that come too late. All chunks **MUST** be placed in the same order as listed above (except for unknown chunks, that **MAY** appear anywhere). If a chunk appears in a wrong place, the file is invalid, but readers **MAY** parse the file ignoring the chunks that come too late.
Rationale: setting the order of chunks should allow to quickly stop the search for e.g., the ICCP if it is not present in the file. The rule of ignoring late chunks should make programs that needs to do a full search give the same results as the ones stopping early. **Rationale:** setting the order of chunks should allow to quickly stop the search for e.g., the ICCP if it is not present in the file. The rule of ignoring late chunks should make programs that needs to do a full search give the same results as the ones stopping early.
Example: An example layout of a non-animated, tiled image may look as follows: **Example:** An example layout of a non-animated, tiled image may look as follows:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
RIFF/WEBP RIFF/WEBP
+- VP8X (descriptions of features used) +- VP8X (descriptions of features used)
+- ICCP (color profile) +- ICCP (color profile)
@ -165,9 +165,11 @@ RIFF/WEBP
+- TILE (fourth tile parameters) +- TILE (fourth tile parameters)
+- VP8 (bitstream - fourth tile) +- VP8 (bitstream - fourth tile)
+- META (XMP metadata) +- META (XMP metadata)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Example: An example layout of an animated image may look as follows: **Example:** An example layout of an animated image may look as follows:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
RIFF/WEBP RIFF/WEBP
+- VP8X (descriptions of features used) +- VP8X (descriptions of features used)
+- LOOP (animation control parameters) +- LOOP (animation control parameters)
@ -176,12 +178,14 @@ RIFF/WEBP
+- FRM (second animation frame parameters) +- FRM (second animation frame parameters)
+- VP8 (bitstream - second image frame) +- VP8 (bitstream - second image frame)
+- META(XMP metadata) +- META(XMP metadata)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
### Assembling the canvas from tiles and animation
Contents of the chunks will be described in details in subsequent section. Here, we provide an overview how they are used to assemble the canvas. The notation VP8X.canvasWidth means the field in the "VP8X" described as canvasWidth. ### Assembling the Canvas from Tiles and Animation
Decoding a non-animated canvas MUST be equivalent to the following pseudo-code: Contents of the chunks will be described in details in subsequent section. Here, we provide an overview how they are used to assemble the canvas. The notation _VP8X.canvasWidth_ means the field in the "VP8X" described as _canvasWidth_.
Decoding a non-animated canvas **MUST** be equivalent to the following pseudocode:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
assert not VP8X.flags.haveAnimation assert not VP8X.flags.haveAnimation
@ -198,7 +202,7 @@ for chunk in data_for_all_frames:
canvas contains the decoded canvas. canvas contains the decoded canvas.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Decoding an animated canvas MUST be equivalent to the following pseudo-code: Decoding an animated canvas **MUST** be equivalent to the following pseudocode:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
assert VP8X.flags.haveAnimation assert VP8X.flags.haveAnimation
@ -224,122 +228,125 @@ for LOOP.loop = 0, ..., LOOP.loopCount-1
canvas contains the decoded canvas. canvas contains the decoded canvas.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
As described earlier, if an assert related to chunk ordering fails, the reader MAY ignore the badly-ordered chunks instead of failing to decode the file. As described earlier, if an assert related to chunk ordering fails, the reader **MAY** ignore the badly-ordered chunks instead of failing to decode the file.
### Bitstream chunk(s) (VP8) ### Bitstream Chunks (VP8)
These chunks contain compressed image data. Currently, the only allowed bitstream is VP8 and uses "VP8 " (note the space as the last character) as its tag. We will refer to all chunks with this tag as bitstream chunks. As described earlier, images without special layout have a single bitstream chunk as the first subchunk of RIFF, while images with special layout may contain several of them - one for each tile. These chunks contain compressed image data. Currently, the only allowed bitstream is VP8 and uses "VP8 " (note the space as the last character) as its tag. We will refer to all chunks with this tag as **_bitstream chunks_**. As described earlier, images without special layout have a single bitstream chunk as the first subchunk of RIFF, while images with special layout may contain several of them -- one for each tile.
The content of a "VP8 " chunk MUST be one VP8 key frame (with optional padding -- see below). The content of a "VP8 " chunk **MUST** be one VP8 key frame (with optional padding -- see below).
The current draft of a VP8 specification can be found at [IETF.org][vp8spec]. Note that the VP8 frame header contains the VP8 frame width and height. It is assumed to be the width and height of the tile. The current draft of a VP8 specification can be found at [IETF.org][vp8spec]. Note that the VP8 frame header contains the VP8 frame width and height. It is assumed to be the width and height of the tile.
The VP8 specification specifies how to decode the image into Y'CbCr format. To convert to RGB, Rec. 601 SHOULD be used. The VP8 specification specifies how to decode the image into Y'CbCr format. To convert to RGB, Rec. 601 **SHOULD** be used.
For compatibility with older readers, if the size of the frame is odd, writers SHOULD append a padding byte (preferably 0) inside the chunk contents, making the chunk's ckSize even. Newer readers MUST support odd-sized tile chunks. For compatibility with older readers, if the size of the frame is odd, writers **SHOULD** append a padding byte (preferably 0) inside the chunk contents, making the chunk's _ckSize_ even. Newer readers **MUST** support odd-sized tile chunks.
### VP8X chunk (special layout)
### VP8X Chunk (Special Layout)
As described earlier, a chunk with tag "VP8X", is the first chunk of images with special layout. It is used to enable advanced features of WebP. As described earlier, a chunk with tag "VP8X", is the first chunk of images with special layout. It is used to enable advanced features of WebP.
The content of the chunk is as follows: The content of the chunk is as follows:
* uint32 flags. The following bits are currently used (with 0 being the least significant bit): * **uint32** _flags_. The following bits are currently used (with 0 being the least significant bit):
* bit 0: haveTile: set if the image is represented by Tiles. * bit 0: _haveTile_: set if the image is represented by Tiles.
* bit 1: haveAnimation: set if the file is an animation. Data in "LOOP" and "FRM " * bit 1: _haveAnimation_: set if the file is an animation. Data in "LOOP" and "FRM "
chunks should be used to control the animation. chunks should be used to control the animation.
* bit 2: haveIccp: set if the file contains a "ICCP" chunk with a color profile. If a file * bit 2: _haveIccp_: set if the file contains a "ICCP" chunk with a color profile. If a file
contains an "ICCP" chunk but this bit is not set, the error is flagged while constructing contains an "ICCP" chunk but this bit is not set, the error is flagged while constructing
the Mux-Container. the Mux-Container.
* bit 3: haveMetadat: set if the file contains a "META" chunk with a XMP metadata. If a file contains an "META" chunk but this bit is not set, the error is flagged while constructing the Mux-Container. * bit 3: _haveMetadat_: set if the file contains a "META" chunk with a XMP metadata. If a file contains an "META" chunk but this bit is not set, the error is flagged while constructing the Mux-Container. FIXME
Future specification MAY define other bits in flags. Bits not defined by this specification Future specification **MAY** define other bits in flags. Bits not defined by this specification
MUST be preserved when modifying the file. **MUST** be preserved when modifying the file.
* uint32 canvasWidth: width of the canvas in pixels (after the optional rotation or symmetry - see below). * **uint32** _canvasWidth_: width of the canvas in pixels (after the optional rotation or symmetry -- see below).
* uint32 canvasHeight: height of the canvas in pixels (after the optional rotation or symmetry see below). * **uint32** _canvasHeight_: height of the canvas in pixels (after the optional rotation or symmetry see below).
Future specifications MAY add more fields. If a chunk of larger size is found, programs MUST ignore the extra bytes but MUST preserve them when modifying the file. Future specifications **MAY** add more fields. If a chunk of larger size is found, programs **MUST** ignore the extra bytes but **MUST** preserve them when modifying the file.
### LOOP chunk (global animation parameters)
### LOOP Chunk (Global Animation Parameters)
For images that are animations, this chunk contains the global parameters of the animation. For images that are animations, this chunk contains the global parameters of the animation.
This chunks MUST appear if the haveAnimation flag in chunk VP8X is set. If the haveAnimation flag is not set and this chunk is present, it MUST be ignored. This chunk **MUST** appear if the _haveAnimation_ flag in chunk VP8X is set. If the _haveAnimation_ flag is not set and this chunk is present, it **MUST** be ignored.
The content of the chunk is as follows: The content of the chunk is as follows:
* uint16 loopCount For animations, the number of times to loop this animation. 0 means infinite. * **uint16** _loopCount_: For animations, the number of times to loop this animation. `0` means infinite.
Future specifications MAY add more fields. If a chunk of larger size is found, programs MUST ignore the extra bytes but MUST preserve them when modifying the file. Future specifications **MAY** add more fields. If a chunk of larger size is found, programs **MUST** ignore the extra bytes but **MUST** preserve them when modifying the file.
### FRM chunk (per-frame animation parameters)
### FRM Chunk (Per-frame Animation Parameters)
For images that are animations, these chunks contain the per-frame parameters of the animation. For images that are animations, these chunks contain the per-frame parameters of the animation.
The content of the chunk is as follows: The content of the chunk is as follows:
* uint32 frameX: x coordinate of the upper left corner of the frame. For images using the VP8 codec, it MUST be divisible by 32. Other codecs MAY specify other constraints. Described in more details later. * **uint32** _frameX_: x coordinate of the upper left corner of the frame. For images using the VP8 codec, it **MUST** be divisible by 32. Other codecs **MAY** specify other constraints. Described in more details later.
* uint32 frameY: y coordinate of the upper left corner of the frame. For images using the VP8 codec, it MUST be divisible by 32. Other codecs MAY specify other constraints. Described in more details later. * **uint32** _frameY_: y coordinate of the upper left corner of the frame. For images using the VP8 codec, it **MUST** be divisible by 32. Other codecs **MAY** specify other constraints. Described in more details later.
* uint32 frameWidth: width of the frame. For images using the VP8 codec, it MUST be divisible by 16 or such that frameX+frameWidth==canvasWidth. Other codecs MAY specify other constraints. Desribed in more details later. * **uint32** _frameWidth_: width of the frame. For images using the VP8 codec, it **MUST** be divisible by 16 or such that _frameX+frameWidth==canvasWidth_. Other codecs **MAY** specify other constraints. Desribed in more details later.
* uint32 frameHeight: height. For images using the VP8 codec, it MUST be divisible by 16 or such that frameY+frameHeight==canvasHeight. Other codecs MAY specify other constraints. Desribed in more details later. * **uint32** _frameHeight_: height. For images using the VP8 codec, it **MUST** be divisible by 16 or such that frameY+frameHeight==canvasHeight. Other codecs **MAY** specify other constraints. Desribed in more details later.
* uint16 frameDuration Time to wait before displaying the next tile, in 1ms unit. * **uint16** _frameDuration_: Time to wait before displaying the next tile, in 1ms units.
Rationale: the requirement for corner coordinates to be divisible by 32 means that pixels on U and V planes are aligned to 16 byte boundary (even after a rotation), what may help with vector instructions on some architectures. Also, this makes the tiles also aligned to 16-pixel macroblock boundaries. **Rationale:** The requirement for corner coordinates to be divisible by 32 means that pixels on U and V planes are aligned to 16 byte boundary (even after a rotation), what may help with vector instructions on some architectures. Also, this makes the tiles also aligned to 16-pixel macroblock boundaries.
Rationale: the requirement for the width and height to be divisible by 16 or touching the edge of the canvas simplifies the handling of macroblocks that are on the edge of a tile - VP8 decoders can overwrite pixels outside the boundary in such a macroblock and this guarantees they won't overwrite any data. **Rationale:** The requirement for the width and height to be divisible by 16 or touching the edge of the canvas simplifies the handling of macroblocks that are on the edge of a tile -- VP8 decoders can overwrite pixels outside the boundary in such a macroblock and this guarantees they won't overwrite any data.
Future specifications MAY add more fields. If a chunk of larger size is found, programs MUST ignore the extra bytes but MUST preserve them when modifying the file. Future specifications **MAY** add more fields. If a chunk of larger size is found, programs **MUST** ignore the extra bytes but **MUST** preserve them when modifying the file.
### TILE chunks (tile parameters) ### TILE Chunks (Tile Parameters)
This chunk contains information about a single tile and describes the bitstream chunk that proceeds it. This chunk contains information about a single tile and describes the bitstream chunk that proceeds it.
The content of such a chunk is as follows: The content of such a chunk is as follows:
* uint32 tileCanvasX: x coordinate of the upper left corner of the tile. For VP8 tiles, it MUST be divisible by 32. Other codecs MAY specify other constraints. * **uint32** _tileCanvasX_: x coordinate of the upper left corner of the tile. For VP8 tiles, it **MUST** be divisible by 32. Other codecs **MAY** specify other constraints.
* uint32 tileCanvasY: y coordinate of the upper left corner of the tile. For VP8 tiles, it MUST be divisible by 32. Other codecs MAY specify other constraints. * **uint32** _tileCanvasY_: y coordinate of the upper left corner of the tile. For VP8 tiles, it **MUST** be divisible by 32. Other codecs **MAY** specify other constraints.
Future specifications MAY add more fields. If a chunk of larger size is found, programs MUST ignore the extra bytes but MUST preserve them when modifying the file. Future specifications **MAY** add more fields. If a chunk of larger size is found, programs **MUST** ignore the extra bytes but **MUST** preserve them when modifying the file.
As described earlier, the TILE chunk is followed by a VP8 data. From that chun, we can read the height and width of the tile, that we will denote by tileWidth and tileHeight. In the case of VP8, we have the following constraints: As described earlier, the TILE chunk is followed by a VP8 data. From that chun, we can read the height and width of the tile, that we will denote by _tileWidth_ and _tileHeight_. In the case of VP8, we have the following constraints:
* The width of a tile MUST be divisible by 16 or there MUST be tileCanvasX+tileWidth == canvasWidth. * The width of a tile **MUST** be divisible by 16 or there **MUST** be _tileCanvasX+tileWidth==canvasWidth_.
* The height of a tile MUST be divisible by 16 or there MUST be tileCanvasY+tileHeight == canvasHeight. * The height of a tile **MUST** be divisible by 16 or there **MUST** be _tileCanvasY+tileHeight==canvasHeight_.
### ICCP chunk (color profile) ### ICCP Chunk (Color Profile)
An optional "ICCP" chunk contains an ICC profile. There SHOULD be at most one such chunk. The first byte of the chunk is the compression type. Two values are currently defined: a value of 0 means no compression, while a value of 1 means deflate/inflate compression. It is followed by a compressed or non-compressed ICC profile - see www.color.org for specifications. An optional "ICCP" chunk contains an ICC profile. There **SHOULD** be at most one such chunk. The first byte of the chunk is the compression type. Two values are currently defined: a value of 0 means no compression, while a value of 1 means deflate/inflate compression. It is followed by a compressed or non-compressed ICC profile -- see <http://www.color.org> for specifications.
The color profile can be a v2 or v4 profile. If this chunk is missing, sRGB SHOULD be assumed. The color profile can be a v2 or v4 profile. If this chunk is missing, sRGB **SHOULD** be assumed.
### META chunk (compressed XMP metadata) ### META Chunk (Compressed XMP Metadata)
Such a chunk (if present) contains XMP metadata. There SHOULD be at most one such chunk. If there are more such chunks, readers SHOULD ignore all except the first one. The first byte specifies compression type. Two values are currently defined: a value of 0 means no compression, while a value of 1 means deflate/inflate compression. It is followed by a compressed or non-compressed XMP metadata packet. Such a chunk (if present) contains XMP metadata. There SHOULD be at most one such chunk. If there are more such chunks, readers **SHOULD** ignore all except the first one. The first byte specifies compression type. Two values are currently defined: a value of 0 means no compression, while a value of 1 means deflate/inflate compression. It is followed by a compressed or non-compressed XMP metadata packet.
XMP packets are XML text specified in the [XMP Specification Part 1][xmpspec]. The chunk tag is different from the one specified by Adobe for WAV and AVI (also RIFF formats) because we have the options of compression. XMP packets are XML text specified in the [XMP Specification Part 1][xmpspec]. The chunk tag is different from the one specified by Adobe for WAV and AVI (also RIFF formats) because we have the options of compression.
Additional guidance about handling metadata can be found in the Metadata Working Group's [Guidelines for Handling Metadata][metadata]. Note that the sections of the document about reconciliation of EXIF, XMP and IPTC-IIM don't apply to WebP, as WebP supports only XMP, thus no reconciliation is necessary. Additional guidance about handling metadata can be found in the Metadata Working Group's [Guidelines for Handling Metadata][metadata]. Note that the sections of the document about reconciliation of EXIF, XMP and IPTC-IIM don't apply to WebP, as WebP supports only XMP, thus no reconciliation is necessary.
### Other chunks ### Other Chunks
A file MAY contain other chunks, defined in some future specification. Such chunks MUST be ignored, but preserved. Writers SHOULD try to preserve them in the original order. A file **MAY** contain other chunks, defined in some future specification. Such chunks **MUST** be ignored, but preserved. Writers **SHOULD** try to preserve them in the original order.