Skip to main content
Vision & MultimodalFebruary 5, 20264 min read

Computer Vision at Scale: From Detection to Game Awareness

Building production computer vision systems requires more than good models—it demands a pipeline architecture that handles ingestion, training, and cross-cloud delivery at scale.

Luís Roque
Luís Roque
Founder & Partner

Introduction

Sports analytics has pushed computer vision beyond object detection into full game awareness: player tracking, ball trajectory, event recognition, and tactical insights. The models are only part of the story. Delivering a system that ingests live feeds, trains on domain-specific data, and serves inferences across clouds and regions is a systems problem.

We designed an 8-phase pipeline for a sports analytics client with a 50-week roadmap from prototype to production. The architecture—ingestion, detection, tracking, event recognition, training loops, and cross-cloud delivery—is reusable for any domain where vision meets real-time data at scale.

The 8-Phase Pipeline

Phase 1: Ingestion — Multi-camera feeds arrive as streams. We normalize formats, handle reconnections, and buffer for downstream processing. Latency budgets vary by use case: live broadcast needs sub-second; post-game analysis can tolerate minutes.

Phase 2: Detection — Person and ball detection run on every frame. We use a hybrid approach: lightweight models for real-time, heavier models for offline refinement. Detection outputs are passed to the tracking layer.

Phase 3: Tracking — Multi-object tracking associates detections across frames and cameras. We use trackers that handle occlusions and camera handoffs. Identity persistence across views is critical for player-level analytics.

Phase 4: Calibration — Camera intrinsics and extrinsics enable 2D-to-3D projection. We calibrate using known court/field geometry and refine with bundle adjustment. Accurate calibration underpins position and velocity estimates.

Phase 5: Event Recognition — Trajectories and positions feed event classifiers: shot, pass, tackle, etc. These can be rule-based (e.g., ball crosses line) or learned (e.g., shot type from trajectory). Events become the atomic units for higher-level analytics.

Phase 6: Game Awareness — Aggregating events into possessions, plays, and tactical patterns. This layer answers questions like "What was the passing network in this possession?" or "Where did the defensive line break?"

Phase 7: Training Loop — Models improve with domain data. We collect labels (manual or semi-automated), retrain detection and event models, and validate on held-out games. The loop runs continuously; new seasons and leagues require adaptation.

Phase 8: Delivery — Inferences and analytics are served to broadcast, coaching, and fan applications. We support multi-cloud deployment so clients can run in their preferred region and comply with data residency requirements.

Training Without Annotations

Fully supervised training for 50+ event types across multiple sports is prohibitively expensive. We use self-supervised and semi-supervised methods:

  • Temporal consistency — Adjacent frames should produce consistent embeddings. We train encoders to be invariant to small temporal shifts, improving robustness.
  • Weak labels — Broadcast metadata (e.g., "goal" timestamps) provides weak supervision. We use multiple instance learning to propagate labels to frame-level predictions.
  • Synthetic data — Rendered game scenarios with known ground truth augment training. Domain randomization helps bridge the sim-to-real gap.

These approaches reduced annotation cost by roughly 40% while maintaining accuracy on held-out events.

Cross-Cloud Architecture

Clients often have existing cloud commitments (AWS, GCP, Azure) and data residency constraints. Our pipeline is cloud-agnostic: ingestion and processing run in containers; we use object storage and message queues that have equivalents in each cloud. A single control plane orchestrates deployment; the data plane runs where the client specifies.

For the sports analytics engagement, we deployed to AWS in the US and GCP in the EU to satisfy regional requirements. The same model artifacts and pipeline code run in both; only configuration differs.

Conclusion

Computer vision at scale is a pipeline problem. Detection and tracking are table stakes; the real value comes from event recognition, game awareness, and continuous improvement via the training loop. Self-supervised and semi-supervised methods reduce annotation burden. Cross-cloud delivery ensures the system fits into existing infrastructure. The 8-phase architecture we used for sports analytics generalizes to manufacturing, retail, and any domain where vision meets high-volume, real-time data.

Tags:

Computer VisionDeep LearningSports Analytics

Talk to ZAAI about a system like this.

We build AI products and bespoke systems for enterprises that need them in production, not in a deck.

Book a call