...
All changes to the old media format are ignored.
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.
If a format was made available both through “Profiles and destinations” and “Asset type configuration”, then “Asset type configuration” will take precidence over “Profiles and destinations”.
Things to be aware of
Although as many old media formats as possible are migrated to new formats with the SQL migration script, there are a few cases that can require manual actions:
...
In the new transcode system, it is not possible to generate renditions at specific destinations. Instead , 2 alternatives are available:
the automation step “Generate asset renditions” can be used to generate renditions with
IgnoreSecurity
set totrue
. This makes the generated renditions publicly available.Use the “No-Security channel folders” settings on formats. In this case the format is considered publically available the moment the asset is added to one of the specified folders. Do note that this does not cause the rendition to be generated. If the rendition is not generated when it is requested, the standard logic of waiting for the transcoding to be completed still applies. To get around this, specify the channel folder in “Pre-generate channel folders” also.
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.
...