Talk:List of codecs

DSD
I find it moderately disturbing that DSD/SACD are listed under "Pulse Density Modulation". This is incorrect, DSD is, was, and has always been an advanced form of Candy/Condon Sigma-Delta (or Delta-Sigma) if you choose, which means that it is a form of PCM with oversampling and noise shaping. There are many forms of PDM that do not have the characteristics of Sigma-Delta, and it seems misleading to call it PDM, when in fact is is a very well known use of a very early technique, namely Sigma-Delta, which is, at its core, nothing more than PCM with noise shaping. — Preceding unsigned comment added by Woodinville (talk • contribs) 01:39, 8 July 2014 (UTC)

AVS
Where does AVS go? —Preceding unsigned comment added by 129.215.101.110 (talk) 14:37, 20 June 2008 (UTC)

Forbidden Technologies codecs
I removed FORlive and FORtune from the list because this looked like a blatant product advertisement. This is not the first time the issue of Forbidden Technologies advertising on Wikipedia has come up. See Articles_for_deletion/FORscene.


 * Appearances are not all that they seem though. Forbidden's 1,000,000 hits per month on the FORlive demo page do not come from Wikipedia. The product Forbidden sells is now is almost exclusively FORscene, which now has its own editing codec (not discussed or even mentioned in the codec list). FORscene was my first article on joining WP ("Be bold", it says!). The nominiator has since said "I've just seen too many people trying to spam the place with advertising. Just after I submitted ForScene for AfD, I noticed that this was probably not the case here. I might not even have nominated it, had I known then what I know now." (see User_talk:Stephen_B_Streater). The notorious Rouge Admin User:JzG offererd to bring it to Deletion Review following discussions on Wikipedia_talk:Notability_%28software%29. Even the deleting admin offered to rewrite the article in a more WP friendly style, as the topic was notable (see User_talk:Stephen_B_Streater). So this deletion was more to do with my inexperience of WP procedures at the time than the significance of the FORscene product itself, which clearly meets both the current and proposed notability guidelines. Stephen B Streater 09:06, 22 May 2006 (UTC)

When I click on the FORlive link I see an ad for streaming video software that says nothing about codecs whatsoever. And when I click on the FORtune link I get a page that doesn't even mention FORtune at all. Thus this information is unverifiable, unrelated to the subject matter of the article, and a blatant product advertisement.


 * I have replaced the FORlive link with a more interesting one. During the day, this gives full frame rate video, with lower frame rate at night. I hope this will help you here.


 * It's just a product demo, it doesn't tell me anything informative. For example, when I click on Theora, I'd expect an article about the codec, not Fluendo's Java demo (although that is mentioned in the article). -- Mcoder 08:17, 1 June 2006 (UTC)
 * Well, it isn't an article, it's an example. If you would like to write an article, I can give you the relevant references to, for example, historical press releases and patents. Stephen B Streater 10:32, 1 June 2006 (UTC)

