The old transcode system will no longer be available in 6.0. Instead, the new transcode system must be used.
The migration to the new transcode system is automatic, but it can require some manual actions if the system is configured to allow users to download renditions of assets in old media formats whose file extension is not supported in the new transcode system. Please see DC 5.10 Formats - Migration for more information on the migration to the new transcode system.
With the deletion of the old transcode system, the following concepts are deleted in 6.0:
Media formats (not to be confused with formats in the new transcode system)
Media format types
Transcodes
Asset type configurations
Profiles
Since the media format concept is deleted with 6.0, it is no longer possible to request a rendition of an asset with the id of an old media format. If the asset streamer URLs returned from the API are used, this should not be an issue and the transition to the new transcode system will happen automatically.
However, if an old media format id has been hardcoded in a link, this link will no longer work in 6.0. It is therefore highly recommended to start locating any potentially hardcoded old media format ids and switch to new format ids in 5.9.
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.