When upgrading to 5.10 , the includes a new and improved transcode system is automatically used. The old transcode system can still be used in 5.10, but it is considered deprecated and will not be available in future releases. Customers must therefore be migrated to the new transcode system before upgrading to a 6-version.
If you are a consultant, please see DC 5.10 Formats - Migration for more information on how the migration to the new transcode system is handled and things to be aware of in relation to this migration.
...
Handling of unavailable renditions.
Handling of failed renditions.
Search2.
New thumbnail formats.
Source formats.
jpg
/jpeg
formats
Handling of unavailable renditions
...
Note that most modern browsers limit the maximum number of simultaneous HTTP connections. Thus, if you show a lot of renditions 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.
In rare cases, the generation of a rendition might fail. In the old transcode system, an asset streamer URL would not be returned in this case. In the new transcode system, an asset streamer URL is returned in this case, but the asset streamer request returns an HTTP 502 error. If the mode
is set to getFallbackImageIfUnavailable
, a fallback image is still returned in this case.
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 that takes more than 100 seconds to become available with the INewAssetStreamerService.GetAssetDownloadStream
method, your request will time out before the rendition is returned. To disable this timeout, use the following setup in your application startup logic:
...
Note that this removes the default timeout of 100 seconds from all HTTP requests performed with the SDK. However, it is still possible to control the timeout per-request by passing a cancellation token to the SDK method used. The effective timeout is always the smallest of the passed cancellation token and the timeout configured for the HTTP client used by the SDK.
Handling of failed renditions
In rare cases, the generation of a rendition might fail. In the old transcode system, an asset streamer URL would not be returned in this case. In the new transcode system, an asset streamer URL is returned in this case, but the actual request returns a HTTP 500 error. A fallback image is never returned by the asset streamer when the generation of the requested generation has failed. Please consider showing a fallback image to end users if a HTTP 500 error is returned.
Search2
Search2 is being deprecated, and it is highly advised to start using the new API or the SDK.
...
The new transcode system now supports a special SourceFormat
that can be used to refer to and get the source files of assets. A special “Original” format of this type is now defined out-of-the-box. If you have previously hard-coded the “Original” format in a list of available download renditions, this can lead to two “Original” formats being shown. It should no longer be necessary to have any special-case handling for getting source formats.
jpg
/jpeg
formats
The new transcode system uses the jpeg
extension for jpg
/jpeg
files and renditions. Existing renditions that have not been generated with the new transcode system will have the same extension as before. Thus, existing jpg
/jpeg
files and renditions will still be returned with the jpg
extension if this was the behavior before upgrading to 5.10. New jpg
/jpeg
renditions that are generated with the new transcode system will have the jpeg
extension.
Please be aware of this if you have any custom logic that relies on the jpg
extension and does not handle the jpeg
extension.