I looked for independant confirmation that these codecs exist and found none. Neither was listed at multimedia.cx, hydrogenaudio, or doom9. The only thing I found with a search engine were links to Forbidden Technologies press releases. See WP:Notability.


 * The FORlive codec was shipped with FORscene until January this year, and FORtune is the audio codec in FORscene. There are dozens of articles about FORscene. The latest customer for FORtune was the British Army, who bought it as part of our FORscene mobile offer. So by avoiding advertising FORscene, and listing the underlying technologies here as FORlive and FORtune, you are finding it hard to find press coverage. We could list them as FORscene version 1 video and FORscene audio, and then you would be able to choose from dozens of press articles.


 * Note that I haven't objected to FORscene being listed in List of video editing software. I think there's enough written about this for it to be notable.  But what exactly would an article on FORtune say?  "FORtune is an audio codec by Forbidden Technologies, which they don't even mention on their web site."  Not a real informative article. Compare that to articles like Windows Media Audio or Apple Lossless which actually tell me something.  Note that RealAudio, for example, isn't on this list, but the codecs (listed in the RealAudio article) are.  WMA is on the list because that refers to WMA standard codec; WMA lossless has a separate entry.  FLV isn't on the list, but H.263, VP6, etc are. (Those are the codecs flv actually uses.) -- Mcoder 08:17, 1 June 2006 (UTC)


 * You are right that FORtune almost nothing published about it, though it is mentioned on the Forbidden website. It has much less about it than FORscene (which includes FORtune). It's an example of a Java audio codec. The interesting thing about it is that it is written in Java and plays back on most platforms (eg Windows, Mac, Linux) without requiring installation, though it does require installation on mobile phones. So in this respect it is a different category to the other codecs listed. The list definition doesn't define interesting compression algorithms as the only criterion to determine qualification for entry - so I suppose my claim is that codecs can be notable because of their implementation. I wouldn't object strongly if you see the list as exclusively bitstream-related though, and wouldn't revert a considered removal edit. See below about FORscene if you are more concerned with published information. Stephen B Streater 10:55, 1 June 2006 (UTC)


 * I'm working on a prototype FORscene article here. I have started to include some information about the video and audio codecs used in FORscene. This could also mention the video codec used in FORlive, which is now deprecated in FORscene, and also FORtune. In fact, I'd welcome any constructive comments and edits prior to deletion review. I am keen to err on the side of too much information rather than too little, as it is easier for me to add content and find references and for other editors to trim it than vice versa. Stephen B Streater 10:55, 1 June 2006 (UTC)


 * That looks pretty good. You might want to trim the See Also list a bit, since things like Java and web application are already linked in the article text.  I was a little confused by the upload section, since you list 3 operating systems separately, and I was under the impression that this is done with java and a web browser and is basically the same on each platform.  Also the server section is confusing - do you sell servers or only usage of your servers? -- Mcoder 13:30, 1 June 2006 (UTC)


 * I've made some improvements. Thanks for your suggestions. Stephen B Streater 07:29, 2 June 2006 (UTC)


 * Copied to proposed article talk page. Stephen B Streater 17:50, 9 June 2006 (UTC)

Below is Stephen B Streater's description of FORlive and FORtune. I have to ask why this is here instead of on forbidden.co.uk? This could be the start of an article, but would need some independant sources (see WP:Cite, Verifiability, No original research) --Mcoder 00:29, 22 May 2006 (UTC)


 * The reason it is here is because you asked for some more information. As for the website, company websites do not generally explain how their codecs work - this information is in the patents. The website lists some features of the codecs here. Forbidden's main products are FORscene and Clesh, which have their own video codecs (not mentioned in the list). The codecs are packaged into other products, and the press in the industries Forbidden sells to are not that interested in the names of the codec technology used.


 * For me, and I suspect for many others reading this list, FORlive and FORtune are the only codecs listed which actually work on an out-of-the-box Mac, PC and Linux machine - truly cross platform codecs. I suspect that this is a major factor in the codecs being listed unchallenged up until now. It would be ironic if the only codecs which almost everyone can actually see in action were removed for some imagined commercial reason.


 * There's nothing wrong with it being commercial. There are articles on Windows Media Video, RealVideo, and many other commercial products.  It's certainly not necessary for the articles to explain in detail how the codecs work (although there may be references to technical documents which do).  Mostly people want to know things like what software is it compatible with, how does the quality and bitrate compare to other codecs, does it support CBR or VBR, and maybe a little bit of the history (eg is FORlive related to EIDOS ESCAPE/RPL?) FORtune is listed alongside codecs like MP3, Vorbis and AAC but I really have no idea if they're even comparable. -- Mcoder 08:17, 1 June 2006 (UTC)


 * This would all be good to put in an article. Perhaps the FORscene article (prototype here) will be the best place to add in this information. This link in this list could then go to the relevant section of the FORscene article. Does this sound like a sensible course of action? If so, I merely ask for patience as I am only just starting to ask for input on the new FORscene article, and still have some references to add. Stephen B Streater 11:01, 1 June 2006 (UTC)


 * Yes, I think the history part explains the Eidos connection pretty well. You've actually got quite a lot of references. -- Mcoder 13:30, 1 June 2006 (UTC)


 * If you would like to write a WP:NPOV article, FORscene or Clesh would be a good place to start. Articles on these subjects could include FORlive, FORtune and the latest FORscene/Clesh codecs. I can dig out some of the patent numbers if you are interested, or you could look at the Java player itself. And there are many press articles and features to get information from.

