Enhance Media API fails when GCP storage bucket has config field 'contentType' – Dolby.io Support

Description:

When calling Media APIs, input/output files are located on Cloud platforms like GCP/AWS/Azure as outlined here. Not all storage bucket configurations are supported by our Media API service.

In this instance Media API call like Enhance fails and return error 500 (problem/internal-error). This happens because 'contentType' field is specified in Google Cloud Platform storage bucket.

Example of GCP bucket configuration which causes the problem:

storage.bucket(bucket).file(req.filename).getSignedUrl({
version: 'v4',
action: "write",
expires: 1000 * 60 * 60, // Hours to ms
contentType: "audio/flac"            <------- field which causes the problem 
});

Affected Product:

Dolby Product(s)

Media Enhance/Analyze/Transcode/Mastering API

Workaround:

The field 'contentType' should be removed from the storage bucket configuration.

storage.bucket(bucket).file(req.filename).getSignedUrl({
version: 'v4',
action: "write",
expires: 1000 * 60 * 60, // Hours to ms
contentType: "audio/flac" -        <------ delete this field 
});

References:

Third Party Reference : N/A