Talk:Container format

message: 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.
Well, I'm not sure what you're really asking here.  Given that container formats often allow multiple streams, you could have 3 audio streams in one container file, each in a different language and each potentially could be encoded with a different encoder - not that any sane person would do that.  But I believe this would not be a technical problem.
As far as "other than audio and video" besides subtitles, I can't think of another stream type, but if you have a relevant encoder and decoder, why not?
InsertNameHere (talk) 23:01, 10 February 2020 (UTC)
thread_title: AV only?

message: 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)
thread_title:  Poor grammar? 

message: The article should address why container formats are used instead of the "raw" content.
94.220.249.144 (talk) 06:03, 27 February 2010 (UTC)
thread_title:  Why container? 

message: 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)
thread_title:  How so TIFF trashes Exif? 

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, 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.
At least something that tries to explain it. It's obvious to me even though I did not write it.  —Preceding unsigned comment added by 84.61.36.161 (talk) 20:04, 21 March 2011 (UTC)
thread_title:  Clarify Container vs content 

message: Would it be appropriate to include a reference to the Core_Audio_Format?
dpbaril 13:51, 17 April 2012 (UTC)
thread_title:  Include Reference to CAF format? 

message: In addition to the other problems with this article as of today, the lead links to the article on metafile.  Unhelpfully, there's essentially no substance there, and it's surprising that it exists.  They should be merged.  (I just don't want to do it myself.) -- C. A. Russell (talk) 15:20, 18 June 2020 (UTC)
replies: text: Klbrain (talk) 15:53, 30 June 2021 (UTC)
thread_title:  Merge with metafile