PS Given the number of people who have seen FORlive from this page and not proposed deletion, I'd prefer at least one other person to express an opinion before we establish a consensus to delete. Does this seem reasonable? Stephen B Streater 09:06, 22 May 2006 (UTC)

FORlive
Someone asked for some details of FORlive, so I've written some down below. Stephen B Streater 22:30, 20 May 2006 (UTC)

Overview
FORlive is a real time video codec. It is designed to compress live video for playback on remote computers, near-live, over the web - without requiring any software upgrades on the watching PCs or the web server. The real time player runs on typical PCs and Macs at up to 384x288 pixels, 25 fps for PAL, or 320x240 pixels, 30fps for NTSC.

FORlive was launched at IBC in September 2004 by Forbidden Technologies plc. It is notable for being the first widely viewed live streaming Java player, with the example page below alone receiving around 1,000,000 hits per month since 2004.

Implementation
All fetches are simple HTTP requests, so the video can be served from a standard webserver. The player is implemented in Java to ensure that Windows, MacOS and Linux computers can play back the latest version of the player without installation. Although not all computers have Java installed, for several years it has been installed as standard by major manufacturers, and the latest versions have been available as free downloads from Sun. The datarate is set at compression time and three simultaneous bitstreams are produced: "modem", "midband" and "broadband" - the average datarates and image sizes are set on the compression machines, which run Debian Linux. The "modem" and "midband" bitstreams are dynamically interchangeable by the player, which senses the datarate as it reads in files and adjusts the fetches to accommodate available bandwidth.

The compressor is easy to install: it can be plugged into a camera, the mains electricity and an ethernet port connected to the internet, and then automatically uploads live video to a webserver where it can be viewed from almost any computer in the world with internet access.

Codec details
The requirements for a real time software compressor / Java player combination covering a wide range of bandwidths and player CPU speeds place some contraints on the computational complexity available to the codec. It operates on the YUV levels directly, and does not use transforms such as DCT or wavelets, to ensure computational efficiency. The compression has two stages - a filter stage to remove noise from the source data (particularly required for cheap cameras with composite outputs) followed by a data compression / bitstream output stage.

The image is split into 2x2 blocks, and each block is treated as a single unit. Uniform blocks are encoded at 6 bits Y, and bilinearly interpolated to 8bpp on playback to give a smooth result. Non-uniform blocks are quantised and encoded using 5bpp. Colour is compressed as UV components, also quantised, but unlike Y values, these are quantised in a non-linear way to reflect the human visual system.

Apart form an initial key frame at the start of each block, only deltas are encoded.

2x2 block deltas are effectively Huffman encoded, though significant improvements over a naïve Huffman encoding are achieved by, instead of using one static Huffman table, using thousands of Huffman tables to allow the most relevant one to be chosen when each codeword is encoded/decoded, and re-evaluating the Huffman tables thousands of times per second. To allow this rapid dynamic reappraisal of the data environment, exact Huffman tables are not used, but close approximations are used instead.

The FORlive codec is covered by several patents in the UK, US, Japan and Europe.

Example of FORlive in action
You can see an example of the FORlive codec here. This demo runs off a $100 PAL composite security camera, and has been running round the clock since 2004, except for brief intermissions for upgrades. As of May 2006, the current version has run non-stop for 14205010 seconds (see Java console) ie 164 days.

Stephen B Streater 22:30, 20 May 2006 (UTC)

FORtune
Someone asked for some details of FORtune, so I've written some down below. Stephen B Streater 22:36, 20 May 2006 (UTC)

