Animowane grafiki PNG

UWAGA: Tłumaczenie tej strony nie zostało zakończone.
Może być ona niekompletna lub wymagać korekty.
Chcesz pomóc? | Dokończ tłumaczenie | Sprawdź ortografię | Więcej takich stron...

Ten artykuł obejmuje funkcje wprowadzone w Firefoksie 3

Autorzy

Orginał specyfikacji APNG autorstwa:

• Stuart Parmenter <pavlov@pavlov.net>
• Vladimir Vukicevic <vladimir@pobox.com>
• Andrew Smith <asmith15@littlesvr.ca>

Informacje wstępne

APNG jest rozwinięciem formatu Portable Network Graphics (PNG), z dodaną obsługą animowanych grafik. Został on stworzony z myślą o zastąpieniu prostych animowanych grafik które zwykle były tworzone przy użyciu formatu GIF, poprzez dodanie wsparcia dla 24-bitowych grafik i 8-bitowej przezroczystości. APNG jest prostszą alternatywą dla MNG, przy użyciu specyfikacji odpowiadającej dla większości zatosowań animowanych grafik w internecie

APNG jest wstecznie zgodny z PNG, każdy dekoder PNG powinien zignorować elementy zgodne ze specyfikacją APNG i wyświetlić nieruchomy obraz.

Struktura

An APNG stream is a normal PNG stream as defined in the PNG Specification, with three additional chunk types describing the animation and providing additional frame data.

To be recognized as an APNG, an 'acTL' chunk must appear in the stream before any 'IDAT' chunks. The 'acTL' structure is described below.

Conceptually, at the beginning of each play the output buffer must be completely initialized to a fully transparent black rectangle, with width and height dimensions from the 'IHDR' chunk.

The default image may be included as the first frame of the animation by the presence of a single 'fcTL' chunk before 'IDAT'. Otherwise, the default image is not part of the animation.

Subsequent frames are encoded in 'fdAT' chunks, which have the same structure as 'IDAT' chunks, except preceded by a sequence number. Information for each frame about placement and rendering is stored in 'fcTL' chunks. The full layout of 'fdAT' and 'fcTL' chunks is described below.

The boundaries of the entire animation are specified by the width and height parameters of the PNG 'IHDR' chunk, regardless of whether the default image is part of the animation. The default image should be appropriately padded with fully transparent pixels if extra space will be needed for later frames.

Each frame is identical for each play, therefore it is safe for applications to cache the frames.

Chunk sequence numbers

The 'fcTL' and 'fdAT' chunks have a 4 byte sequence number. Both chunk types share the sequence. The purpose of this number is to detect (and optionally correct) sequence errors in an Animated PNG, since the PNG specification does not impose ordering restrictions on ancillary chunks.

The first 'fcTL' chunk must contain sequence number 0, and the sequence numbers in the remaining 'fcTL' and 'fdAT' chunks must be in order, with no gaps or duplicates.

The tables below illustrates the use of sequence numbers for images with more than one frame and more than one 'fdAT' chunk.

If the default image is the first frame:

If the default image is not part of the animation:

Decoders must treat out-of-order APNG chunks as an error. APNG-aware PNG editors should restore them to correct order using the sequence numbers.

'acTL': The Animation Control Chunk

The 'acTL' chunk is an ancillary chunk as defined in the PNG Specification. It must appear before the first 'IDAT' chunk within a valid PNG stream.

The 'acTL' chunk contains:

num_frames indicates the total number of frames in the animation. This must equal the number of 'fcTL' chunks. 0 is not a valid value. 1 is a valid value for a single-frame APNG. If this value does not equal the actual number of frames it should be treated as an error.

num_plays indicates the number of times that this animation should play; if it is 0, the animation should play indefinitely. If nonzero, the animation should come to rest on the final frame at the end of the last play.

'fcTL': The Frame Control Chunk

The 'fcTL' chunk is an ancillary chunk as defined in the PNG Specification. It must appear before the 'IDAT' or 'fdAT' chunks of the frame to which it applies, specifically:

