...
With the deletion of the old transcode system in 6.0, 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 system6.0, it was will no longer be possible to generate renditions and make them available at specific make renditions publicly available by publishing them to LaxSecurity destinations via asset type configurations configuration 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 trueInstead, this must be handled with automations.
Please see https://digizuite.atlassian.net/wiki/spaces/DD/pages/3710091372/DC+5.10+Formats+-+Migration#LaxSecurity-destinations for more information.