Overview
FORtune is a real time audio codec. It is designed to compress live audio for playback on remote computers, near-live, over the web - without requiring any software upgrades on the watching PCs or the web server. The audio datarate can be varied from 8kb/s to 80kb/s per channel.

Implementation
All fetches are simple HTTP requests, so the audio can be served from a standard webserver. The player is implemented in Java to ensure that Windows, MacOS and Linux computers can play back the latest version of the player without installation. FORtune can be run in conjunction with FORlive, where the video and the audio play back in sync.

Example of FORtune in action
You can see an example of the FORtune audio codec here.

Codec details to follow. Stephen B Streater 22:36, 20 May 2006 (UTC)

Some codec details
The FORtune audio codec splits the audio into sections of around 10ms. These are then converted into frequency space and quantised. The FORtune codec takes into account how loud the sound is at any point to give a constant signal:noise ratio. The audio is compressed using a similar dynamic Huffman-like compression to the FORlive video, to take into account the type of sound at any point.

The player can play back on integer only CPUs such as the ARM widely used in mobile phones. A freely downloaded mobile phone application, FORmobile (currently being used by the British Army ), is available for playing back video/audio using an integer-only ARM implementation of the audio player (and an integer-only video player).

If the audio is being played in conjunction with video, for example with the FORlive streaming video codec or the FORscene video editing codec, it is seamlessly resynched every frame to ensure the video and audio can play over any period of time without slipping out of sync.

The Java implementation of the FORtune audio codec takes a few percent of the available CPU time on typical PCs, and is negligible compared with the CPU taken to play full frame rate video on the same machine. Stephen B Streater 15:10, 21 May 2006 (UTC)

Reliable sources
FORscene has its own article now, and I'm wondering what sort of places count as reliable sources for codec information. There's quite a lot which could be said. FORscene has two codecs, Blackbird and Impala, for video and audio (see above) but the trade publications in FORscene's market are more interested in workflow in the professional post-production industry than in technical details of compression. What publications do the other codecs draw from? Stephen B Streater 09:12, 19 June 2006 (UTC)


 * Some sources I've used or seen used are:


 * ISO standards, where applicable (eg MP3, AAC)
 * ITU standards (eg G.728, G.729)
 * Government standards (eg FS-1015, FS-1016, ATSC)
 * Publications from other standards groups (Telecommunications Industry Association, xiph.org, etc)
 * Journal articles (see for example VSELP)
 * ffmpeg source code and wiki (see WMA, RealAudio)
 * Other reference source code (eg Adaptive Multi-Rate, Ogg Vorbis)
 * Hydrogenaudio listening tests (although this was disputed in Talk:Windows Media Audio)
 * doom9 codec tests (DivX, X264)
 * General links to product documentation and company web sites (see links at Windows Media Audio, RealAudio)
 * Press releases, when needed to establish dates and history (see RealVideo)
 * Publications in general media, for history (such as XviD and Sigma Designs controversy)
 * Public statements from credible persons involved in codec development (Cook Codec, Apple Lossless, VP6)
 * Standards documents are often the authoritative source by definition, and source code is inherently verifiable in that you can compile it and test it. So I tend to cite these for factual accuracy even though they can be difficult to understand.  Patents can be cited, especially if the company makes a claim regarding patents, however I tend to avoid them for technical content since people will claim all sorts of things in patents which they never actually use.  Press releases are good for historical context, but sometimes you have to read between the lines, because companies will say things which are misleading (such as the realvideo/clearvideo situation).  Independant testing is very important, but this does tend to inspire controversy.  I think hydrogenaudio's methodology is fair, but you can never please everybody.  You do have to be careful though since some companies (such as Microsoft) are infamous for paying for "independent tests" that only show the results they want shown.  Some companies outright lie (such as Nero's claim of "CD quality stereo at 48 kb/s" and other nonsense.)  So in general I'm very skeptical of press releases, except to confirm that a certain product was announced on a certain date.  If you can get first-hand statements from the people directly involved (on blogs, mailing lists) that's generally pretty good. --Mcoder 10:43, 20 June 2006 (UTC)

