question

JohanKlijn avatar image
0 Votes"
JohanKlijn asked ajkuma-MSFT answered

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

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.


azure-media-services
indexjson.txt (477.7 KiB)
· 7
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JohanKlijn, Thanks for reporting this issue. I'm checking on this internally and will get back to you shortly.

In the interim, I'll leave this thread open for other community members/SMEs to share their insights.

Apologies for any inconvenience this may have caused. Thanks for your patience.

0 Votes 0 ·

JohanKlijn, Following-up.

Our product team is investigating this issue, I'll post back as soon as I hear more updates on this.

Thanks for your patience and cooperation!

0 Votes 0 ·

JohanKlijn, Our product engineering team have identified the problem, the fix is deployed which should be rolling out over by this week, but we do not have an exact ETA to share.

I'll share an update as soon as I hear more. Thanks again for bringing this to our attention.
We apologies for any inconvenience this issue may have caused.

Please note that this timeline is just an estimate and is subject to change, depending on a myriad of factors.

0 Votes 0 ·

@ajkuma-MSFT : thanks for the update. More or less related to this topic.... it still unclear which 'faces' element a consumer of the API should use, because there are two different formats of faces element in insights json response. Sometime ago I already created a issue on github, see https://github.com/MicrosoftDocs/azure-docs/issues/89860, but unfortunately there no answer yet.

0 Votes 0 ·

JohanKlijn, Thanks for sharing the Azure doc. yes, It looks like the Azure doc can add additional clarity, so I'm following-up on this.

Apologies for not getting an answer on your Azure doc issue, I have followed-up further on this internally.

0 Votes 0 ·
Show more comments

1 Answer

ajkuma-MSFT avatar image
0 Votes"
ajkuma-MSFT answered

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 @JohanKlijn 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.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.