...
In previous version of the old transcode system, it was possible to embed EXIF metadata in the generated renditions/transcodes. This is not supported in the new transcode system.
API and SDK users
It has been ensured that the automatic switch to the new transcode system is seamless in all applications and integrations developed by Digizuite. However, the new transcode system has a few caveats to be aware of for anyone that uses the Digizuite API or SDK:
Handling of renditions that are not available yet.
Search2
New thumbnail formats.
Search2
Search2 allows the tables media_transcode_proxy_destination and media_transcode_proxy to be referenced in both input and output, providing access to information about transcodes/renditions. Information about renditions generated with the new transcode system can not be accessed through these tables. If one of these tables is used in a search, it is recommended to start using the API or the SDK to retrieve information about transcodes instead. This can be done using the endpoint <api-url>/DigizuiteCore/LegacyService/api/assets/search or IAssetSearchService in the SDK.
...
If the caveats above are addressed, Search2 can still be used to retrieve valid URLs for old media formats that have been mapped to new formats, ensuring that the new transcode system is used. However, we it is generally recommend starting recommended to rewrite start rewriting applications that use Search2 to use the new API or SDK instead. If this is not possible, it is still possible to opt-out of using the new transcode system by ensuring that no old media formats are mapped to new formats.
On-demand transcoding
A key difference between the old transcode system and the new transcode system is that renditions can now be generated on-demand. In particular, this means that
New thumbnail formats
With the 5.10 release, the thumbnail and preview formats that are defined out of the box have been reworked. By default, this is handled automatically and no manual actions should be required.
The main difference between the old and the new thumbnail formats is that they are now webp files with transparency. The old thumbnails were jpeg files without transparency.
As described above, the thumbnails for existing assets are not automatically re-generated. If the existing thumbnails should be re-generated, this can be done by setting up an automation that uses the “Generate asset renditions” step with the “Force generate” flag enabled.
Since the file type of the thumbnails has been changed, the asset streamer returns the response header Content-Type: image/webp instead of the correct response header Content-Type: image/jpeg for existing thumbnails. Most browsers should be able to display the thumbnails despite of this. If it becomes an issue, the existing thumbnails can either be re-generated as described above, or the thumbnail format can be modified to be jpeg.