High Efficiency Image File Format: Difference between revisions

Revision as of 15:40, 26 November 2015

Revision as of 15:45, 26 November 2015

Line 35:

* Image sequences are stored as ''tracks''. An image sequence track can be indicated to be displayed either as a timed sequence or in a non-timed manner, such as a gallery or album of images. When there is coding dependency between images, an image sequence track is used instead of image items.

* A file may contain both image items and image sequence tracks along with other media. For example, it is possible to create a HEIF file, which includes image items or image sequence tracks conforming to HEIF, and audio and/or timed text tracks conforming to any derivative format of the ISOBMFF

Keeping the above-mentioned design principles in mind, HEIF files can store the following types of data<ref name=":2">{{Cite web|url = http://phenix.int-evry.fr/jct/doc_end_user/current_document.php?id=10265|title = Overview of the High Efficiency Image File Format|date = |accessdate = |website = |publisher = JCT-VC document JCTVC-V0072, Oct. 2015|last = M. M. Hannuksela, E. B. Aksu, V. K. Malamal Vadakital, J. Lainema|first = }}</ref>:

* '''Image Items:''' storage of individual images, image properties and thumbnail(s).

* '''Image Derivations:''' derived images are generated during run-time based on descriptions such as rotation, grid and overlay. These images depend on other images stored in the HEIF file. The storage overhead of derived images is small.

Line 44:

== Comparison ==

Below table shows a comparison of different image formats<ref name=":2" />:

{|

|+'''Comparison of the features of some image file formats'''