• For the default image, if a 'fcTL' chunk is present it must appear before the first 'IDAT' chunk. Position relative to the 'acTL' chunk is not specified.
• For the first frame excluding the default image (which may be either the first or second frame), the 'fcTL' chunk must appear after all 'IDAT' chunks and before the 'fdAT' chunks for the frame.
• For all subsequent frames, the 'fcTL' chunk for frame N must appear after the 'fdAT' chunks from frame N-1 and before the 'fdAT' chunks for frame N.
• Other ancillary chunks are allowed to appear among the APNG chunks, including between 'fdAT' chunks.

Exactly one 'fcTL' chunk is required for each frame.

The frame must be rendered within the region defined by x_offset, y_offset, width, and height. The offsets must be non-negative, the dimensions must be positive, and the region may not fall outside of the default image.

Constraints on frame regions:

• x_offset >= 0
• y_offset >= 0
• width > 0
• height > 0
• x_offset + width <= 'IHDR' width
• y_offset + height <= 'IHDR' height

The delay_num and delay_den parameters together specify a fraction indicating the time to display the current frame, in seconds. If the denominator is 0, it is to be treated as if it were 100 (that is, delay_num then specifies 1/100ths of a second). If the the value of the numerator is 0 the decoder should render the next frame as quickly as possible, though viewers may impose a reasonable lower bound.

Frame timings should be independent of the time required for decoding and display of each frame, so that animations will run at the same rate regardless of the performance of the decoder implementation.

dispose_op specifies how the output buffer should be changed at the end of the delay (before rendering the next frame).

Valid values for dispose_op are:

If the first 'fcTL' chunk uses a dispose_op of APNG_DISPOSE_OP_PREVIOUS it should be treated as APNG_DISPOSE_OP_BACKGROUND.

blend_op<code> specifies whether the frame is to be alpha blended into the current output buffer content, or whether it should completely replace its region in the output buffer.

Valid values for <code>blend_op are:

Note that for the first frame the two blend modes are functionally equivalent due to the clearing of the output buffer at the beginning of each play.

The 'fcTL' chunk corresponding to the default image, if it exists, has these restrictions:

• The x_offset and y_offset fields must be 0.
• The width and height fields must equal the corresponding fields from the 'IHDR' chunk.

As noted earlier, the output buffer must be completely initialized to fully transparent black at the beginning of each play. This is to ensure that each play of the animation will be identical. Decoders are free to avoid an explicit clear step as long as the result is guaranteed to be identical. For example, if the default image is included in the animation, and uses a blend_op of APNG_BLEND_OP_SOURCE, clearing is not necessary because the entire output buffer will be overwritten.

'fdAT': The Frame Data Chunk

The 'fdAT' chunk has the same purpose as an 'IDAT' chunk. It has the same structure as an 'IDAT' chunk, except preceded by a sequence number.

At least one 'fdAT' chunk is required for each frame. The compressed datastream is then the concatenation of the contents of the data fields of all the 'fdAT' chunks within a frame. When decompressed, the datastream is the complete pixel data of a PNG image, including the filter byte at the beginning of each scanline, similar to the uncompressed data of all the 'IDAT' chunks. It utilizes the same bit depth, color type, compression method, filter method, interlace method, and palette (if any) as the default image.

Each frame inherits every property specified by any critical or ancillary chunks before the first 'IDAT' in the file, except the width and height, which come from the 'fcTL' chunk.

If the PNG 'pHYs' chunk is present, the APNG images and their x_offset and y_offset values must be scaled in the same way as the main image. Conceptually, such scaling occurs while mapping the output buffer onto the canvas.

Revisions to this specification

Test Encoder and Sample Images

Sample images are available from the APNG implementation page at http://littlesvr.ca/apng/

An encoder (open source) is available in versions of the Gecko engine starting with version 1.9 alpha 4.

An application (open source) using the Mozilla encoder to assemble APNGs available here: http://littlesvr.ca/apng/apngedit.html

Zobacz także

• Portable Network Graphics (PNG) Specification (Second Edition)
• Extensions to the PNG Specification, Version 1.2.0
• Graphics Interchange Format 89a