We are pleased to announce the progress we’ve made this year. There are new updates to MediaConch that expand its capabilities, user stories to share, and new events related to implementation checking and the standardization of open audiovisual formats.
The MediaConch team recently collaborated with VIAA on tests to migrate their JPEG2000/MXF collection to FFV1/Matroska. Learn more about our process and findings!
The development of MediaConch has been closely following the work of the IETF CELLAR working group which is creating specifications for EBML, Matroska, FFV1 and FLAC. Review the latest versions of those documents.
- MediaConch optimized its FFV1 parser, which will allow upcoming versions to provide more comprehensive implementation checking of FFV1 against its specification.
- We improved the Matroska checker, particularly to support the CELLAR working group's development of the EBML Schema, which defines Matroska’s structure in a manner similar to an XML Schema.
- Attachments to Matroska files may now be analyzed against other implementation checkers. For instance, Matroska can now use VeraPDF or DPF Manager to assess TIFF or PDF data.
- In collaboration with the Tate Museum, we have added a TN2162 policy checker to MediaConch. This policy assesses uncompressed video in QuickTime against Apple’s list of additional requirements that affect that combination of formats.
- Several bugs were reported and fixed. Thanks to our users for their reports!
- See what’s new in MediaConch's GUI ad CLI!
Jérôme, Reto, and Kieran recently presented MediaConch and CELLAR standardization at the Reel Thing Conference in Amsterdam.
The presentations and conversations at the Reel Thing demonstrated a growing interest in the standardization process of Matroska and FFV1 as well as methods to integrate these formats into preservation environments. Conversations focused on use of these formats for film preservation challenges and collaborative work to develop more tools around lossless video.
- “FrameMD5” computing in MediaConch, in order to compare resulting file to a source file, pixel per pixel, after a conversion to Matroska/FFV1, if the conversion includes a “FrameMD5” of the source file.
- Adding more information (specific location of the error in the bitstream) when FFV1 validation fails.
- Stabilization of the software, with bug fixes and more automatic non-regression tests.
Ashley recently interviewed Eddy Colloton from the Denver Art Museum about his process and experience using MediaConch. Read it here!