Talk:Video coding format

Examples

I think there could be better examples of codecs and container formats:

The article currently mentions x264 as an example of a video codec. x264 is only an encoder, so it is at least questionable whether it can be called a codec ("coder/decoder"—yes, Wikipedia allows calling a decoder or encoder a codec with its "and/or" definition in video codec, but not all definitions elsewhere are so liberal, and even Wikipedia says "encoding and decoding" e.g. in Comparison of video codecs). So in order to differentiate between encoders, decoders and encoders/decoders (codecs), I would suggest changing the example to a codec library that can encode and decode. For example, libtheora (the Theora encoding/decoding library, but perhaps too obscure to be a good example), libvpx (the VP8 codec library by Google), Xvid (a popular, very well known example), or the DivX Codec (problematic as an example, because first, "DivX" is just a common brand name for the whole DivX product line, so it should be a specific product name, not "DivX", but there were several products over the years like the DivX Pro Codec etc., and second, because DivX supports both MPEG-4 Part 2 and 10, which would make the DivX example needlessly complicated).
WebM was used as an example of a container format. First, WebM is a full file type (file format) which sets an audio, video and a container format as parts of its specification. The container format used in a WebM file is Matroska. So I think WebM is higher-level than a container format (a container format, namely Matroska, is its subset). I changed the wording to "file format", but then, it makes the example pointless and confusing. So I would suggest changing the example to a real (pure) container format like Matroska, AVI, ASF, MP4 or Ogg.—J. M. (talk) 00:02, 15 October 2011 (UTC)[reply]
- Good points. I changed the x264 to Xvid. I have also rewritten the second part. Thanks for the very helpful suggestions :). Thue | talk 13:22, 15 October 2011 (UTC)[reply]

Please call it algorithm but not format

See algorithm. Format is rather a file format or a special container format. Why do we need this article and Video codec? User:ScotXW^t@lk 20:59, 27 June 2014 (UTC)[reply]

Because a video codec, as the article explains, is a piece of software or hardware, an implementation. Typically a software library. While video compression format refers to the specification. Two completely different things. The difference between a specification and an implementation is one of the most crucial things to understand in the world of digital technology. And "Video compression format" is perfectly fine. It is actually the bitstream format, the way the produced video bitstream must be formed to meet the specification. You could rename it to "video compression standard", as that's the way it is called in specifications such as H.264, but then you could argue what the word "standard" really means and which specification is "standardized" etc. "Algorithm" is not a good way to call it. Acutally, the implementations—codecs—use algorithms to encode and decode the video. But they are free to use any algorithm they choose to achieve the result. This is especially true with encoders. There are many different encoders made by different people that use the same format. They all use different algorithms and therefore achieve very different results (different picture quality for the same bitrate). The only requirement is that they produce streams in the specified video compression format. Because, again, specification (standard, format description) is not the implementation (codec, a piece of software or hardware that follows the specification), even though, admittedly, many people confuse these two things.—J. M. (talk) 00:58, 28 June 2014 (UTC)[reply]

I called the article "Video compression format" instead of "Video compression standard" when I created it because all the Wikipedia pages for individual specifications called it "Video compression format". I wrote this article to further my own understanding (I was confused about codec vs format, because everybody were using them interchangably, wrongly), so there were absolutely no expert judgement behind the choice of "format" over "standard". While I have the impression that you (J. M.) is a bit more knowledgeable, so feel free to overrule me. Thue (talk) 11:03, 28 June 2014 (UTC)[reply]

Using "format" is more correct than "standard" in this context, because some formats are not standardized. In this context, a "standard" ordinarily refers to a technical standard approved by a standards organization. Sometimes the word "standard" is used more loosely, to refer to a de facto standard, but some formats are not de facto standards either. A de facto standard, per the article on that topic, should be something "that has achieved a dominant position by public acceptance or market forces", although that term is also sometimes used more loosely (esp. by promoters – e.g., to convey a false impression of broad acceptance and approval). Some formats aren't even documented, much less standardized. —Mulligatawny (talk) 21:23, 28 June 2014 (UTC)[reply]

I added a section on why a video compression format is not an algorithm. Thue (talk) 12:47, 28 June 2014 (UTC)[reply]

Well, then please call is "Video compression algorithm". Format is simply wrong. I am aware of the difference between a spec and its implementation. User:ScotXW^t@lk 16:18, 28 June 2014 (UTC)[reply]

Read what I and J. M. wrote again. We are both specifically saying a video compression format is NOT a Video compression algorithm. Format is simply right. Thue (talk) 18:39, 28 June 2014 (UTC)[reply]

There is a difference between being a "format" and being a "file format" or a "container format". A format is not necessarily a file format. See, for example, the article Digital container format versus Content format. A "file format" or "container format" is something that may contain other formats within it. It generally defines a "wrapper" for containing different types of data that are each in their own particular formats (e.g., a file may contain an audio format, a video format, a format for subtitles, synchronization information, menu overlay and control data, etc. – sometimes with multiple A/V tracks, each in their own identified format, sometimes with multiple audio tracks or multiple subtitle tracks for the same video track, etc.). I agree that "format" is the correct term to use here. It is certainly incorrect to use "algorithm", since different algorithms can use the same data format. That is especially true for encoders (e.g., since different encoders use different search and decision-making algorithms), but it is also true for decoders as well (e.g., since different decoders use different algorithms for optimization of processing speed, memory usage, degree of parallel-processing, etc.). —Mulligatawny (talk) 21:23, 28 June 2014 (UTC)[reply]

Rename to "Video format"?

I want to rename the article to "Video format", because it is not all video formats which use compression (Uncompressed video). Limiting this article to only formats using compression seems inelegant.

There does not seem to be a standardized term for the concept, like "Video compression format" was just a description and not standardized, so no reason I can see for not renaming.

Any objections? Thue (talk) 16:55, 30 June 2014 (UTC)[reply]

How about "video coding format"? Coding does not necessarily imply compression. I think "video format" might sound like a file/container format. (Also, I wonder whether it's really necessary to consider uncompressed video to be within the scope of this article.) —Mulligatawny (talk) 19:14, 30 June 2014 (UTC)[reply]