Skip to content

How to Preserve

Interoperable Master Format (IMF)

The Interoperable Master Format (IMF) has proven invaluable in the exchange and processing of multiple content versions of finished works for a variety of global distribution channels, ranging from airline edits of films and television series to special editions and multiple language versions.

It is possible, however, that the IMF and components of the Society of Motion Picture and Television Engineers' (SMPTE) standards may also be able to address archival and preservation concerns. For instance, it could be used at the edge of an archive system to exchange content. Or it could be used in the long term preservation as a data storage format, splitting the component parts of an audio-visual master and maintaining them as a digital inventory.

What does the forum think of the possibilities, and how the framework's core features could be wrangled for this broader usage?

The IMF is first and foremost a framework, that provides a mechanism to:

  •  Reference high-quality file-based masters
  •  Maintain components wrapped as track files
  •  Essence (image and audio)
  •  Data essence (subtitles and captioning)
  • Have a non-destructive means of combining track files via an edit-decision list through the Composition Play List (CPL), enabling rendition versioning
  • Have a means of specifying output renders (using static and dynamic metadata through the Output Profile List)
  • Enable packaging
  • Provide security

The Interoperable Master Format enables assembly of the components into a nicely wrapped package for delivery, the IMP (Interoperable Master Package). However, this framework does not require packaging, and it can be used to keep assets in situ.

Although the IMF was created to handle version explosions in theatrical workflows, it is not only used for them. Numerous broadcast facilities are currently considering adopting the format. The diagram below provides a conceptual flow of assets along the digital supply chain.

digital supply chain assets flow

The immediate focus of it was distribution servicing. To accomplish this, motion picture studios gathered at the University of Southern California's Entertainment Technology Center to develop requirements specifications. The Society of Motion Picture and Television Engineers (SMPTE) was then given this specification in order to formulate a set of standards that would allow manufacturers to create products to support this initiative.

An overview can be found at IMF Explainer.

A guide to the SMPTE suite of IMF standards is available at SMPTE OV 2067-0:2017. The “Core Constraints” standard, which specifies provisions common to all IMF “Applications,” is available at ST 2067-2:2020 - SMPTE Standard - Interoperable Master Format — Core Constraints.

The IMF can easily be expanded with new varieties of standard or user-specific audio-visual essence and metadata. In fact, SMPTE continuously updates the Interoperable Master Format family of standards to match emerging use cases and fix bugs. Therefore, one consideration for the Academy Digital Preservation Forum is how the format can be extended to support archival and preservation needs.

The Forum solicits discussion around this area and would be interested in hearing from you on how capabilities of IMF can be extended for archiving and preservation. For some thoughts on this, see Why IMF for archival applications?.

Keep in mind the core features of the framework, namely:

  1. Ability to reference original high-quality masters
  2. Provide non-destructive means of combining masters, with an edit-decision list
  3. Provide non-destructive means of modifying (that is, rendering) the content through processing instructions, to generate any deliverable, such as:
    1. a VFX render – based on render instructions that are codified within the OPL
    2. a color-correction render – based on CC lists or an ACES Metadata File
    3. a pan-and-scan deliverable – based on ongoing work by the ASC Framing Decision List

Join the Discussion

Each post in the Academy Digital Preservation Forum has a companion topic in our community. Click 'Continue the discussion' to go to our community and give your response to this post.

  • Avatar for jun_jazz

    Questions I would be eager to know answers to are whether
    a) A componentized framework is consistent with the notion of Archiving Image and Audio ?
    b) Since we can store uncompressed assets within IMF - what are the additional archivist’s needs ?

  • Avatar for annie.chang

    I am also interested in the answers to Arjun’s questions. IMF was created originally for one purpose (distribution mastering and dealing with the infinite versions of a master), but that doesn’t mean that it can’t be extended for other uses such as archiving. Typically, we’ve archived image separate from audio, but that can cause issues when you are trying to bring that all back online in an approved manner. An IMF version of the original source material could be useful, but the downside is that there is some post processing needed to assemble everything unless there is a way to re-use CPLs from either downstream DCPs or IMFs.

  • Avatar for craig.seidel

    I believe the Media Manifest Core (MMC), part of the MovieLabs Digital Distribution Framework (MDDF) is the missing link (or at least contains the missing links).

    IMF is a great solutions for managing compositions and their component tracks. But, unless everything is managed as part of the IMF there is no glue to put independent pieces together. For example, what there’s an IMF for an OV, and the conformed localized tracks (subs and dubs) just happen to be somewhere else. You could theoretically put them all in an IMP, but those other tracks might be in non-IMF-friendly codecs, or possibly not even directly accessible (e.g., access rights, physical location, etc.).

    MMC was designed to be independent and neutral to track location and encoding. Basically, you can associate data (media, metadata/artwork, interactive material, etc.) without restrictions on the state of the assets. It can even be done with IDs adding a whole other layer of transparency.

    As far as I know, MMC has never been considered for preservation, but IMHO it should.

    P.S., I another post I mentioned the linking system in the MovieLabs 2030 Vision. I believe that will ultimately incorporate the relationships in MMC, thereby obsoleting MMC.