/
fdd000341.xml
344 lines (344 loc) · 25.8 KB
/
fdd000341.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
<?xml version="1.0" encoding="UTF-8"?>
<fdd:FDD id="fdd000341" titleName="FF Video Codec 1, Version 0, 1 and 3" shortName="FFV1_v0-1-3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:fdd="http://www.loc.gov/preservation/digital/formats/schemas/fdd/v1" xsi:schemaLocation="http://www.loc.gov/preservation/digital/formats/schemas/fdd/v1 http://www.loc.gov/preservation/digital/formats/schemas/fdd/v1/fdd-v1-2.xsd">
<fdd:properties>
<fdd:gdfrGenreSelection>
<fdd:gdfrGenre>moving-image</fdd:gdfrGenre>
</fdd:gdfrGenreSelection>
<fdd:formatCategories>
<fdd:category>encoding</fdd:category>
</fdd:formatCategories>
<fdd:gdfrComposition>unitary</fdd:gdfrComposition>
<fdd:gdfrForm>binary</fdd:gdfrForm>
<fdd:gdfrConstraint>unstructured</fdd:gdfrConstraint>
<fdd:gdfrBasis>sampled</fdd:gdfrBasis>
<fdd:updates>
<fdd:date>2023-10-10</fdd:date>
</fdd:updates>
<fdd:draftStatus>Preliminary</fdd:draftStatus>
</fdd:properties>
<fdd:identificationAndDescription>
<fdd:fullName>FF Video Codec 1, Version 0, 1, and 3</fdd:fullName>
<fdd:keywords>
<fdd:keyword>lossless compression</fdd:keyword>
</fdd:keywords>
<fdd:description>
<p>FFV1 is a lossless intra-frame video codec from the <a href="http://ffmpeg.org/">FFmpeg</a> project. The specification for FFV1 versions 0, 1 and 3 was published by IETF as <a href="https://www.ietf.org/rfc/rfc9043.txt">RFC 9043: FFV1 Video Coding Format Versions 0, 1, and 3</a> in August 2021. (There is no stable version 2. See <a href="#notes">Notes</a> for more information.)</p>
<p>The design of FFV1 considers the storage of image characteristics, data fixity, and the optimized use of encoding time and storage requirements. FFV1 is designed to support a wide range of lossless video applications such as long-term audiovisual preservation, scientific imaging, screen recording, and other video encoding scenarios that seek to avoid the generational loss of lossy video encodings.</p>
<p>Note: This brief update in November 2021 primarily provides an update on the publication of RFC 9043 by IETF. A more complete update will be done in early 2022. </p>
</fdd:description>
<fdd:shortDescription>FFV1 is a lossless intra-frame codec standardized as IETF RFC 9043: FFV1 Video Coding Format Versions 0, 1, and 3. </fdd:shortDescription>
<fdd:productionPhase>Middle state, used for storage or archiving</fdd:productionPhase>
<fdd:relationships>
<fdd:relationship>
<fdd:typeOfRelationship>Has later version</fdd:typeOfRelationship>
<fdd:relatedTo>
<fdd:titleName>FFV1 version 4</fdd:titleName>
</fdd:relatedTo>
<fdd:comment>Not described at this time. Specification still in development at IETF</fdd:comment>
</fdd:relationship>
<fdd:relationship>
<fdd:typeOfRelationship>Used by</fdd:typeOfRelationship>
<fdd:relatedTo>
<fdd:id>fdd000349</fdd:id>
<fdd:shortName>AVI_FFV1</fdd:shortName>
<fdd:titleName>AVI File Format with FFV1 video encoding</fdd:titleName>
</fdd:relatedTo>
<fdd:comment/>
</fdd:relationship>
<fdd:relationship>
<fdd:typeOfRelationship>Used by</fdd:typeOfRelationship>
<fdd:relatedTo>
<fdd:id>fdd000343</fdd:id>
<fdd:shortName>Matroska_FFV1</fdd:shortName>
<fdd:titleName>Matroska File Format with FFV1 video encoding</fdd:titleName>
</fdd:relatedTo>
<fdd:comment/>
</fdd:relationship>
</fdd:relationships>
</fdd:identificationAndDescription>
<fdd:localUse>
<fdd:experience>As of November 2021, the National Audio-Visual Conservation Center (NAVCC) has ingested several hundred ffv1/mkv files. These files were received from CUNY-TV through the American Archive of Public Broadcasting and the Library will receive many more of these files through the AAPB in the future.</fdd:experience>
<fdd:preference>FFV1 codec in the Matroska container is a 'preferred' format in the Recommended Formats Statement for <a href="http://www.loc.gov/preservation/resources/rfs/moving.html"> Video -- File-based</a> moving image works.</fdd:preference>
</fdd:localUse>
<fdd:sustainabilityFactors>
<fdd:disclosure>
<p>Full and open disclosure. The Internet Engineering Task Force (IETF) published <a href="https://www.ietf.org/rfc/rfc9043.txt">RFC 9043: FFV1 Video Coding Format Versions 0, 1, and 3</a> in August 2021. See history section of the <a href="#notes">Notes</a> below which also reports on the CELLAR IETF standardization project launched in 2015.</p>
</fdd:disclosure>
<fdd:documentation>
<p>Published as <a href="https://www.ietf.org/rfc/rfc9043.txt">RFC 9043: FFV1 Video Coding Format Versions 0, 1, and 3</a> in August 2021. The <a href="http://www1.mplayerhq.hu/~michael/ffv1.html">FFV1 Video Codec Specification</a> site from Michael Niedermayer has an undated legacy version from pre-IETF work. </p>
<p>FFmpeg's <a href="https://github.com/FFmpeg/FFV1">FFV1 GitHub repository</a> serves as the drafting source of the FFV1 specification. According to the README, "The FFV1 specification was initially written in lyx. In July 2015 the formatting of the specification was transitioned to Markdown to be used with xml2rfc version 2. In August 2019 the formatting was transitioned to target xml2rfc version 3." </p>
</fdd:documentation>
<fdd:adoption>
<p>Increasing adoption in heritage repositories including as a preferred format for the Library of Congress in 2023, especially now that RFC 9043 is published. But the success of the <a href="https://mediaarea.net/NoTimeToWait">No Time to Wait (NTTW)</a> series of symposiums starting 2016 and initially sponsored as part of the European <a href="http://www.preforma-project.eu/project.html">PREFORMA</a> (PREservation FORMAts for culture information/e-archives) project played a large part in the rapid spread of adoption in recent years. Very early adopters include the <a href="http://download.das-werkstatt.com/pb/mthk/info/video/FAQ-digital_video_archiving.html">Austrian Mediathek</a> using FFV1 wrapped in <fddLink id="fdd000059">AVI</fddLink> for their preservation masters and <a href="http://www.vancouverarchives.ca/2011/10/06/a-day-in-the-lives-of-2-archivists-gone-digital/">The City of Vancouver Archives</a> chose FFV1 wrapped in the <fddLink id="fdd000342">Matroska</fddLink> container, as discussed briefly on the archives' <a href="http://www.vancouverarchives.ca/2011/11/03/celebrating-%E2%80%9Chollywood-north%E2%80%9D-yaletown-productions-inc-fonds/">blog</a>. Significant influencers for FFV1 adoption include high profile institutions including The New York Public Library's <a href="https://nypl.github.io/ami-preservation/pages/amiLabs/ami-labs.html">AMI (Audio Moving Image) Preservation Labs</a> which uses FFV1 version 3 in <fddLink id="fdd000342">Matroska</fddLink> for both <a href="https://nypl.github.io/ami-preservation/pages/ami-specifications.html">digitized motion picture film and video</a>. and Indiana University Media Digitization and Preservation Initiative (MDPI) and the influential white paper published in March 2017 <a href="https://mdpi.iu.edu/doc/MDPIwhitepaper.pdf">Encoding and Wrapper Decisions and Implementation for Video Preservation Master Files</a>. Author Mike Casey summarized some of the advantages of FFV1 including "roughly 65% less data than a comparable file using the v210 codec" because "FFV1 uses variable bit rate encoding so the size of the resulting file varies according to the nature of the program content." At scale, this can result in a huge savings in storage cost and processing time. A selection of additional FFV1 users include the <a href="https://www.dpconline.org/docs/miscellaneous/events/2019-events/1984-dpc-moving-image-bfi-mcnatch/file">British Film Institute</a>, the <a href="https://siarchives.si.edu/what-we-do/digital-curation/digitizing-collections">Smithsonian Institution Archives</a>, <a href="https://blogs.library.duke.edu/bitstreams/2021/03/12/ffv1-the-gains-of-lossless/">Duke University Libraries</a>, and <a href="https://sulair.stanford.edu/research/digitization-services/labs/stanford-media-preservation-lab/capture-specs">Stanford Libraries</a> among many others. </p>
<p>In 2020, the Library of Congress added Matroska and FFV1 as an "acceptable" format for <a href="https://www.loc.gov/preservation/resources/rfs/moving.html">file-based video</a> content without closed captions and/or timecode information.</p>
<p>The <a href="https://www.iasa-web.org/tc06/guidelines-preservation-video-recordings">IASA-TC 06 Guidelines for the Preservation of Video Recordings</a> recommends Matroska and FFV1 for a number of different "classes" of video content including digitized analogue video recordings (class 1), digital videotapes with encodings that are “out of reach” or inappropriate for long-term retention (class 2), and digital videotapes with encodings that can be extracted “as data" (class 3). FFV1 in Matroska is also used as a preservation format for digitized motion picture film as an alternative to <fddLink id="fdd000178">Digital Moving-Picture Exchange (DPX)</fddLink>. Reto Kromer and Kieran O’Leary led this work with a presentation at NTTW in 2016 (see <a href="https://www.youtube.com/watch?v=q54_FirxdX8">video</a> of presentation) with Kromer later following up in his 2017 paper <a href="https://retokromer.ch/publications/JFP_96.html">Matroska and FFV1: One File Format for Film and Video Archiving?</a>: "The Matroska container and the FFV1 video codec are good choices for single-image-based content when making archive masters. Often, a resolution of 2K, or sometimes 4K, an RGB colour space, the 4:4:4 chroma sampling and a bit-depth of 16 bit per colour channel are canonical choices. For stream-based content, the Matroska container and the FFV1 video codec are also good choices for the archive master. A resolution of HD (with pillar-boxing of letter-boxing if required), in general, the Y′CBCR colour space, the 4:2:2 subsampling and a bit-depth of 10 bit are usually considered best practice." See <a href="https://reto.ch/training/2016/20160819/Reto_Kromer.pdf">slides</a> from O'Leary and Kromer's talk on "Using Matroska and FFV1 for DPX Preservation" from The Reel Thing XXXVIII in Hollywood, California, 18–20 August 2016. This is echoed by Caroline Gil and Peter Oleksik in their talk <a href="https://mediaarea.net/Events/2018-10-26_NoTimeToWait3/presentations/25.%20Caroline%20Gil,%20Peter%20Oleksik%20-%20Assessing%20the%20preservation%20of%20DPX%20image%20sequences%20with%20MoMA/102618_MoMA_NTTW.pdf">Assessing the preservation of DPX image sequences with MoMA</a>. Many NTTW presentations advocate for the use of FFV1 in Matroska with some notable ones including O'Leary's <a href="https://mediaarea.net/Events/2019-12-05_NoTimeToWait4/04.%20Kieran%20O'Leary%20-%20Is%20ProRes-MOV%20to%20FFV1-MKV%20a%20good%20idea/kieran_Prores%20and%20mov%20and%20such.pdf">Migrating ProRes/MOV to FFV1/MKV</a> from 2019, Peter Bubestinger-Steindl's <a href="https://mediaarea.net/Events/2019-12-05_NoTimeToWait4/03.%20Peter%20B.%20-%20Presets%20for%20FFV1%20and%20MKV,%20Choosing%20the%20right%20parameters%20for%20the%20job/ffv1_params.html">Presets for FFV1 and MKV: Choosing the right parameters for the job</a> (2019), Genevieve Havemeyer-King and Ben Turkus from NYPL <a href="https://www.youtube.com/watch?v=n1XYEVtxzU8">MKV and Mass Digitization: What We've Learned Since Giving Uncompressed Video the Boot</a> (video from 2017; presentation starts at about 5:17:00).</p>
<p>Media players that support FFV1 include <a href="https://www.videolan.org/">VLC</a> (VideoLAN client) and for encoders, the open source <a href="https://trac.ffmpeg.org/wiki/Encode/FFV1">FFmpeg</a> is the primary resource. <a href="https://mediaarea.net/MediaConch/Documentation/HowToUse">MediaConch</a> is an implementation checker, policy checker, reporter, and fixer for FFV1 (as well as <fddLink id="fdd000342">Matroska</fddLink> and <fddLink id="fdd000011">LPCM</fddLink>. </p>
</fdd:adoption>
<fdd:licensingAndPatents>
<p>RFC 9043 is covered by IETF copyright statements as defined in BCP 78 and the <a href="https://trustee.ietf.org/license-info">IETF Trust's Legal Provisions Relating to IETF Documents</a>. Draft versions of the specification in <a href="https://github.com/FFmpeg/FFV1">GitHub</a> carry a <a href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International (CC by 4.0)</a> license. The legacy 2003-2012 versions of the <a href="http://www.ffmpeg.org/~michael/ffv1.html">specification</a> at the FFmpeg site carried a copyright attribution to Michael Niedermayer and a declaration that "this text can be used under the GNU Free Documentation License or GNU General Public License."</p>
</fdd:licensingAndPatents>
<fdd:transparency>Depends upon algorithms and tools to read; will require sophistication to build tools.
</fdd:transparency>
<fdd:selfDocumentation>Section 4 of the specification indicates that the types of technical metadata required to read and play the file are provided in frame headers. Additional metadata, if any, would be carried by the wrapper format. <a href="http://www.digitalpreservation.gov/formats/contact_format.shtml">Comments welcome</a>
</fdd:selfDocumentation>
<fdd:externalDependencies>None</fdd:externalDependencies>
<fdd:techProtection>Not provided by the bitstream encoding. Technical protections, if any, would be provided by the wrapper format.</fdd:techProtection>
</fdd:sustainabilityFactors>
<fdd:qualityAndFunctionalityFactors>
<fdd:movingImageQF>
<fdd:normalVideo>Supported</fdd:normalVideo>
<fdd:clarity>Lossless compression that retains all of the video picture information presented to the encoder. <a href="http://www.digitalpreservation.gov/formats/contact_format.shtml">Comments Welcome</a>
</fdd:clarity>
</fdd:movingImageQF>
</fdd:qualityAndFunctionalityFactors>
<fdd:fileTypeSignifiers>
<fdd:signifiersGroup>
<fdd:internetMediaType>
<fdd:sigValues>
<fdd:sigValue>video/FFV1</fdd:sigValue>
</fdd:sigValues>
<fdd:note>As defined in RFC 9043 and <a href="https://www.iana.org/assignments/media-types/media-types.xhtml">IANA Media Type</a> list
</fdd:note>
</fdd:internetMediaType>
<fdd:other>
<fdd:tag>Microsoft FOURCC</fdd:tag>
<fdd:values>
<fdd:sigValues>
<fdd:sigValue>FFV1</fdd:sigValue>
</fdd:sigValues>
</fdd:values>
</fdd:other>
<fdd:other>
<fdd:tag>Pronom PUID</fdd:tag>
<fdd:values>
<fdd:sigValueNA>See note.</fdd:sigValueNA>
<fdd:note>PRONOM has no corresponding entry as of November 2021.</fdd:note>
</fdd:values>
</fdd:other>
<fdd:other>
<fdd:tag>Wikidata Title ID</fdd:tag>
<fdd:values>
<fdd:sigValues>
<fdd:sigValue>Q579857</fdd:sigValue>
</fdd:sigValues>
<fdd:note>See <a href="https://www.wikidata.org/wiki/Q579857">https://www.wikidata.org/wiki/Q579857</a>. Note that Wikidata does not specify versions.</fdd:note>
</fdd:values>
</fdd:other>
</fdd:signifiersGroup>
</fdd:fileTypeSignifiers>
<fdd:notes>
<fdd:history>
<p>The Wikipedia <a href="https://en.wikipedia.org/wiki/FFmpeg">FFmpeg</a> article, consulted May 7, 2012, reports that the FFmpeg project "was started by Fabrice Bellard (using the pseudonym "Gerard Lantau") and has been maintained by Michael Niedermayer since 2004. . . . The name of the project comes from the MPEG video standards group, together with 'FF' for 'fast forward.'" Niedermayer's <a href="http://www.ffmpeg.org/~michael/ffv1.html">Web page</a> states that an FFV1 encoder and decoder have been part of the FFmpeg library since 2003. Incidentally, the section of the specification devoted to frame header metadata includes the tag "version" with possible values of "0" or "1."</p>
<p>The "V" in FFV1 stands for "Video Codec," not "version." According to RFC 9043, the version release timeline is as follows:</p>
<ul>
<li>"Version 0 of FFV1 was the original implementation of FFV1 and was flagged as stable on April 14, 2006 [FFV1_V0].</li>
<li>Version 1 of FFV1 adds support of more video bit depths and was flagged as stable on April 24, 2009 [FFV1_V1].</li>
<li>Version 2 of FFV1 only existed in experimental form and is not described by this document, but it is available as a LyX file at <a href="https://github.com/FFmpeg/FFV1/blob/8ad772b6d61c3dd8b0171979a2cd9f11924d5532/ffv1.lyx">https://github.com/FFmpeg/FFV1/blob/8ad772b6d61c3dd8b0171979a2cd9f11924d5532/ffv1.lyx</a>.</li>
<li>Version 3 of FFV1 adds several features such as increased description of the characteristics of the encoding images and embedded Cyclic Redundancy Check (CRC) data to support fixity verification of the encoding. Version 3 was flagged as stable on August 17, 2013 [FFV1_V3]."</li>
</ul>
</fdd:history>
</fdd:notes>
<fdd:formatSpecifications>
<fdd:urls>
<fdd:url>
<fdd:urlReference>
<link>https://www.ietf.org/rfc/rfc9043.txt</link>
<tag>IETF RFC 9043: FFV1 Video Coding Format Versions 0, 1, and 3</tag>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>https://github.com/FFmpeg/FFV1</link>
<tag>FFV1 specification GitHub</tag>
<comment>Markdown version of the FFV1 specification used to generate IETF versions</comment>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>http://www1.mplayerhq.hu/~michael/ffv1.html</link>
<tag>Legacy FFV1 Video Codec Specification </tag>
<comment>This is superceeded by RFC 9043</comment>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>https://datatracker.ietf.org/doc/charter-ietf-cellar/</link>
<tag>IETF Charter for CELLAR Project (Codec Encoding for LossLess Archiving and Realtime transmission)</tag>
<comment>IETF Working Group page, including specifications for FFV1, Matroska, FLAC and EBML</comment>
</fdd:urlReference>
</fdd:url>
</fdd:urls>
</fdd:formatSpecifications>
<fdd:usefulReferences>
<fdd:urls>
<fdd:url>
<fdd:urlGroup>
<fdd:intro>No Time to Wait Conferences</fdd:intro>
<fdd:urlList>
<fdd:urlReference>
<link>https://mediaarea.net/NoTimeToWait</link>
<tag>No Time to Wait 1, Berlin, July 18-20 2016</tag>
</fdd:urlReference>
<fdd:urlReference>
<link>https://docs.google.com/document/d/1dkT5cpUWFWXKHXC1132d1ndmwrnVPV7nBeyHAehM5HQ/edit?usp=sharing</link>
<tag>Google doc with notes from Matroska working group from No Time to Wait in Berlin 2016.</tag>
</fdd:urlReference>
<fdd:urlReference>
<link>https://mediaarea.net/NoTimeToWait2</link>
<tag>No Time to Wait 2, Vienna, November 9-10 2017</tag>
</fdd:urlReference>
<fdd:urlReference>
<link>https://mediaarea.net/NoTimeToWait3</link>
<tag>No Time to Wait 3, London, October 25-26 2018</tag>
</fdd:urlReference>
<fdd:urlReference>
<link>https://mediaarea.net/NoTimeToWait4</link>
<tag>No Time to Wait 4, Budapest, December 5-6 2019</tag>
</fdd:urlReference>
</fdd:urlList>
</fdd:urlGroup>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>https://mdpi.iu.edu/doc/MDPIwhitepaper.pdf</link>
<tag>Encoding and Wrapper Decisions and Implementation for Video Preservation Master Files</tag>
<comment>Indiana University Media Digitization and Preservation Initiative (MDPI), authored by Mike Casey in March 2017</comment>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>https://github.com/NYPL/ami-specifications</link>
<tag>New York Public Library (NYPL) AMI Digital Asset Technical Specifications on GitHub</tag>
<comment>Technical file format specification including use of Matroska and FFV1</comment>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>https://www.iasa-web.org/tc06/guidelines-preservation-video-recordings</link>
<tag>IASA-TC 06 Guidelines for the Preservation of Video Recordings, 2018</tag>
<comment>Recommends Matroska and FFV1</comment>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>https://retokromer.ch/publications/JFP_96.html</link>
<tag>Matroska and FFV1: One File Format for Film and Video Archiving? By Reto Kromer</tag>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>https://reto.ch/training/2016/20160819/Reto_Kromer.pdf</link>
<tag>Slides from Kieran O'Leary and Reto Kromer's talk on "Using Matroska and FFV1 for DPX Preservation" from The Reel Thing XXXVIII in Hollywood, California, 18–20 August 2016.</tag>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>https://mediaarea.net/Events/2018-10-26_NoTimeToWait3/presentations/25.%20Caroline%20Gil,%20Peter%20Oleksik%20-%20Assessing%20the%20preservation%20of%20DPX%20image%20sequences%20with%20MoMA/102618_MoMA_NTTW.pdf</link>
<tag>Caroline Gil and Peter Oleksik's talk Assessing the preservation of DPX image sequences with MoMA. NTTW3</tag>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>https://mediaarea.net/Events/2019-12-05_NoTimeToWait4/04.%20Kieran%20O'Leary%20-%20Is%20ProRes-MOV%20to%20FFV1-MKV%20a%20good%20idea/kieran_Prores%20and%20mov%20and%20such.pdf</link>
<tag>Kieran O'Leary: Migrating ProRes/MOV to FFV1/MKV. NTTW4</tag>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>https://mediaarea.net/Events/2019-12-05_NoTimeToWait4/03.%20Peter%20B.%20-%20Presets%20for%20FFV1%20and%20MKV,%20Choosing%20the%20right%20parameters%20for%20the%20job/ffv1_params.html</link>
<tag>Peter Bubestinger-Steindl: Presets for FFV1 and MKV: Choosing the right parameters for the job. NTTW4</tag>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>https://www.youtube.com/watch?v=n1XYEVtxzU8</link>
<tag>Genevieve Havemeyer-King and Ben Turkus from NYPL: MKV and Mass Digitization: What We've Learned Since Giving Uncompressed Video the Boot. (video from 2017; presentation starts at about 5:17:00).</tag>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>https://www.si.edu/sites/default/files/unit/OCIO/si_dams_supported_file_formats_2019.pdf</link>
<tag>Smithsonian Institutions DAMS Supported File Formats</tag>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>https://siarchives.si.edu/what-we-do/digital-curation/digitizing-collections</link>
<tag>Smithsonian Institution Archives: Digitizing Collections</tag>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>https://blogs.library.duke.edu/bitstreams/2021/03/12/ffv1-the-gains-of-lossless/</link>
<tag>FFV1: The Gains of Lossless by Alex Marsh, Duke University Libraries blog. March 12, 2021</tag>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>https://sulair.stanford.edu/research/digitization-services/labs/stanford-media-preservation-lab/capture-specs</link>
<tag>Stanford Libraries Capture Specs</tag>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>https://www.fiafnet.org/images/tinyUpload/E-Resources/Commission-And-PIP-Resources/TC_resources/FFV1_and_Matroska_reading_list.pdf</link>
<tag>FFV1 and Matroska reading list </tag>
<comment>Collated for FIAF by Stephen McConnachie, Head of Data, BFI, March 2018</comment>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>http://www.vancouverarchives.ca/2011/10/06/a-day-in-the-lives-of-2-archivists-gone-digital/</link>
<tag>A City of Vancouver Archives' blog post mentioning their use of FFV1</tag>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>http://wiki.multimedia.cx/index.php?title=FFV1</link>
<tag>MultimediaWiki entry for FFV1 </tag>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>http://ffmpeg.org/</link>
<tag>FFmpeg project website </tag>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>http://dericed.com/papers/reconsidering-the-checksum-for-audiovisual-preservation/</link>
<tag>Reconsidering the Checksum for Audiovisual Preservation</tag>
<comment>Online article by Dave Rice, CUNY.</comment>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>http://www.cnet.com/news/five-biggest-changes-to-windows-10-media-playback/</link>
<tag>The Five Biggest Changes to Media Playback in Windows 10</tag>
<comment>Online article from cnet describing Windows 10 capabilities for video and other rich media</comment>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>http://www.preforma-project.eu/index.html</link>
<tag>PREFORMA, PREservation FORMAts for culture information/e-archives</tag>
<comment>Collaborative EU-funded project with goal of "implementing good quality standardised file formats" including Matroska, FLAC and FFV1</comment>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>https://mediaarea.net/MediaConch/</link>
<tag>MediaConch: Open source implementation checker, policy checker, and reporter for Matroska, FFV1, & PCM</tag>
<comment>Part of PREFORMA project</comment>
</fdd:urlReference>
</fdd:url>
<fdd:url>
<fdd:urlReference>
<link>https://www.wikidata.org/wiki/Q579857</link>
<tag>Wikidata entry for Q579857</tag>
<comment>Information in Wikidata about FFV1. Wikidata Title ID: Q579857.</comment>
</fdd:urlReference>
</fdd:url>
</fdd:urls>
</fdd:usefulReferences>
</fdd:FDD>