Talk:Digital container format
|WikiProject Computing / Software||(Rated Start-class, Low-importance)|
|WikiProject Guild of Copy Editors|
Aren't there possibilities other than audio and video? I would agree that the idea is usually used to distinguish between different compression formats (whether lossless or lossy) - as opposed to uncompressed data - you don't get a format that is designed to contain spreadsheets in e.g. either CSV or Excel format. But what about images? I'm thinking of TIFF in particular, which allows a number of different compressed image formats.
VBR Delivery as apposed to encoding
I believe that an item for varaible bit rate delivery should be added to the Issues section. For example, depending on the bandwidth connecting the viewer to the video stream, one could view the same video in a lower resulotion/frame rate/bitdepth/artifacts/etc by skipping chunks of the file.
- Nice idea, but the way you put that sounds like original research :-P.
This made me cringe and I was wondering if anyone else did the same when reading this:
"A container or wrapper format is a file format whose specifications regard only the way data are stored (but not coded) within the file, and how many metadata could or are effectively stored" I can have a go at cleaning it up myself, but was after someone elses opinion. Legios (talk) 05:04, 13 March 2009 (UTC)
A good chunk of the introduction to this article made me cringe, actually. There are way too many parentheses and comma, and at times it seems like there is a stretch for more wiki-links. I tried re-writing a sentence and I could barley understand what its purpose was. Below is a new version of the introduction that I think is more clear and still contains the relevant information for someone looking for more information. I'll wait for comments before putting it on the main page.
A container or wrapper format is a meta-file format whose specification describes how data and meta-data is stored (not coded). A program able to identify and open a container file might not be able to decode the contained data. This can be caused by the program lacks the required decoding algorithm or the meta-data does not provide enough information. By definition, a container format could wrap any kind of data. Though there are a few examples of such file formats (e.g. Microsoft Windows's DLL files), most container formats are specialized for the specific requirements of the data.
For example, a popular family of containers is found among multimedia file formats. Since audio and video streams can be coded and decoded with many different algorithms, a container format can be used to provide a single file to the user.
How so TIFF trashes Exif?
Removed the following:
- , which results in difficulties in properly preserving information – notably, Exif photo data is often discarded.
I did a lot of work with TIFF in the late 1980s and the only reason I can think of for Exif lossage is sloppy coding, or a developer cutting corners to create a false impression of speed. Explain it so a software developer with 30 years of experience can comprehend it, or leave it out. My experience with TIFF was that it was disk seek intensive and only performed well if the file was written in a sensible order to disk. We had tools in house to do this which tripled the speed of many operations in a TIFF-like data structure we used to store font data. — MaxEnt 18:46, 13 April 2010 (UTC)
Clarify Container vs content
"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, or the meta-data not providing enough information.[clarification needed]"
Could one please find nice words for: A program can read (open) the container, but is not able to handle the content.
Include Reference to CAF format?
Would it be appropriate to include a reference to the Core_Audio_Format?