AVCHD or MTS?
Hello all. I'm a newbie searching for information on AVCHD and MTS. Should that not appear somewhere in this discussion? Is it too new? Thanks. —Preceding unsigned comment added by 75.99.77.130 (talk) 17:48, 21 March 2010 (UTC)

FRAPs codec lossless, but only with FFMPEG decoder
Makes no sense, isn't claimed to be lossless by the company that makes it - citation was to a forum where people discuss how lossless RGB changes the chroma subsampling - not the same thing as having a lossless codec. Not even sure why it said FFMPEG decoder, this doesn't just apply to just FRAPs codec either, why is it important what FFMPEG can or can't decode, what's that got to do with whether or not FRAPs (or other codecs) are lossless or not?

Maybe we'd have it as a lossless codec if the company's website said, FRAPs is a lossless codec. I mean, if it were, surely it would be part of the advertised feature-set? 86.135.238.18 (talk) 18:48, 23 June 2012 (UTC)
 * Would you look at that, I did a few tests, and it does look lossless. I can't find a good citation though. 86.135.238.18 (talk) 19:33, 23 June 2012 (UTC)

"Very fast"
I've marked an unsourced claim that a codec is "very fast" with cn. Not sure whether it should be mentioned at all, since most codecs listed here have no information about speed or quality. —Frungi (talk) 19:56, 8 January 2013 (UTC)
 * Removed. The Russian site (surprisingly as it may seem) is really one of the few available sources with reproducible video codec tests.--Regression Tester (talk) 01:12, 10 January 2013 (UTC)

List of formats
The article appears to be a list of data formats (the first sentence even says so), not codecs ("device or computer program capable of encoding or decoding"), so should be renamed accordingly. 203.176.108.99 (talk) 00:03, 20 February 2013 (UTC)
 * I don't know what data formats are but the article definitely contains a (long) list of audio and video codecs.--Regression Tester (talk) 00:43, 20 February 2013 (UTC)

MQA - Master Quality Authenticated
Should this be added to the list?

New lossless audio codec launched Dec 2014.

Company site

3rd party news article covering launch

Also mentioned in BBC Click episode 17-Jan-15 - iPlayer link — Preceding unsigned comment added by 82.37.220.173 (talk) 12:02, 18 January 2015 (UTC)

EL collection (spam trap)
How about a traditional list with required articles (no red links) and no references? – Be..anyone (talk)  21:40, 11 April 2016 (UTC)

Merge from List of open-source codecs
That list has highlighted that "open" is a multi-factored thing - like having an open-source encoder, open-source decoder, and being free of patents. The status of each of those things could be indicated in this list if it were turned into a simple table. -- Beland (talk) 04:38, 20 May 2016 (UTC)
 * You make some good points about defining "open-source" more distinctly. Fortunately, that can be done in the existing List of open-source codecs article.
 * Merging, on the other hand, does not seem like a good solution. Converting List of codecs to tables would create a large overlap with Comparison of audio coding formats and Comparison of video codecs. (For audio, some of the codec-specific info is in the "Open-source Implementations (codecs)" column in the General information section.) List of codecs is hierarchical. Capturing that hierarchy in HTML tables, or improving its organisation in table format, is not nearly as easy as adding column three columns to a flat list.
 * Also, List of open-source codecs has a significant daily readership for whom conciseness is an advantage. Readers of List of codecs would have to sift through a long article to find that information. Redirection would also be a problem.
 * Instead, we could ask: How can we make List of open-source codecs a better article for its readers? —Ringbang (talk) 03:51, 8 January 2017 (UTC)
 * Closed merge proposal, given consensus to improve rather than merge. Klbrain (talk) 21:38, 16 March 2018 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified one external link on List of codecs. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20080223010804/http://www.doom9.org/codec-comparisons.htm to http://www.doom9.org/codec-comparisons.htm

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 10:32, 29 December 2017 (UTC)

