FFV1

FFV1, which stands for "FF video codec 1", is a lossless intra-frame video codec. It can use either variable-length coding or arithmetic coding for entropy coding. The encoder and decoder are part of the free, open-source library libavcodec in the project FFmpeg since June 2003.[1] FFV1 is also included in ffdshow and LAV Filters,[2] which makes the video codec available to Microsoft Windows applications that support system-wide codecs over Video for Windows (VfW) or DirectShow. FFV1 is particularly popular for its performance regarding speed and size, compared to other lossless preservation codecs, such as M-JPEG2000.[3][4][5] The European Broadcasting Union (EBU) lists FFV1 under the codec-family index "31" in their combined list of video codec references.[6]

FFV1
Developed byMichael Niedermayer (FFmpeg)
Initial release9 June 2003 (2003-06-09)
Latest release
Version 3 (FFV1.3)
(3 August 2013 (2013-08-03))
Type of formatVideo compression format
Contained byAVI, MKV, MOV, NUT, etc.
WebsiteFFV1 Video Codec Specification (in progress)

Video archiving

For long-term preservation of digital video sustainable container formats as well as audio/video codecs are necessary. There is no consensus to date among the archival community as to which file format or codecs should be used for preservation purposes for digital video.[7] The previously proclaimed encodings were Motion JPEG 2000 (lossless)[8] and uncompressed video.[9]

FFV1 proved to be a viable archival encoding and the U.S. Library of Congress began regarding it as a suitable option for preservation encoding in 2014.[3][10] With compression ratios comparable to lossless JPEG 2000 and lower computing requirements, it is being used by archives, particularly where the collections do not feature extensive broadcast materials and instead consist of oral history and the like.[11][12]

As of 2018, standardisation of FFV1 through the Internet Engineering Task Force (IETF) is a work in progress as part of the European PREFORMA Project,[13] as well as implementation of a conformance checker for FFV1 in the Matroska container.[14] Details of FFV1's standardization plan[15] have been prepared by MediaArea (authors of MediaInfo) as part of their conformance checking tool "Media CONCH".[16]

It is also listed as a format option for long-term preservation of moving images on sites of the U.S. Library of Congress',[10][17] State Records NSW[7] and others. The Society of American Archivists has published a paper in August 2014, suggesting only FFV1 as preservation codec for video.[18]

The Digital Preservation project at the U.S. Library of Congress identified AVI and Matroska as common container formats for FFV1.[19][20]

List of institutions known to use FFV1
Austria
Australia
Belgium
  • meemoo, the Flemish Institute for Archives announced in June 2020 that they would start a major operation transcoding and rewrapping their MXF wrapped JPEG2000 files resulting from digitisation projects for the cultural heritage sector material to MKV wrapped FFV1 files. In 2019 they had already announced that MKV-FFV1 would be the mezzanine format of their migration project for DV, DVCAM and DVCPRO cassettes.
Canada
France
Germany
  • SMIDAK Filmproduktion[28]
Ireland
Slovakia
Slovenia
Switzerland
United Arab Emirates
  • Sharjah Media Corporation (SMC).[32]
United Kingdom
United States

Development and improvements

The "Österreichische Mediathek" has also developed DVA-Profession[35] a Free Software solution for archive-suitable mass video digitization, mainly using FFV1 as video encoding throughout the whole workflow, without transcoding. Additionally, they have initiated the development of "FFV1.3" (=version 3 of FFV1) together with Michael Niedermayer (FFmpeg), Peter Bubestinger and Dave Rice.

FFV1.3 contains improvements and new features such as support for multi-threaded encoding/decoding, error resilience and integrity validation by CRC checksums, storing of display aspect ratio (DAR) and field order. It was tested for over 1 year,[36] and officially released stable for production in August 2013.[37]

In August 2016, support for 48bit/16bpc (=bits per component) in RGB was added.[38] Before that, 16bpc in FFV1 were only supported in YCbCr and RGB was limited to 14bpc.

Use as a preservation codec

Within the video archiving domain, the interest in FFV1 is increasing, as can be seen in a thread on the AMIA-L mailing list,[39] the PrestoCentre Forum[40] or the Archivematica mailing list.[41][42] Companies are also picking up FFV1 support. For example, NOA (formerly "NOA Audio Solutions"), announced support for the FFV1 in their product line in July 2013[43] and KEM-Studiotechnik released a film-scanner with FFV1 output in November 2013.[44]

