Jump to content

Talk:Container format

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Sutekh.destroyer (talk | contribs) at 22:54, 12 December 2009 (→‎Poor grammar?: paragraph tags). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

WikiProject iconComputing Unassessed
WikiProject iconThis article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
???This article has not yet received a rating on Wikipedia's content assessment scale.
???This article has not yet received a rating on the project's importance scale.

AV only?

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.

Poor grammar?

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)[reply]

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.

Sutekh.destroyer (talk) 22:53, 12 December 2009 (UTC)[reply]