Lossless video - generational loss vs initial loss, and GIF
tl;dr: Should GIF be added to the lossless video list?

I'm wondering if (animated) GIF should be added to the list of lossless video codecs. The pros are that it is very much a video format, it is lossless in that there is no generational loss, and for those videos for which it is well-suited (e.g. a limited color input where few pixels change between frames) it outperforms h264 lossless, h265 lossless, FFV1, MSU lossless, YULS, VP9-losless, and others by orders of magnitude, and does not require a x2, x4, or x8 size constraint.

The cons are that there is a first-time loss (colors reduced to a maximum 256 color palette per frame - although GIFs can switch palettes throughout their run, this is rarely used), few video players support GIF files, and those that do rarely support seeking the timeline - even if the GIF is constructed so that there are full frames available. In terms of the first-time loss, this is true for most formats considered lossless, as they often convert color spaces from regular RGB or even 10bit RGB for their encoders to work well.

Due to the extremely high compression ratio that can be reached for those specific cases for which other codecs are abysmally ill-suited, I would suggest that GIF be considered - but wanted to write my reasoning and seek feedback. Kmqz (talk) 22:48, 12 May 2018 (UTC)
 * Well, it can be considered a video compression format. But this article is a list of video codecs. A video codec is not a video compression format. This is a list of software programs and libraries. GIF is not a codec, it is a format. So I guess it could be included, but only if the GIF section lists notable software implementations, which is what this article is really about.&mdash;J. M. (talk) 23:16, 12 May 2018 (UTC)
 * Ah, gotcha. Yeah, it would be out of place here then (until such a time as that GIF's compression technique would be embraced for a proper codec, at which point it would no longer be GIF, but somethingLZWsomething). Thanks for clarifying that. Kmqz (talk) 03:59, 13 May 2018 (UTC)

List merge
reverted my attempt to move unnecessary detail from Video codec to this list. I know that this move created some overlap here and I hoped we could iron that out over time. I don't feel it would be a good idea to restore this material to Video codec so I'll reproduce it below. ~Kvng (talk) 18:33, 19 March 2019 (UTC)

H.265/MPEG-H HEVC codecs

 * x265: A GPL-licensed implementation of the H.265 video standard. x265 is only an encoder.

H.264/MPEG-4 AVC codecs

 * x264: A GPL-licensed implementation of the H.264 video standard. x264 is only an encoder.
 * Nero Digital: Commercial MPEG-4 ASP and AVC codecs developed by Nero AG.
 * QuickTime H.264: H.264 implementation released by Apple.
 * DivX Pro Codec: An H.264 decoder and encoder was added in version 7.

H.263/MPEG-4 Part 2 codecs

 * DivX Pro Codec: A proprietary MPEG-4 ASP codec made by DivX, Inc.
 * Xvid: Free/open-source implementation of MPEG-4 ASP, originally based on the OpenDivX project.
 * FFmpeg MPEG-4: Included in the open-source libavcodec codec library, which is used by default for decoding or encoding in many open-source video players, frameworks, editors and encoding tools such as MPlayer, VLC, ffdshow or GStreamer. Compatible with other standard MPEG-4 codecs like Xvid or DivX Pro Codec.
 * 3ivx: A commercial MPEG-4 codec created by 3ivx Technologies.

H.262/MPEG-2 codecs

 * x262: A GPL-licensed implementation of the H.262 video standard. x262 is only an encoder.

Microsoft codecs

 * WMV (Windows Media Video): Microsoft's family of proprietary video codec designs including WMV 7, WMV 8, and WMV 9. The latest generation of WMV is standardized by SMPTE as the VC-1 standard.
 * MS MPEG-4v3: A proprietary and not MPEG-4 compliant video codec created by Microsoft. Released as a part of Windows Media Tools 4. A hacked version of Microsoft's MPEG-4v3 codec became known as DivX ;-)

Google (On2) codecs

 * VP6, VP6-E, VP6-S, VP7, VP8, VP9: Proprietary high definition video compression formats and codecs developed by On2 Technologies used in platforms such as Adobe Flash Player 8 and above, Adobe Flash Lite, Java FX and other mobile and desktop video platforms. Supports resolution up to 720p and 1080p. VP9 supports resolutions up to 2160p. VP8 and VP9 have been available under the New BSD License by Google with source code available as the libvpx VP8/VP9 codec SDK.
 * libtheora: A reference implementation of the Theora video compression format developed by the Xiph.org Foundation, based upon On2 Technologies' VP3 codec, and christened by On2 as the successor in VP3's lineage. Theora is targeted at competing with MPEG-4 video and similar lower-bitrate video compression schemes.

Lossless codecs
See the Audio full list and Video full list.

Other codecs

 * Apple ProRes: Is a lossy video compression format developed by Apple Inc.
 * Schrödinger and dirac-research: implementations of the Dirac compression format developed by BBC Research at the BBC. Dirac provides video compression from web video up to ultra HD and beyond.
 * DNxHD codec: a lossy high-definition video production codec developed by Avid Technology. It is an implementation of VC-3.
 * Sorenson 3: A video compression format and codec that is popularly used by Apple's QuickTime, sharing many features with H.264. Many movie trailers found on the web use this compression format.
 * Sorenson Spark: A codec and compression format that was licensed to Macromedia for use in its Flash Video starting with Flash Player 6. It is considered as an incomplete implementation of the H.263 standard.
 * RealVideo: Developed by RealNetworks. A popular compression format and codec technology a few years ago, now fading in importance for a variety of reasons.
 * Cinepak: A very early codec used by Apple's QuickTime.
 * Indeo, an older video compression format and codec initially developed by Intel.

This Article is a List of Software called: CODECS
This Article is a List of Software called: CODECs it is not Article containing list of dead mere Codecs Specification / Standard, it is list of Codecs, and that is software: Decoder and Encoder.

"Computer program" == is software!
 * Essential Video Coding (EVC; MPEG-5 Part 1; developed; consumer products under-development)
 * REVC Encoder/Decoder of free base profile
 * XEVD (the eXtra-fast Essential Video Decoder) both main and base profile
 * XEVE (the eXtra-fast Essential Video Encoder) both main and base profile


 * Low Complexity Enhancement Video Coding (LCEVC; MPEG-5 Part 2; developed; consumer products under-development)
 * FFmpeg (with support for over 20 base encoders)
 * Patch for AOSP
 * ExoPlayer (Android)
 * AVPlayer (iOS)
 * Microsoft UWP (Windows)
 * web players: HLS.js, Shaka Player, video.js
 * integration for HTML5 web browsers
 * lots of playback apps in Android/iOS/Microsoft stores

FFmpeg is mentioned next to almost every codec standard.

And some user change statement from true to false, by Writing that MPEG-5 codecs are under-development,

It is false, as Those 2 codecs are NOW fully developed.

Only Consumer Hardware is steel under development, or additional implementation in Software. — Preceding unsigned comment added by 46.187.199.166 (talk • contribs)
 * Yes, this article is a list of codecs—or more exactly, as the first sentence explains, a list of coding formats and codecs that implement the coding formats. Feel free to add codecs to the list, as long as you really understand what a codec is. For example, a player is not a codec. A web application or mobile playback applications are not codecs. An operating system is not a codec. A patch for an operating system is not a codec. And so on.
 * Please make sure you really understand what this article is about, what a video coding format, audio coding format, video codec and audio codec is. For example, a codec does not necessarily have to be software, there are hardware codecs, too, or combinations of hardware and software. Please make sure you understand the difference between a standard an an implementation, and the difference between a codec library and application software (that uses the codecs). Please make sure you understand the logic of this article and its list—that is, a list of coding formats, where each item consists of a sublist containing codecs (i.e. encoding/decoding libraries) that implement the coding format in software.
 * So, please, only add things to this article if you really understand what all these things mean.—J. M. (talk) 19:42, 31 August 2021 (UTC)