Filename FaceInstanceThumbnail insights json response of Azure Video Indexer different than downloaded artifacts

Question

Filename FaceInstanceThumbnail insights json response of Azure Video Indexer different than downloaded artifacts
I am using the Azure Video Indexer to index video’s. Our program download the insights.json and the “Face Instance Thumbnails”. We are using the REST API:

Download insights json:
https://api.videoindexer.ai/{{location}}/Accounts/{{account-id}}/Videos/{{video-id}}/Index?reTranslate=true&includeStreamingUrls=true&accessToken={{access-token}}

Example: insights.json
`
As you can see the json contains “links” to the faces thumbnails like: “FaceInstanceThumbnail_b02e252b-ebc0-4503-8a30-e1d86e436dc3.jpg”

Download Video artifacts
https://api.videoindexer.ai/{{location}}/Accounts/{{account-id}}/Videos/{{video-id}}/ArtifactUrl?type=FacesThumbnails&accessToken={{access-token}}
wich returns a SAS url to download the artifacts, which is a zip file containing all the thumbails. For example:

• sample_1638_1970_838656.jpg
• sample_1848_1970_946176.jpg

In the past the filenames in the zip files corresponded to the links in the insights json, but today (10-05-2022) I figured out the filenames suddenly had a different format: sample_<some-number>_<face_id><some-number>.jpg instead of FaceInstanceThumbnail<thumbnail_id>.jpg. Now it not possible anymore to find the thumbnail for a face.

Answer 1

To benefit the community, posting our discussion from the comments.

Our product engineering team identified a bug, and the fix has been deployed to remedy this issue. It's working fine as expected now.

We apologize for any inconvenience this may have caused.

Thanks @Johan Klijn for your patience and great collaboration.

Additionally,
SummarizedInsights is a shorter version of the insights. We highly recommend using Insights and not using SummarizedInsights. We also recommend passing &includeSummarizeInsights=false in GetVideoIndex api to save time and reduce response length. We didn’t remove the SummarizeInsights as we must be backward compatible and not to break existing APIs.