Brand Detection in Microsoft Video Indexer

%3CLINGO-SUB%20id%3D%22lingo-sub-153054%22%20slang%3D%22en-US%22%3EBrand%20Detection%20in%20Microsoft%20Video%20Indexer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-153054%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F114%22%20target%3D%22_blank%22%3E%40Marc%20Mroz%3C%2FA%3E%20-%20when%20features%20like%20this%20launch%20in%20Azure%2C%20do%20they%20also%20automatically%20show%20up%20in%20Stream%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fblog%2Fbrand-detection-in-microsoft-video-indexer%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EBrand%20Detection%20in%20Microsoft%20Video%20Indexer%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-153061%22%20slang%3D%22en-US%22%3ERe%3A%20Brand%20Detection%20in%20Microsoft%20Video%20Indexer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-153061%22%20slang%3D%22en-US%22%3E%3CP%3ENo%2C%20not%20automatically.%20There%20are%20a%20couple%20of%20facets%20to%20this.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAny%20underlying%20service%20we%20leverage%20in%20Stream%20needs%20to%20be%20fully%20compliant%20(ISO%2C%20SOC%2C%20HIPPA%20certs%2C%20O365%20Tier%20C%2B%2C%20etc).%20This%20is%20a%20requirement%20so%20that%20Stream%20itself%20remains%20complaint.%20Some%20of%20the%20underlying%20new%20AI%20services%20offered%20from%20MS%20and%20VI%20don't%20yet%20have%20their%20compliance%20certifications%2C%20as%20such%20we%20can't%20use%20them%20in%20Stream%20until%20they%20do.%20(The%20various%20feature%20by%20feature%20from%20VI).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20addition%20VI%20does%20build%20some%20UI%2FUX%20as%20part%20of%20their%20offering%20but%20mostly%20it's%20APIs.%20We%20need%20to%20build%20our%20own%20UI%2FUX%20on%20top%20of%20these%20capabilities%20to%20make%20sure%20they%20fit%2Fwork%20with%20Stream%2C%20etc.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EToday%20Video%20Indexer%20as%20I%20understand%20is%20somewhat%20of%20a%20layer%20on%20top%20of%20Azure%20Media%20Services%20adding%20the%20extra%20fancy%20capabilities.%20Over%20the%20course%20of%20time%20we'll%20be%20working%20to%20merge%20VI%20capabilities%20and%20AMS%20more%20closer%20together%2C%20so%20when%20we%20deploy%20AMS%20to%20a%20new%20DC%20we%20can%20leverage%20the%20VI%20stuff%20from%20there%20as%20well%20without%20other%20deployments%20or%20calls%20to%20other%20DCs%2C%20etc.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Regular Contributor

Hi @Marc Mroz - when features like this launch in Azure, do they also automatically show up in Stream?

 

Brand Detection in Microsoft Video Indexer

1 Reply

No, not automatically. There are a couple of facets to this. 

 

Any underlying service we leverage in Stream needs to be fully compliant (ISO, SOC, HIPPA certs, O365 Tier C+, etc). This is a requirement so that Stream itself remains complaint. Some of the underlying new AI services offered from MS and VI don't yet have their compliance certifications, as such we can't use them in Stream until they do. (The various feature by feature from VI).

 

In addition VI does build some UI/UX as part of their offering but mostly it's APIs. We need to build our own UI/UX on top of these capabilities to make sure they fit/work with Stream, etc.

 

Today Video Indexer as I understand is somewhat of a layer on top of Azure Media Services adding the extra fancy capabilities. Over the course of time we'll be working to merge VI capabilities and AMS more closer together, so when we deploy AMS to a new DC we can leverage the VI stuff from there as well without other deployments or calls to other DCs, etc.