...
This page describes the most important things to be aware of in relation to the new transcode system.
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
EXIF
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.
...
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 unavailable renditions.
Search2.
New thumbnail formats.
...
By default, when requesting a rendition of an asset with the asset streamer (prefixed with <api-url>/DigizuiteCore/LegacyService/api/assetstream), the request will not terminate before the rendition is available. This process can take a while. If you do not want to wait for renditions to become available, the query parameter mode=getFallbackImageIfUnavailable can be added to the asset streamer request when using the API. With this query parameter set, a fallback image will be returned with the HTTP status code 202 if the requested rendition is not immediately available.
...
Note that this removes the default timeout of 100 seconds from ALL all HTTP request performed with the SDK. However, it is still possible to control the timeout per-request by passing a cancellation token to the used SDK method. The effective timeout is always the smallest of the passed cancellation token and the timeout configured for the HTTP client used by the SDK.
...