github.com/NVIDIA-AI-Blueprints/video-search-and-summarization @v3.2.0

NVIDIA AI Blueprint: Video Search and Summarization (VSS)

Table of Contents

• Overview
• Use Case / Problem Description
• Agent Workflows
• Software Components
• Target Audience
• Repository Structure Overview
• Documentation
• Prerequisites
• Hardware Requirements
• Quickstart Guide
• Contributing
• License

Overview

The NVIDIA Blueprint for Video Search and Summarization (VSS) provides a suite of reference architectures for building vision agents and AI-powered video analytics applications. Those architectures bring together accelerated vision microservices, vision language models (VLMs), and large language models (LLMs) so you can use them in existing applications, as standalone microservices, or as part of a larger vision agent.

VSS is organized into three areas of processing and analysis: real-time video intelligence (feature extraction, embeddings, and stream understanding with results published to a message broker), downstream analytics (enrichment of metadata into trajectories, incidents, and verified alerts), and agentic and offline processing (orchestrated tools for search, Q&A, summarization, and clip retrieval, including via the Model Context Protocol).

This repository implements the blueprint and powers the NVIDIA build experience for natural-language video agents—search, summarization, visual Q&A, and related workflows—backed by generative AI, VLMs and LLMs, and NVIDIA NIM microservices as configured in the stacks below.

Use Case / Problem Description

The NVIDIA AI Blueprint for Video Search and Summarization addresses the challenge of deploying visual agents capable of interacting with large volumes of video data, both stored and streamed. This can be used to create vision AI agents, that can be applied to a multitude of use cases such as monitoring smart spaces, warehouse automation, and SOP validation. This is important where quick and accurate video analysis can lead to better decision-making and enhanced operational efficiency.

Agent Workflows

We provide multiple reference Agent Workflows which demonstrate how the individual components can be leveraged by an agent:

Software Components

1. NIM microservices: Here are models used in this blueprint:

   • Cosmos-Reason2-8B
   • NVIDIA Nemotron-Nano-9B-v2

2. Real-time video intelligence: The Real-Time Video Intelligence layer extracts rich visual features, semantic embeddings, and contextual understanding from video data in real-time, publishing results to a message broker for downstream analytics and agentic workflows. It provides three core microservices for processing video streams.

3. Downstream analytics: The Downstream Analytics layer processes and enriches the metadata streams generated by real-time video intelligence microservices, transforming raw detections into actionable insights and verified alerts.

4. Agent and offline processing: The top-level agent leverages the Model Context Protocol (MCP) to access video analytics data, incident records, and vision processing capabilities through a unified tool interface. It integrates multiple vision-based tools including video understanding with Vision Language Models (VLMs), semantic video search using embeddings, long video summarization for extended footage analysis, and video snapshot/clip retrieval.

Target Audience

This blueprint is designed for ease of setup with extensive configuration options, requiring technical expertise. It is intended for:

1. Video Analysts and IT Engineers: Professionals focused on analyzing video data and ensuring efficient processing and summarization. The blueprint offers 1-click deployment steps, easy-to-manage configurations, and plug-and-play models, making it accessible for early developers.

2. GenAI Developers / Machine Learning Engineers: Experts who need to customize the blueprint for specific use cases. This includes modifying the pipelines for unique datasets and fine-tuning LLMs as needed. For advanced users, the blueprint provides detailed configuration options and custom deployment possibilities, enabling extensive customization and optimization.

Repository Structure Overview

Documentation

For detailed instructions and additional information about this blueprint, please refer to the official documentation.

Prerequisites

Obtain API Key

• NVIDIA AI Enterprise developer licence required to local host NVIDIA NIM.
• API catalog keys:
• NVIDIA API catalog or NGC (steps to generate key)

Hardware Requirements

The platform requirement can vary depending on the configuration and deployment topology used for VSS and dependencies like VLM, LLM, etc. For a list of validated GPU topologies and what configuration to use, see the GPU requirements.

Quickstart Guide

Launchable Deployment

Ideal for: Quickly getting started with your own videos without worrying about hardware and software requirements.

Follow the steps from the documentation and notebook in deploy/docker/scripts directory to complete all pre-requisites and deploy the blueprint using Brev Launchable in a 2xRTX PRO 6000 SE AWS instance. - deploy/docker/scripts/deploy_vss_launchable.ipynb: This notebook is tailored specifically for the AWS CSP which uses Ephemeral storage.

Docker Compose Deployment

Ideal for: Deploying a VSS agent on your own hardware or bare metal cloud instance.

System Requirements

• OS:
  • x86 hosts: Ubuntu 22.04 or Ubuntu 24.04
  • DGX-SPARK: DGX OS 7.4.0
  • IGX-THOR: Jetson Linux BSP (Rel 38.5)
  • AGX-THOR: Jetson Linux BSP (Rel 38.4)
• NVIDIA Driver:
  • 580.105.08 (x86 hosts with Ubuntu 24.04)
  • 580.65.06 (x86 hosts with Ubuntu 22.04)
  • 580.95.05 (DGX-SPARK)
  • 580.00 (IGX-THOR and AGX-THOR)
• NVIDIA Container Toolkit: 1.17.8+
• Docker Engine: 28.3.3 <= Docker Engine < 29.5.0
• Docker Compose: v2.39.1+
• NGC CLI: 4.10.0+

Docker upper bound: Docker Engine 29.5.0+ may fail pulling NGC-hosted images. Use Docker Engine 28.3.3 or another supported version below 29.5.0.

Please refer to Prerequisites section here for installation details.

Contributing

See CONTRIBUTING.md for the development workflow, branch naming convention, and PR guidelines.

License

Refer to LICENSE