Microsoft Media and Entertainment United States

Pacers Sports & Entertainment (PS&E)

Document Processing

Pacers Sports & Entertainment needed a custom captioning system that could keep up with fast, unscripted basketball commentary and deliver accurate live captions and translations to deaf, hard-of-hearing, and non-English-speaking fans on arena displays and in its mobile apps.

12 additional languages planned after the initial English and Spanish rollout
Audio preparation for a single game reduced from upwards of five days to roughly two minutes
Caption error rate reduced to just 1.14%
Model training time reduced by 99.97%

Reported impact

Business outcome

PS&E launched the first live in-arena and mobile captioning experience of its kind for Pacers and Fever games, reduced caption error to 1.14%, cut model-training preparation time from days to minutes, and created a scalable foundation for multilingual and future AI-powered fan experiences.

  • Customer Experience
  • Productivity Improvement
  • Scalability
  • Speed to Market

Solution

Pacers Sports & Entertainment built a real-time captioning stack on Microsoft Azure to turn live game commentary into synchronized captions across Gainbridge Fieldhouse screens and the Pacers and Fever mobile apps. Azure AI Foundry provided a secure, containerized environment for training and refining custom Azure AI Speech models with hundreds of hours of Pacers and Fever broadcasts plus structured lists of player, coach, and official names. In production, announcer audio is transcribed and translated by Azure AI Speech, then Azure Functions processes caption events and Azure SignalR Service pushes them to a single endpoint used by both in-arena displays and the mobile app with virtually no lag. The architecture gave PS&E near-instant English captions, added Spanish, and created a path to roll out 12 additional languages and more AI-powered fan experiences.

Data flow

Live announcer audio is sent into Azure AI Speech models trained in Azure AI Foundry, where it is transcribed and translated in real time. Azure Functions processes the caption output and Azure SignalR Service publishes it to a shared endpoint that keeps the Pacers and Fever mobile apps and Gainbridge Fieldhouse displays in sync.

Solution architecture

4 components · 3 layers
  1. Compute
    • Azure AI Speech Transcribes and translates live announcer audio using models tuned to basketball terminology, names, and cadence.
  2. Serving
    • Azure SignalR Service Streams synchronized captions to arena displays and mobile clients with virtually no perceptible delay.
  3. Orchestration
    • Azure AI Foundry Provides the secure environment where PS&E trains, tests, and refines custom speech models before release.
    • Azure Functions Processes caption events and coordinates real-time delivery from the speech service to client endpoints.

Architecture clues

  • Built-in moderation filters prevent inappropriate or misinterpreted content from reaching the screen.
  • Captions are delivered through a single event-driven endpoint shared by mobile and in-arena displays.
  • PS&E used a standard WebView to keep client integration simple for future expansion.
  • Structured text files with player, coach, and official names improved domain-specific transcription accuracy.
  • The custom training dataset used hundreds of hours of Pacers and Fever broadcasts.

Evidence from the source

"By tailoring the model to the Pacers’ broadcast style, they reduced the speech-to-text transcription error rate by 87%."
"Captions are delivered through an event-driven architecture using Azure Functions and Azure SignalR Service."
"Originally, the audio file for a single game took us upwards of five days to manually cut the game audio. Now, using our custom script, it takes us roughly two minutes to cut and encode a game and unload for translation."
"The system had to follow fast, unscripted announcers, recognize game-specific lingo and player names, and still deliver captions instantly to keep fans engaged in real time."
"With each iteration, the team pushed well past their original 10% error rate goal, landing at just 1.14%."
Transparency Evidence & methodology 100/100 reference value · 95% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    3 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence95%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability25/25
    12 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency10/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Microsoft

    Indiana Pacers use Azure AI Foundry to create first live arena captioning service | Microsoft Customer Stories

    First-party
    https://www.microsoft.com/en/customers/story/23957-pacers-sports-and-entertainment-azure-ai-foundry
    Source type
    Vendor-published customer story
    Published
    May 19, 2025
    Supports
    • Customer
    • Industry
    • Region
    • Company size
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • Business outcome
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page May 19, 2025 · Microsoft · First-party
    Open date source