• NVIDIA GPU Driver Version (valid for GPU only)
NVIDIA Driver: 570.211.01
• Issue Type( questions, new requirements, bugs)
Quenstion • How to reproduce the issue ? (This is for bugs. Including which sample app is using, the configuration files content, the command line used and other details for reproducing)
**
**
Hi,
I’ve been going through the DeepStream 9.0 documentation and noticed that MTMC from previous versions no longer appears to be maintained. From what I understand, MV3DT may be intended as its replacement.
Could you clarify the relationship between these two approaches? Specifically:
What are the main differences in terms of architecture and capabilities?
Do they address the same use case (multi-target, multi-camera tracking), or are there key scope changes?
Is MV3DT a direct successor to MTMC, or should they be considered distinct solutions?
Any guidance or pointers to detailed documentation would be appreciated.
MV3DT (Multi-View 3D Tracking) and MTMC (Multi-Target Multi-Camera) are two distinct approaches for multi-camera tracking in the DeepStream SDK. While they share some similarities, they have different architectures, capabilities, and use cases.
Main Differences:
Architecture:
MTMC: A centralized approach that aggregates metadata from multiple cameras and performs global target association and clustering.
MV3DT: A decentralized approach that enables real-time collaboration among cameras with overlapping fields of view (FOVs) to perform distributed global ID assignment and tracklet propagation.
Capabilities:
MTMC: Focuses on multi-target tracking across multiple cameras, with an emphasis on global target association and clustering.
MV3DT: Provides a more comprehensive solution for multi-view 3D tracking, including object detection, single-view 3D tracking, and distributed global ID assignment.
Use Cases:
MTMC: Suitable for applications that require centralized processing and global target association, such as surveillance systems.
MV3DT: Designed for applications that require real-time, decentralized processing, such as smart cities, industrial automation, and autonomous vehicles.
Relationship between MV3DT and MTMC:
MV3DT is not a direct successor to MTMC, but rather a distinct solution that addresses a broader range of use cases. While MTMC is no longer maintained in DeepStream 9.0, MV3DT provides a more advanced and flexible solution for multi-camera tracking.
Guidance and Documentation:
For more information on MV3DT, refer to the DeepStream 9.0 documentation, specifically the sections on MV3DT and the NvMultiObjectTracker Library. Additionally, the DeepStream Tracker 3D Multi-View reference repository provides example workflows and sample datasets for MV3DT.
In summary, MV3DT and MTMC are two distinct approaches for multi-camera tracking in DeepStream, with different architectures, capabilities, and use cases. MV3DT provides a more comprehensive solution for multi-view 3D tracking, while MTMC is no longer maintained.