...

• All changes to the old media format are ignored.

• Renditions are no longer generated based on profiles. Thus, if renditions of the old media format were previously being generated when an asset was published to a specific channel folder, this is no longer the case. Pre-generation can be set up for the new format. However, please carefully consider if this is necessary now that the transcode system supports on-demand transcoding.

• Existing renditions are not re-generated. Thus, the existing renditions will be used when requesting renditions of existing assets in the new format. This is also the case if generating the rendition with the new format definition would lead to a different rendition than the existing rendition. As described in https://digizuite.atlassian.net/wiki/spaces/DD/pages/3708157997/DC+5.10+Breaking+changes+-+Transcode+system#New-thumbnail-formats, it is possible to use the “Generate asset renditions” automation step to force existing renditions to be re-generated.

• For new assets, the new transcode system and the new format are used to generate renditions. This is also the case if a rendition of the old media format is requested.

• Renditions of the format can still be requested with the ID of the old media format. This is mainly relevant for backward compatibility reasons.

Manual migration

Although as many old media formats as possible are migrated to new formats, there are a few cases that can require manual actions:

1. Unsupported media format type: The new transcode system supports a limited set of format types. All old media formats that do not have a corresponding format type in the new transcode system can not be automatically migrated to a new format. If a media format is used and has not been migrated, consider if one of the supported format types in the new transcode system can be used instead. Otherwise, reach out to R&D to share your use case.

   1. All non-migrated media formats can be identified by running the following SQL query against the database after upgrading:

      View file
      name identify_non_migrated_formats.sql

      .

2. Special ImageMagick commands: If an old media format is defined with an ImageMagick command that refers to a local file on the server, renditions of the corresponding migrated format can not be generated with the new transcode system. This can e.g. be the case if a custom profile or a special watermark is used. An example of such an ImageMagick command is: %infile%[0] -profile "D:\my\local\file\path\custom_profile.icc" %outfile%. If a local file is referenced, the corresponding migrated format must be edited manually.

   1. The media formats for which this potentially is an issue can be identified by running the following SQL query against the database after upgrading:

      View file
      name identify_problematic_conversion_commands.sql

      .

Configuration Management

All new formats that have been created as part of the automatic format migration, as described above, will appear as delete actions when diffing in configuration management. Furthermore, all member groups that had one of these old formats configured as a download quality will have an update action, updating the download qualities to the corresponding new formats.

...

Although not strictly necessary, the introduction of the new transcode system provides a good basis for revisiting the formats that are defined for existing customers. Maybe some of the old media formats are no longer needed. Maybe some of the automatically mapped formats can be mapped better manually, for instance, utilizing the support for webp and transparency.

When revisiting the available formats, please keep an eye out for the following:

Are there any used media formats that have not been manually mapped to a new format?

...

.

Re-run automatic migration

...