In an interview for The New York Times magazine about "Tips on Archiving Family History",[45] Bertram Lyons from the U.S. Library of Congress says:

"[...] for video, there are many choices when it comes to codecs (the way the bits are encoded/decoded to represent the visual data, e.g., ffv1, H.264, Apple ProRes) [...]"

In January 2013, the possible use and adoption of FFV1 as an archiving codec was addressed in the issue of PrestoCentre's[46] AV Insider magazine:[47]

"FFV1 has many beneficial technical features [...], but adoption rates are relatively low compared with alternatives, for example JPEG2000. [...] But holding back too long only serves to self-perpetuate the status of FFV1.

The adoption by Archivematica and the Austrian Mediathek with their active promotion of FFV1 along with others may start to break this vicious circle. This could lead to a virtuous circle of wider take-up, to shared development, to incorporation into commercial products and a host of other benefits for the community."

PACKED - the "Centre of Expertise in Digital Heritage" in Belgium, say in an article about video formats for archiving:[48]

"When removing the proprietary codecs from this list, only a few are left. [...] This basically leaves heritage institutions that want to use a lossless codec, with only two options: Jpeg2000 and FFV1."

In 2015, the International Federation of Television Archives (FIAT/IFTA) mentioned FFV1 explicitly in their call-for-presentations for their annual World Conference, asking "Is FFV1 the new JPEG2000"?.[49] A workshop titled "FFV1 for Preservation" is also featured.[50]

Applications supporting FFV1

Here is a list of applications known to be able to read and/or write FFV1 video files, either natively or by installing codec packages.

Entries marked with "-" means that they generally only support either encoding or decoding.

The term "built-in" means that the application can handle FFV1 without the necessity to install additional codec packages. Applications that come with FFV1 support out of the box, usually use FFmpeg's or Libav's libraries in order to do so.

The list is far from being complete, and will be augmented over time:

ApplicationEncodingDecodingMethod
Adobe PremiereYesYesDirectShow[51][52]
Archivematica[53]YesYesbuilt-in
AVIDUn­knownYesTheir transcoder can handle FFV1
AvidemuxNo (removed in v2.6 and later)Yesbuilt-in
BlenderYes[54]Yesbuilt-in
DVA-Profession[55]YesYesbuilt-in
ffdshow-tryoutsYesYesbuilt-in
FFmpegYesYesbuilt-in
Harris Broadcast VelocityYesYesVideo for Windows[51]
kdenliveYesYesbuilt-in
KEM Scan (motion picture film scanner)[44][56]Yes-built-in
LAV Filters[52]YesYesbuilt-in
MediaInfo-Yesbuilt-in
Media Lovin' Toolkit[57]YesYesbuilt-in
Media Player Classic-Yesbuilt-in
MPlayer/MEncoderYesYesbuilt-in
NOA MediaButler[58]YesYesbuilt-in
QUADRIGA Video[59]Yes[60]Un­knownUn­known
Shotcut[61]YesYesbuilt-in
Sorenson SqueezeUn­knownYesbuilt-in
VirtualDubYesYesVideo for Windows[51]
VLC media playerNoYesbuilt-in
Windows Media PlayerUn­knownYesDirectShow[51][52]

Compression details

FFV1 is not strictly an intra-frame format; despite not using inter-frame prediction, it allows the context model to adapt over multiple frames. This can be useful for compression due to the very large size of the context table, but can be disabled to force the encoder to generate a strictly intra-frame bitstream. As the gained compression seems to decrease[62] with later versions of FFV1 (version 2,3), the use of GOP size greater than "1" might disappear in the future.

Prediction process

During progressive scanning of a frame, the difference between a current pixel and its predicted value, judging by neighboring pixels, is sent to the entropy-coding process. The prediction is done as follows:

Prediction = Median( Top, Left, Top + Left - TopLeft )

The third value, "Top + Left - TopLeft", is effectively equivalent to applying the top predictor to the current and the left sample, followed by applying the left predictor to the prediction residual of the top predictor. This method, also known as the gradient, exploits both horizontal and vertical redundancy. So in simple terms the prediction is the median of the top, left, and gradient prediction methods. For improved performance and simplicity, the edges of the frame are assumed to be zero to avoid special cases. The prediction in encoding and decoding is managed using a ring buffer.[63]

Entropy coding process

The residuals are coded using either variable-length coding or arithmetic coding. Both options use a very large context model. The "small" context model uses (11*11*11+1)/2=666 contexts based on the neighboring values of (Left-TopLeft), (TopLeft-Top), and (Top-TopRight). The "large" context model uses (11*11*5*5*5+1)/2=7563 contexts based on the same values as before, but also (TopTop - Top) and (LeftLeft-Left), where "TopTop" is the pixel two above the current one vertically, and "LeftLeft" is the pixel two to the left of the current one. In arithmetic coding, each "context" actually has 32 sub-contexts used for various portions of coding each residual, resulting in a grand total of 242,016 contexts for the "large" model.

Early experimental versions of FFV1 used the CABAC Arithmetic coder from H.264, but due to the uncertain patent/royalty situation, as well as its slightly worse performance, CABAC was replaced by Range encoding.

Status

On April 16, 2006, a commit-message by Michael Niedermayer confirmed that the bitstream of FFV1 (version 1) is frozen:[64]

"ffv1 and ffvhuff haven't changed since a long time and no one proposed any changes within 1 month after my warning so they are officially no longer experimental and we will guarantee decodability of files encoded with

the current ffv1/ffvhuff in the future"

Codec
Version 1 (FFV1.1)

The bitstream of version 1 is frozen and considered stable for production use since April 2006.[64] The remark "experimental" in the source code was overlooked back then and removed in March 2010.[65]

Version 2 (FFV1.2)

Version 2 was an intermediate version, that was never officially released and should not be used for production purpose.

Version 3 (FFV1.3)

The bitstream of version 3 is frozen since August 3, 2013.[66] The final commit marking this version as officially released for production usage was on August 26, 2013.[37] There is still no any VFW multithreaded encoder of FFV1.3 for Windows in 2017. FFdshow can encode only FFV1.1 stream with single CPU core.

Version 4 (FFV1.4)

Improvements beyond FFV1.3 are work in progress and being discussed on the IETF "CELLAR" mailing list.[67] Planned are additional support for color-handling, especially non-linear/logarithmic color spaces.

Documentation

The current authoritative documentation was started in April 2012, and stayed in a very basic state until 2015.[68] In 2015, as part of the IETF standardization process, the documentation is now improved and reviewed by the CELLAR working group in close cooperation with Michael Niedermayer.[69]

See also

