In the last release of Azure Media Indexer, we had a few bugs impacting usability.  Thanks to all of the users with their quick feedback, we have been able to remain agile and have made some updates!

Output Formats

In version 1.2, we updated the configuration file and gave users the ability to choose which output files Indexer will generate.  However due to a parsing bug, this flag was being ignored until now.  With version 1.2.1, we will now be properly outputting only the desired files!

Don’t remember the configuration change?  Check out the previous post: Azure Media Indexer v1.2

Primary Asset File

Next, we changed the logic that determines which file will be the primary AssetFile of an Indexer job’s output asset.  The media processor will choose a primary AssetFile in the following priority order:

1. TTML file (if it exists)
2. First CaptionFormat specified in XML (if there is no TTML)

WebVTT Timestamp Issue

Finally, we fixed a bug causing the WebVTT output file to contain mislabeled timestamps in certain situations.

As always, feel free to reach out to us with any questions or comments at indexer@microsoft.com.

Not sure what Azure Media Indexer is?  Check out the introductory blog post here!

Indexer has been updated!  Check out the release notes for version 1.3.2 to learn more.