foigus' Notes

Mostly OS X Admin Related

Blinded me with Silence: Adobe and the End of the Dolby License

Recently Adobe ended a licensing agreement with Dolby, “moving to native Operating System (OS) support for Dolby Digital decoding (reading Dolby files) and…no longer provid[es] support for encoding (writing) Dolby Digital and Dolby Digital Plus sound formats in the current and future releases of Creative Cloud.”  Adobe will now rely on native OS decoding of Dolby media for playback (supported by OS X 10.11+ or Windows 8.1+) and the ability to create Dolby media will be removed. As a result some versions of some Creative Cloud software titles are no longer available, and as of November 3, 2017 the following professional titles are affected:

  • After Effects CC 2015.3 and 2017
  • Audition CC 2014, 2015, 2015.2, and 2017
  • Media Encoder CC 2014, 2015, 2015.3, and 2017
  • Prelude CC 2014, 2015, 2015.4, and 2017
  • Premiere Pro CC 2014, 2015, 2015.3, and 2017

These titles are no longer available for Enterprise packaging via the Creative Cloud Packager or the Admin Console Cloud Packager. The CC 2017 versions of the applications do seem to be available via the Creative Cloud Desktop App (CCDA), however these CC 2017 titles appear to have been revised to no longer include Dolby software.

This change may create issues for customers–if a package for an appropriate version of a particular title has not been previously built (i.e. from either the Creative Cloud Packager or the Admin Console Cloud Packager), it may not be possible to install that software. This complicates both new installations (such as installing the software on additional computers) and reinstallation (such as during troubleshooting or computer rebuild situations). Beyond this, if the CCDA is used to install newer versions of software, the default setting is to remove previous versions of that software title. It is reasonable that a later version of a piece of software would be installed for testing, however if issues were discovered it would be impossible to reinstall the earlier version and be able to access the full features of that previous version.

Regarding software installation, if it’s not possible to build the software installation packages required by your organization the only option is to reach out to Adobe support and request assistance.

Also note that if it’s not possible to build an installation package for a title, it’s also not possible to build an uninstallation package for that title. There are a few options for uninstallation:

  • Software can be uninstalled by hand using the GUI uninstaller–although it doesn’t scale well, it is an option
  • If the original uninstallation package (created when the installation package was created) is available, this would also work to uninstall the software
  • If the title to be uninstalled uses a new-style “HyperDrive” package (“HyperDrive” package titles listed here) it is possible to uninstall the software via the command line
  • The CC Cleaner Tool may be used to generate an XML file to uninstall software using the CC Cleaner Tool binary. Note the CC Cleaner Tool is a command-line binary plus a configuration file that needs to be generated on a computer that has the software installed that is wished to be removed. The CC Cleaner Tool is not a traditional macOS installation package and will require being integrated into a package to be used with most management systems. Also note it appears it is not possible to silently uninstall “all” products and suppress the CC Cleaner Tool EULA–all products that are desired to be uninstalled will need to be noted in “cleanup.xml” in order to bypass the EULA
  • It may be possible to build a CCP “Uninstall ‘Package'” and modify the “AdobeCCUninstallerConfig.xml” configuration file to add additional products to uninstall. Note a CCP “Uninstall ‘Package'” is a command-line binary plus a generated configuration file–it is not a traditional macOS installation package and will require being integrated into a package to be used. Also note software installed using the older Adobe “RIBS”-based packages require “SapCode”, “Version”, “Leid”, “Platform”, “mediaSignature”, and “adobeCode” information in order to be successfully uninstalled. Obtaining this information will likely will require the assistance of Adobe support, and modifying a CCP “Uninstall ‘Package'” should be evaluated after trying the above CC Cleaner Tool option
  • It also may be possible to contact Adobe support and ask to be provided the proper uninstall package

These installation changes due to shifting licensing are unfortunate, since it shifts a potentially significant burden onto the IT administrator. Hopefully in the future Adobe’s licensing folks will work with the Enterprise IT folks in order to have a smoother transition with additional documentation.

Advertisements

One response to “Blinded me with Silence: Adobe and the End of the Dolby License

  1. Pingback: Episode 58: It’s Raining Shoes – Mac Admins Podcast

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: