Forum Discussion
Video Indexer vs Content Understanding: which one for domain-specific video analysis?
Your results fit the products’ different strengths: Content Understanding is handling the domain schema, while Video Indexer provides timestamped OCR. For the overlay counter, index the video with Video Indexer, export the OCR insight JSON, and join recognized values to the nearest Content Understanding segment by timestamp. Keep confidence thresholds and manual review because small, low-contrast counters can be missed. Microsoft’s Content Understanding limits state that video is sampled at approximately one frame per second and frames are resized to 512 by 512; they do not document a setting that increases that cadence. Do not rely on schema prompting to improve temporal precision. If every counter change matters, preprocess the footage into higher-frequency still frames or short clips, run OCR separately, then merge those results with the custom-schema output. Retain the original footage and route ambiguous condition classifications to an inspector.
Thank you, Jamony, for your insightful explanation.
I realize now that Video Indexer and Content Understanding are complementary rather than competing services. Video Indexer is stronger in search, OCR, and media intelligence, while Content Understanding is better for generating inspection-ready answers in a controlled schema.
Your insights on OCR extraction and sampling behavior helped clarify the limitations I observed with footage counters and timestamps.
I appreciate the approach of leveraging each service for its strengths and correlating outputs by timestamp instead of using a single analyzer. Thank you for your detailed response.