High Efficiency Image File Format: Difference between revisions

Content deleted Content added
Indicate that HEVC isn't a neutral choice
Tag: Reverted
 
(One intermediate revision by the same user not shown)
Line 20:
'''High Efficiency Image File Format''' ('''HEIF''') is a digital [[container format]] for storing individual [[digital image]]s and image sequences. The standard covers [[multimedia]] files that can also include other media streams, such as [[timed text]], audio and video.<ref name="JCTVC" />
 
HEIF can store images encoded with multiple coding formats, for example both [[Standard-dynamic-range video|SDR]] and [[High-dynamic-range video|HDR]] images. [[High Efficiency Video Coding|HEVC]] is a [non-free](https://en.wikipedia.org/wiki/Royalty-free)an image and video encoding format and the default image codec used with HEIF. HEIF files containing HEVC-encoded images are also known as '''HEIC''' files. Such files require less storage space than the equivalent quality [[JPEG]].<ref name="CNET" /><ref name="LesShu" />
 
HEIF files are a special case of the [[International Organization for Standardization|ISO]] Base Media File Format ([[ISO base media file format|ISOBMFF]], ISO/IEC 14496-12), first defined in 2001 as a shared part of [[MP4]] and [[JPEG 2000]]. Introduced in 2015, it was developed by the [[Moving Picture Experts Group]] (MPEG) and is defined as Part 12 within the [[MPEG-H]] media suite (ISO/IEC 23008-12).
Line 191:
{{Further|High Efficiency Video Coding#Patent holders}}
 
HEIF itself is a container that may not be subject to additional royalty fees for commercial ISOBMFF licensees. Note however that Nokia also grants its patents on a royalty-free basis for non-commercial purposes.<ref name="nokiaheiflicense">{{cite web |title=Nokia High-Efficiency Image File Format (HEIF) License |website=[[GitHub]] |url=https://github.com/nokiatech/heif/blob/master/LICENSE.TXT |access-date=2020-05-07 |archive-date=2020-11-12 |archive-url=https://web.archive.org/web/20201112020815/https://github.com/nokiatech/heif/blob/master/LICENSE.TXT |url-status=live }}</ref> When containing images and image sequences encoded in a particular format (e.g., HEVC or AVC) its use becomes subject to the licensing of patents on the coding format.<ref name="ars">{{cite web |title=macOS High Sierra tech preview: A quick look at the stuff you can't see |url=https://arstechnica.com/apple/2017/06/macos-high-sierra-tech-preview-a-quick-look-at-the-stuff-you-cant-see/ |access-date=2017-07-04 |date=2017-06-19 |quote=If there's one major downside to both HEVC and HEIF, it's that they're covered by patents that may need to be licensed for use in various apps and services. |archive-date=2017-06-20 |archive-url=https://web.archive.org/web/20170620001037/https://arstechnica.com/apple/2017/06/macos-high-sierra-tech-preview-a-quick-look-at-the-stuff-you-cant-see/ |url-status=live }}</ref><ref name="jpgtoheif">{{cite web |title=Converting a JPEG to the new HEIF format |url=http://jpgtoheif.com/ |access-date=2017-07-04 |quote=HEIF and HEVC are extensively covered by patents, which means there could be legal implications to implementing HEIF support, particularly in paid software or a hardware product. |archive-date=2017-07-07 |archive-url=https://web.archive.org/web/20170707214211/http://jpgtoheif.com/ |url-status=live }}</ref><ref name="beamr-on-licensing">{{cite web |title=Apple Endorses New Image Format, HEIF |url=https://www.linkedin.com/pulse/apple-endorses-new-image-format-heif-jan-ozer |access-date=2017-10-31 |date=2017-06-12 |first1=Jan |last1=Ozer |first2=Dror |last2=Gill |archive-date=2019-03-21 |archive-url=https://web.archive.org/web/20190321220755/https://www.linkedin.com/pulse/apple-endorses-new-image-format-heif-jan-ozer |url-status=live }}</ref>
 
== See also ==