References
  1. "Repository history of FFV1's sourcecode in FFMPEG repository". Michael Niedermayer. Archived from the original on 23 March 2012. Retrieved 21 October 2010.
  2. https://code.google.com/p/lavfilters/
  3. Bubestinger, Peter. "Comparing video codecs and containers for archives". Österreichische Mediathek. Retrieved 8 October 2014.
  4. "MSU Lossless Video Codecs Comparison" (PDF). MSU Graphics & Media Lab (Video Group). March 2014. Retrieved 8 October 2014.
  5. "Graphs about FFV1 performance (transcoding, retrieval)". NOA GmbH. Retrieved 8 October 2014.
  6. Evain, Jean-Pierre (15 August 2016). "Video Compression Code (A combined list of video codecs inc. EBU, DVB and MPEG)". European Broadcasting Union. Retrieved 19 September 2016.
  7. "Formats and codecs for digital video preservation (Guideline 22)". NSW State Records. August 2013. Archived from the original on 10 November 2013. Retrieved 10 November 2013.
  8. "Motion JPEG 2000 at digitalpreservation.gov". U.S. Library of Congress. Retrieved 6 March 2013.
  9. Fleischhauer, Carl; Frost, Hannah; Beard, Isaiah (November 2010). "AMIA/IASA 2010 - Wrappers and Codecs: A Survey of Selection Strategies". AMIA/IASA. Retrieved 6 October 2013.
  10. Fleischhauer, Carl; Egan, Courtney (8 September 2014). "Digital File Formats for Videotape Reformatting". FADGI (U.S. Library of Congress). Retrieved 8 October 2014.
  11. http://www.digitizationguidelines.gov/about/
  12. Fleischhauer, Carl; Murray, Kate (3 December 2014). "Comparing Formats for Video Digitization". FADGI (U.S. Library of Congress). Retrieved 8 September 2015.
  13. "PREservation FORMAts for culture information/e-archives (PREFORMA)". Retrieved 2015-09-24.
  14. Murray, Kate; Rice, Dave; Blewer, Ashley (September 23, 2015). "Improving Technical Options for Audiovisual Collections Through the PREFORMA Project". U.S. Library of Congress. Retrieved 2015-09-24.
  15. Fallon, Tessa; Rice, Dave; Blewer, Ashley (March 3, 2015). Conch – Appendix on Standardization Exercises (PDF) (Report). MediaArea. Retrieved 2015-09-24.
  16. "CONformance CHecking for audiovisual files (CONCH)". Retrieved 2015-09-24.
  17. "FFV1 at digitalpreservation.gov". U.S. Library of Congress. 29 May 2012. Retrieved 10 November 2013.
  18. Austen, Barbara; Bowling, Melissa; Deakyne, Holly; Evans, Ryan (7 August 2013). "Electronic Records Project" (PDF). Society of American Archivists. Retrieved 21 October 2014.
  19. "AVI File Format with FFV1 video encoding". AVI_FFV1. Digital Preservation. LoC. 2012-07-20. fdd000349. Retrieved 2015-04-22.
  20. "Matroska File Format with FFV1 video encoding". Matroska_FFV1. Digital Preservation. LoC. 2012-05-29. fdd000343. Retrieved 2015-04-22.
  21. landesmuseum.net
  22. mediathek.at
  23. Lewetz, Hermann (30 August 2011). "DVA-Profession used at the Austrian Mediathek: Codec". Österreichische Mediathek. Archived from the original on 14 October 2014. Retrieved 8 October 2014.
  24. http://vancouver.ca/ctyclerk/archives/
  25. "Matroska video container information at digitalpreservation.gov". U.S. Library of Congress. Retrieved 10 May 2012.
  26. "A City of Vancouver Archives' blog post mentioning their use of FFV1". City of Vancouver Archives. Retrieved 10 May 2012.
  27. Musée d'art contemporain de Montréal (Archives and Media Centre)
  28. "SMIDAK Filmproduktion". Retrieved 2016-03-31.
  29. "RTVS Slovakia: Complete Video Archive System from NOA". NOA GmbH. 1 September 2014. Retrieved 10 May 2017.
  30. "National Broadcaster of Slovenia is first in successfully deploying Complete Video Archive Solutions from NOA". NOA GmbH. 2014. Retrieved 10 May 2017.
  31. "Image sequence into Matroska/FFV1". AV Preservation by reto.ch. 11 December 2016. Retrieved 10 May 2017.
  32. "Installation at SMC: United Arab Emirates First for NOA". NOA Archive GmbH. March 2018. Retrieved 15 March 2017.
  33. "Media micro-services and archival workflows at CUNY Television". 10 November 2015. Retrieved 19 August 2016.
  34. Esteva, Maria; Vega, Karla; Henriksen, Vandy; Lee, Jennifer; Martin, Wendy (May 2013). "Automated Archiving of DVD Content (Presentation at TCDL 2013)". Texas Advanced Computing Center (TACC) and University of Texas at Austin - Libraries. Archived from the original on 3 June 2015. Retrieved 21 October 2014.
  35. "dva-profession.mediathek.at". Archived from the original on 2012-05-25. Retrieved 2012-05-10.
  36. Bubestinger, Peter (6 February 2014). "FFV1 performance statistics". Österreichische Mediathek. Retrieved 8 October 2014.
  37. Niedermayer, Michael (26 August 2013). "Repository commit message: FFV1.3 released as stable". FFmpeg. Archived from the original on 4 March 2016. Retrieved 29 August 2013.
  38. Niedermayer, Michael (16 August 2016). "Repository commit message: avcodec/ffv1enc: Add RGB48 support". FFmpeg. Retrieved 18 August 2016.
  39. "FFV1 discussion on AMIA-L mailing list". AMIA. December 2012. Retrieved 6 March 2013.
  40. "Digital master archive format". PrestoCentre Forums. 26 October 2012. Archived from the original on 15 April 2013. Retrieved 6 March 2013.
  41. "FFV1 vs other formats for preservation". Archivematica mailing list. 24 September 2012. Retrieved 6 March 2013.
  42. "Digital film archiving in big scale". Archivematica mailing list. 29 January 2013. Retrieved 6 March 2013.
  43. "Company announcement confirming FFV1 support". NOA Audio Solutions. 10 July 2013. Archived from the original on 13 April 2016. Retrieved 29 August 2013.
  44. Kober, Helmfried (14 November 2013). "KEM SCAN Film Scanner Data Sheet" (PDF). KEM-Studiotechnik. Retrieved 30 April 2015.
  45. Lyons, Bertram (2013). "Ask an Expert: Tips on Archiving Family History, Part 3". The New York Times Magazine (online). The New York Times.
  46. prestocentre.org
  47. Addis, Matthew (2013). "Crossing the Chasm (From Research Results to Sustainable Tools and Services for AV)". AV Insider Magazine. No. #3. PrestoCentre. pp. 14–15.
  48. Emanuel Lorrain (March 2014). "A short guide to choosing a digital format for video archiving masters". PACKED, Belgium. Retrieved 2 June 2014.
  49. "Conference Call for Presentations, FIAT/IFTA World Conference Vienna 7-10 October 2015" (PDF). International Federation of Television Archives. 13 May 2015. Archived from the original (PDF) on 2015-10-10. Retrieved 2015-09-01.
  50. "FIAT/IFTA World Conference 2015, Programme Day 1". International Federation of Television Archives. Aug 2015. Archived from the original on 2015-09-10. Retrieved 2015-09-01.
  51. "ffdshow tryouts". Retrieved 27 April 2015.
  52. "LAVFilters (Open-Source DirectShow Media Splitter and Decoders)". Hendrik Leppkes. Retrieved 27 April 2015.
  53. "Archivematica - Format policies". Artefactual Systems Inc. Retrieved 2015-04-30.
  54. "Blender v2.6 Manual: Render/Output/Video". Blender Foundation. 18 November 2011. Retrieved 4 August 2013.
  55. "DVA-Profession used at the Austrian Mediathek: Codec". Österreichische Mediathek. Archived from the original on 2016-04-17. Retrieved 2016-03-31.
  56. "KEM Scan". KEM Studiotechnik GmbH. Retrieved 2015-04-30.
  57. "Media Lovin Toolkit (MLT/melt)". Dan Dennedy. Retrieved 2015-04-27.
  58. "NOA MediaButler". NOA Audio Solutions GmbH. Retrieved 2015-04-27.
  59. "Video Tape Migration with Quadriga". CubeTec International. Retrieved 2016-03-31.
  60. "QUADRIGA Video Specifications". CubeTec International. Retrieved 2016-03-31.
  61. "Shotcut". Dan Dennedy. Retrieved 2015-04-27.
  62. "Message on FFmpeg developer mailing list about the impact of GOP size parameter of FFV1". Retrieved 10 May 2012.
  63. Michael Niedermayer (2013-09-05). "FFV1 Video Codec Specification". FFmpeg. Retrieved 2015-03-18.
  64. "Repository commit message: Bitstream FFV1.1 frozen". Michael Niedermayer. 14 April 2006. Archived from the original on 4 March 2016. Retrieved 8 May 2012.
  65. "Repository commit message". Michael Niedermayer. 22 March 2010. Archived from the original on 23 March 2012. Retrieved 21 October 2010.
  66. "Mailing list post: Bitstream FFV1.3 frozen". Michael Niedermayer. 3 August 2013. Retrieved 29 August 2013.
  67. "Discussion thread on FFV1 version 4 (on IETF CELLAR mailing list)". 2016-01-05. Retrieved 2016-08-18.
  68. Michael Niedermayer (2013-11-03). "The FFV1 Video Codec Specification (2013)". Retrieved 2016-08-19.
  69. Michael Niedermayer (2016-07-31). "The FFV1 Video Codec Specification (Development Draft)". Retrieved 2016-08-19.
  70. "Lossless Video Codecs Comparison '2007". Graphics & Media Lab Video Group of Moscow State University. Retrieved 2015-04-27.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.