...
From 5.10.8, the migration from the old transcode system to the new transcode system must be performed manually.The automatic migration in
Environments that have been on 5.10.0-5.10.7
...
The automatic migration that was run on 5.10.0-5.10.7 versions (both inclusive) did not migrate profiles. Instead, please ensure that the following script is run to achieve exactly the same result as the manual migrationprofile-like setups had to be configured with the Generate asset renditions automation step.
If you upgrade a site to 5.10.8 (or newer) and start using the “No-security channel folders” parameter on formats to control publicly available renditions, please be aware that existing publicly available renditions will always remain publicly available, unless the automation step Generate asset renditions is still used to make the renditions private again.
We recommend using the “No-security channel folders” parameter on formats to control which renditions that are publicly available. If you decide to do this and you have previously used the automation approach, please run the following script to ensure that renditions can be made private again based on the “No-security channel folders” parameter of the configured formats: https://github.com/Digizuite/scripts/blob/main/enforce_channel_based_ignore_security.sql. If the script above is not run, then renditions that were already publicly available when migrating can only be made private with the Generate asset renditions automation step and not via the “No-Security channel folders” option on formats.
Migration script
To manually migrate from the old transcode system to the new transcode system, the following SQL script can be used: https://github.com/Digizuite/scripts/blob/main/transcode_system_migration.sql.
...