Digital container format
|This article needs additional citations for verification. (June 2017) (Learn how and when to remove this template message)|
Since the container does not describe how data or metadata is encoded, a program able to identify and open a container file might not be able to decode the contained data. This may be caused by the program lacking the required decoding algorithm.
By definition, a container format could wrap any kind of data. Though there are some examples of such file formats (e.g. Microsoft Windows's DLL files), most container formats are specialized for specific data requirements. For example, a popular family of containers is found for use with multimedia file formats. Since audio and video streams can be coded and decoded with many different algorithms, a container format may be used to provide a single file format to the user.
Multimedia container formats
The container file is used to identify and interleave different data types. Simpler container formats can contain different types of audio formats, while more advanced container formats can support multiple audio and video streams, subtitles, chapter-information, and meta-data (tags) — along with the synchronization information needed to play back the various streams together. In most cases, the file header, most of the metadata and the synchro chunks are specified by the container format. For example, container formats exist for optimized, low-quality, internet video streaming which differs from high-quality Blu-ray streaming requirements.
Container format parts have various names: "chunks" as in RIFF and PNG, "atoms" in QuickTime/MP4, "packets" in MPEG-TS (from the communications term), and "segments" in JPEG. The main content of a chunk is called the "data" or "payload". Most container formats have chunks in sequence, each with a header, while TIFF instead stores offsets. Modular chunks make it easy to recover other chunks in case of file corruption or dropped frames or bit slip, while offsets result in framing errors in cases of bit slip.
Some containers are exclusive to audio:
- AIFF (IFF file format, widely used on Mac OS platform)
- WAV (RIFF file format, widely used on Windows platform)
- XMF (Extensible Music Format)
Other containers are exclusive to still images:
- FITS (Flexible Image Transport System) still images, raw data, and associated metadata.
- TIFF (Tagged Image File Format) still images and associated metadata.
Other flexible containers can hold many types of audio and video, as well as other media. The most popular multi-media containers are:
- 3GP (used by many mobile phones; based on the ISO base media file format)
- ASF (container for Microsoft WMA and WMV, which today usually do not use a container)
- AVI (the standard Microsoft Windows container, also based on RIFF)
- DVR-MS ("Microsoft Digital Video Recording", proprietary video container format developed by Microsoft based on ASF)
- Flash Video (FLV, F4V) (container for video and audio from Adobe Systems)
- IFF (first platform-independent container format)
- Matroska (MKV) (not limited to any coding format, as it can hold virtually anything; it is an open standard container format)
- MJ2 - Motion JPEG 2000 file format, based on the ISO base media file format which is defined in MPEG-4 Part 12 and JPEG 2000 Part 12
- QuickTime File Format (standard QuickTime video container from Apple Inc.)
- MPEG program stream (standard container for MPEG-1 and MPEG-2 elementary streams on reasonably reliable media such as disks; used also on DVD-Video discs)
- MPEG-2 transport stream (a.k.a. MPEG-TS) (standard container for digital broadcasting and for transportation over unreliable media; used also on Blu-ray Disc video; typically contains multiple video and audio streams, and an electronic program guide)
- MP4 (standard audio and video container for the MPEG-4 multimedia portfolio, based on the ISO base media file format defined in MPEG-4 Part 12 and JPEG 2000 Part 12) which in turn was based on the QuickTime file format.
- Ogg (standard container for Xiph.org audio formats Vorbis and Opus and video format Theora)
- RM (RealMedia; standard container for RealVideo and RealAudio)
Single coding formats
In addition to pure container formats, which specify only the wrapper but not the coding, a number of file formats specify both a storage layer and the coding, as part of modular design and forward compatibility.
In principle, coding can be changed while the storage layer is retained; for example, Multiple-image Network Graphics (MNG) uses the PNG container format but provides animation, while JPEG Network Graphics (JNG) puts JPEG encoded data in a PNG container; in both cases however, the different formats have different magic numbers – the format specifies the coding, though a MNG can contain both PNG-encoded images and JPEG-encoded images.
||This section possibly contains original research. (January 2011) (Learn how and when to remove this template message)|
The differences between various container formats arise from five main issues:
- Popularity; how widely supported a container is.
- Overhead. This is the difference in file-size between two files with the same content in a different container.
- Support for advanced codec functionality. Older formats such as AVI do not support new codec features like B-frames, VBR audio or VFR video natively. The format may be "hacked" to add support, but this creates compatibility problems.
- Support for advanced content, such as chapters, subtitles, meta-tags, user-data.
- Support of streaming media.
- Comparison of (audio/video) container formats
- Open source codecs and containers
- List of multimedia (audio/video) codecs
Similar packaging structures
- Ho, Anthony T. S.; Li, Shujun (20 May 2016). Handbook of Digital Forensics of Multimedia Data and Devices, Enhanced E-Book. John Wiley & Sons. pp. 146–(?). ISBN 9781118757079. OCLC 953319457.
- Online Video File Format Identification Tool - Designed primarily for CCTV video formats and codecs