|
== Encodings inside the container ==
<!--The Improve the below paragraph as it doesn't adhere to Wikipedia's standards. -->HEIF container specification describes various encodings that can be stored inside:
* JFIF (JPEG)
* HEVC
These leads to confusion, asAs users cannot easily tell what kindencoding ofand encoding hasparameters beenan used.image Simplywas sayingstored thatin, “HEIFthe isHEIF bettercontainer thanformat JPEG”can asbe promotionalconfusing materialand doesn'tmakes meancomparison anythingstatements tolike the“HEIF is better than JPEG” vague and userinaccurate.
Simply knowing a file is in the HEIF container does not reveal much information, as it could be:
Inside the HEIF container, JFIF (JPEG) can be stored. It can also contain AV1 encoding. The user would also need to know the encoding parameters in which the encoding happened (e.g., color quality "q", if delta in chroma planes were used, if some advanced tuning for ssim/psnr was used, or what quantization mode was applied).
If a user creates a ".HEIF" photo with their phone, the user or the receiver of the photo cannot determine which image format inside the file was used. It could be:
* a JFIF (JPEG);
* an HEVC with poor quality parameters; or
* an HEVC with high quality parameters.
Hence, simply stating in promotional materials that “HEIF is better” doesn't mean anything at all, as HEIF is just a container specification. What is contained inside the container must be described.
It's impossible to easily determine exactly what you receive in HEIF container. At best, users can use graphics magic to determine if it's impossible by visual inspection (gradients transitions are broken in 8-bit photos) to tell if the photo is 12-bit or 10-bit per channel, or 8-bit.
{{anchor|MIAF}}{{anchor|MPEG-A}}
| 