Page Comparison

...

In the previous version of the old transcode system, it was possible to embed EXIF metadata in the generated renditionsqualities/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 who uses the Digizuite API or SDK.

1. Handling of unavailable renditionsqualities.

2. Search2.

3. New thumbnail formats.

4. Source formats.

Handling of unavailable

...

qualities

Previously, asset streamer URLs would never be returned for renditions qualities that hadn’t been generated yet. However, with the new transcode system, asset streamer URLs are returned for renditions qualities that can be generated but are not necessarily ready yet.

...

By default, when requesting a rendition quality of an asset with the asset streamer, the request will not terminate before the rendition quality is available. This process can take a while. If you do not want to wait for renditions qualities to become available, it is possible to get a fallback image returned with the HTTP status code 202 if the requested rendition quality is not immediately available. This can be done in the following way:

...

Note that most modern browsers limit the maximum number of simultaneous HTTP connections. Thus, if you show a lot of renditions qualities simultaneously (e.g. thumbnails in an asset list), strongly consider using the mode argument to limit the number of simultaneous HTTP connections. Please be careful that you do not cache the fallback image as the requested image.

If you are using the SDK, be aware that the default HTTP client used by the SDK has a timeout of 100 seconds. Thus, if you request a rendition quality that takes more than 100 seconds to become available with the INewAssetStreamerService.GetAssetDownloadStream method, your request will time out before the rendition quality is returned. To disable this timeout, use the following setup in your application startup logic:

...

• 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 renditionsqualities. Information about renditions qualities generated with the new transcode system can not be accessed through these tables.

• Search2 allows URLs for renditions qualities of old media formats to be retrieved with the functions urlAbsolut, urlRelative, downloadUrlAbsolut, and downloadUrlRelative. It has been ensured that this still works, even if the targeted old media format has been mapped to a new format. If an old media format has not been mapped to a new format, these functions work in exactly the same way as previously. However, a few caveats should be mentioned in the case where an old media format is mapped to a new format:

  • A URL is always returned, even though a rendition quality of the asset in the old media format can not be generated. As an example, this means that a thumb URL is included for an asset in the default GetAssets search, even if it can not be generated. Previously, the thumb URL would be null in this case. Thus, it must be ensured that clients do no rely on the URL in a search to be null when it can't be generated.

  • If the urlRelative or downloadUrlRelative function is used, the returned relative URL will be relative to <api-url> instead of <api-url>/dmm3bwsv3 as it was before.

...