Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Next »

With the 5.10 release, a new transcode system is introduced.

The new transcode system has been written from scratch and is much easier to configure than the old transcode system. The main capabilities of the new transcode system are described here.

When upgrading existing environments to 5.10, the new transcode system is automatically used as much as possible. The old transcode system can still be used in 5.10, but it is deprecated and can not be used in future versions. Thus, it is highly advised to fully use the new transcode system instead of the old transcode system as soon as possible.

This page describes the main things to be aware of in relation to the migration to the new transcode system.

Automatic migration

When upgrading to 5.10, as many old media formats as possible are automatically migrated to new formats. In particular, a new format with the same name as the old format is created, and then the old format is mapped to the new format. This is only done for old media formats that can be mapped to a supported format type in the new transcode system. Please contact R&D if you have a use case for a format type that is not supported in the new transcode system.

An overview of all formats can be seen on the system administration page in the Media Manager. If a format is mapped to an old media format, this can be seen in the “Mapped media formats” parameter when viewing the details of a format.

image-20240229-114542.png

When an old media format is mapped to a new format, please be aware of the following:

  • 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.

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.

Please ensure that these update and delete actions are exported into a custom layer before applying the configuration.

LaxSecurity destinations

In the old transcode system, it was possible to generate renditions and make them available at specific destinations via asset type configurations or profiles. If a destination was configured with LaxSecurity set to true, the renditions stored in this destination would be publicly available.

In the new transcode system, it is not possible to generate renditions at specific destinations. Instead, the automation step “Generate asset renditions” can be used to generate renditions with IgnoreSecurity set to true. This makes the generated renditions publicly available.

Note that existing renditions at LaxSecurity destinations will still be publicly available in 5.10. However, to ensure that the same renditions for new assets, uploaded after updating to 5.10, are made publicly available, please ensure that you create corresponding automations to make these renditions publicly available.

Thus, automations must be created to cover the use case of generating renditions at LaxSecurity destinations. In the old transcode system, this was configured with asset type configurations and profiles.

Revisit 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?

    • This can happen if the new transcode system does not support the type of the media format. If you encounter such a case, 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.

Re-run automatic migration

As mentioned in https://digizuite.atlassian.net/wiki/spaces/DD/pages/3710091372/DC+5.10+Formats+-+Migration#Automatic-migration, as many existing media formats as possible are automatically migrated when updating to 5.10. However, the automatic migration can always be re-run by running the following script against the database: .

This is, e.g., relevant if the automatically migrated formats were accidentally deleted with Configuration Management.

  • No labels