Skip to main content
If your task is running and ingesting a stream but you’re not seeing any highlights, check the following common causes.

​
No Commentary

Narrative relies on spoken commentary to detect highlights. A stream with only crowd noise, ambient audio, or music — even if it contains an audio track — will not produce reliable results. Make sure your source includes active play-by-play or color commentary.

​
Unsupported Commentary Language

Commentary must be in one of the 50 supported languages. If the commentary is in a language Narrative does not support, highlights will not be detected. Language is detected automatically — no configuration is needed — but the language must be on the supported list.

​
Duplicate Highlights

Narrative is designed to process a game stream linearly in real time. If the same segment of a stream is sent to the same task more than once (for example, by restarting a file from the beginning into a task that already ingested it), previously identified highlights will not be detected again. Each task expects a continuous, forward-moving stream.

​
Poor Audio Levels

If crowd noise or other background audio overpowers the commentary — making it virtually inaudible — Narrative may not be able to extract speech reliably enough to detect highlights. Similarly, if the commentary track is mixed at a very low level relative to the rest of the audio, detection accuracy will suffer. Ensure commentary is clearly audible in the mix.