Adobe Responds to Apple Discontinuing Support For Older Media Codecs

Recently, Apple announced that it would be discontinuing support for “legacy media” using 32-bit codecs in the next major release of the macOS after Mojave. These codecs were built, for the most part, on QuickTime 7, which is also 32-bit.

Prominent on Apple’s list were Cineform, Flash Video, and Motion JPEG A & B,  which are used regularly in Adobe Premiere Pro projects. Because the concept of “old media not working” can scare any editor, I emailed Adobe a series of questions to learn the impact of Apple’s decision on Adobe software.

Bill Roberts, Senior Director of Product Management for Audio and Video Products at Adobe Systems, responded with more detailed answers. Here’s our conversation.

Larry asks: My first question speaks to the fear of “nothing working” in Premiere. My understanding is that Adobe relies on codecs supplied by the macOS. Therefore, if some codecs – such as the list Apple provided – are no longer supported by the macOS, Premiere and other Adobe applications will no longer be able to play existing media. Is this understanding correct?

Adobe: The majority of the codecs we ship for common / high-use formats are our own Adobe written codecs. It is for this reason that any changes made to the macOS recently have not impacted Adobe users, nor will any of our supported codecs be impacted by OS-level changes.

Larry asks: As a follow-on question, when does Adobe rely on Apple’s codecs and when does Adobe create their own?

Adobe: It is our objective to provide as much performance as possible to our users. In some cases relying on vendor-specific functionality is the only way to take advantage of hardware acceleration (such as built-in hardware for decode / encode of specific formats). It’s these cases where the benefits are so substantial that we’ll make exceptions.

Larry asks: For editors that, for whatever reason, don’t want to transcode their media to ProRes, which codecs does Adobe recommend for those that want to future-proof their media – and would you recommend the same codecs for Windows?

Adobe: We look for Intermediate Codecs to provide a range of functions, including high quality imagery, efficient file sizes and great documentation. Also, due to the mixed nature of post-production we recommend codecs that are available on all popular operating systems — for these reasons ProRes, DNx and Cineform all make good intermediate formats. With our recently released support for writing of ProRes files on Windows, ProRes becomes an even more applicable intermediate.

Larry asks: Because technology marches on, should Windows users consider transcoding their media?

Adobe: We always recommend native workflows and we will continue to support as wide a range as possible to provide the highest quality and most efficient workflows.

The entire computing industry is going through the final phase of moving from 32bit computing to 64bit computing. This impacts the media and entertainment industry because some of the older formats do not have 64bit decode paths. If you have any old 32bit only codecs, it’s good advice to migrate these to an intermediate that will have a long life.

Larry asks: For those editors that live in the Adobe universe, is Adobe planning to provide a utility that can search for outdated media and convert it into a more future-proof format?

Adobe: Generally, this will not be needed as we’re in a good position with the formats we support. As previously stated, this is a point in time where 32-bit technology is being phased out industry-wide. Adobe moved early on the 64-bit migration path and we do not anticipate big changes in file formats supported going forward.


Bill uses the phrase: “native codec.” This means a codec that was written by Adobe, which does not rely on the 32-bit architecture of QuickTime 7. As Bill discussed above, all native codecs should be fine for future use, it is those built on QuickTime 7 that are in jeopardy.

Part of the confusion over the coming codec change is that QuickTime 7 provides support for Cineform, while Adobe also provides native Cineform support. This leads to confusion where Adobe recommends transcoding to Cineform, while Apple says that Cineform is one of the codecs being discontinued. Sigh… It is currently very difficult for non-engineers to tell if they are using a 32-bit or 64-bit version of a codec. Hopefully, this confusion will get cleared up over time.

As mentioned in my original article, we don’t need to do anything, yet, except to be aware that this change is coming. However, it wouldn’t hurt to look over past projects and start to catalog what codecs they used. We will learn more from both Adobe and Apple as the transition gets closer.

Bookmark the permalink.

4 Responses to Adobe Responds to Apple Discontinuing Support For Older Media Codecs

  1. Marlin Sharp says:

    I have many, many archived completed movie files that are in Quicktime 7.+. 32 bit. Will i need to convert all of those so not to loose them playing or functioning? Also will Quicktime Player 7 no longer function for quick editing? As of now I can shorten clips and save them in QT.

    • Larry says:


      You are correct:

      1. QuickTime Player 7 will not work in any version of the macOS AFTER Mojave (10.14.x).
      2. Any media or finished movies that use one of the 32-bit codecs on Apple’s list will not play in any version of the macOS AFTER Mojave.

      The good news is that we are months away from any new version of the operating system. (In the past, Apple tends to release these in September, but I don’t know their plans.)

      Second, Apple, and other vendors, have announced plans for new products that will help us convert older media into a current format.

      For now, spend time tracking down the footage you need to convert, but don’t start the actual conversion until we know more about which tools are available and what formats are recommended.


  2. […] Meanwhile, as Apple clarifies the ‘legacy media warning; with an update to their Knowledge Base article, Scott Simmons notes that Apple’s move “mentions a future version of Final Cut Pro X as FCPX editors are the ones most likely affected by these changes.” Scott says say to read the Digital Rebellion article, Thoughts on 32-bit codecs being phased out in macOS. He adds, “We won’t get the support for some of these legacy codecs in the base level of the operating system. I honestly think it won’t make that big of a deal as most of the software that editors will be working in will be able to support the various post-production codecs that we need.” Larry Jordan also offered reassurance in Adobe Responds to Apple Discontinuing Support For Older Media Codecs. […]

Leave a Reply

Your email address will not be published. Required fields are marked *

Larry Recommends:

FCPX Complete

NEW & Updated!

Edit smarter with Larry’s latest training, all available in our store.

Access over 1,900 on-demand video editing courses. Become a member of our Video Training Library today!


Subscribe to Larry's FREE weekly newsletter and save 10%
on your first purchase.