High Efficiency Image File Format: Difference between revisions

Revision as of 11:01, 25 November 2015

Revision as of 14:14, 25 November 2015

Line 4:

== History ==

The requirements and main use cases of HEIF were defined in 2013 <ref name=":0">{{Cite web|title = Requirements for still image coding using HEVC {{!}} MPEG|url = http://mpeg.chiariglione.org/standards/mpeg-h/high-efficiency-video-coding/requirements-still-image-coding-using-hevc|website = mpeg.chiariglione.org|accessdate = 2015-11-25}}</ref><ref name=":1">{{Cite web|title = Requirements for HEVC image sequences {{!}} MPEG|url = http://mpeg.chiariglione.org/standards/mpeg-h/high-efficiency-video-coding/requirements-hevc-image-sequences|website = mpeg.chiariglione.org|accessdate = 2015-11-25}}</ref>.The technical development of the specification took about 1.5 years and was finalized in summer 2015<ref>{{Cite web|url = http://mpeg.chiariglione.org/sites/default/files/files/meetings/docs/w15328.docx|title = Evidence motivates MPEG to launch new standardization effort for HDR|date = |accessdate = |website = |publisher = |last = |first = }}</ref>.

== Use Cases ==

Some main use cases supported by HEIF are as follows<ref name=":0" /><ref name=":1" />:

* Storage of single or multiple images and their thumbnails,

* Storage of [[Burst mode (photography)|burst photos]],

* Support for simultaneous capture of video and still images, i.e. storing still images and timed image sequences into the same file,

* Efficient representation of animations and [[Cinemagraph|cinemagraphs]],

* Storage of [[Bracketing|focal and exposure stacks]] into the same container file, 

* Storage of images derived from other images of the file, either as derived images represented by [[Layers (digital image editing)|non-destructive image editing]] operations or as pre-computed derived images,

* Support for storing other media, such as audio and timed text, into the same container file with timed image sequences and synchronizing their playback. 

<references />__FORCETOC__