Quick Example
The preferred RTStream interface follows the same Understand → Index → Retrieve flow as videos, but runs continuously on new stream windows.Initial support for the new interface is VLM-only with time-based segmentation. See Understand & Index RTStreams for the complete interface and migration notes.
Visual Indexing Compatibility
The legacy helperindex_visuals() remains available while applications migrate to rtstream.understand(...) + rtstream.index(...). It creates a continuous VLM scene index directly from stream frames.
batch_config options
Examples:
Managing legacy scene indexes
Audio Indexing
Extract insights from audio tracks:Audio batch_config
Transcription
Real-time speech-to-text:Search
Query indexed content with natural language:Search Results
Each shot contains:Stream Generation
Usegenerate_stream() to create a playable stream for a time range. You can optionally pass player_config to attach metadata to a shareable player URL.
player_url vs stream_url
generate_stream() returns player_url and stores both URLs on the instance. Use player_url for sharing and embedding, stream_url for custom player integrations.
player_config
player_config is optional. When provided, the player URL includes the metadata for sharing.
Embed Code
After generating a stream, you can produce embeddable HTML:RTStream does not support
auto_generate because generate_stream() requires explicit start and end parameters.Events and Alerts
Events are reusable detection rules. Alerts wire events to indexes for notifications.Create Event
Create Alert
Alert Delivery
Manage Alerts
WebSocket Events
Receive real-time events by passingws_connection_id:
Event Channels
Next Steps
Stream Lifecycle
Start, stop, and reconnect patterns
RTSP Ingest
Connect RTSP sources