An absent attribute can describe a location
RFC 8216 permits an EXT-X-MEDIA entry of TYPE=AUDIO to omit its URI attribute. For that declaration, the audio is expected inside the media playlist associated with the referencing EXT-X-STREAM-INF entry. The client is required to assume that audio is present in every video rendition specified by that variant.
A network log without a separate audio-playlist request can therefore be consistent with the manifest. Do not manufacture an audio URL from the language name or copy one from an unrelated presentation. First establish what this master playlist actually declares.
Trace the reference, then inspect the media
Start with the variant’s AUDIO group reference and find the corresponding EXT-X-MEDIA entries. Record each group, name and whether a URI is present. Follow the video playlist that belongs to the variant and inspect an authorised sample with a suitable media-inspection tool. A label in the master is an expectation; the sample shows what the packaged resource contains.
For a synthetic inspection note, distinguish these three outcomes. A URI is absent and the expected audio is present: the absence alone is not the fault. A URI is absent but the referenced media contains no expected audio: investigate the declaration and packaging together. A URI is present but retrieval fails: preserve that actual request and response as a different problem.
Do not apply one rule to every media type
This distinction belongs to the specific tag and media type. It is not a general rule that missing URLs are harmless. Keep the entire entry with your report so another reviewer can see which interpretation applies.
| EXT-X-MEDIA type | URI rule in RFC 8216 | Inspection consequence |
|---|---|---|
| AUDIO | May be omitted | Check the referencing video media for the declared audio. |
| SUBTITLES | Required | An omitted subtitle URI needs investigation. |
| CLOSED-CAPTIONS | Must be absent | Use the in-stream caption declaration; do not invent a subtitle request. |
Preserve a small reproducible evidence set
Keep a redacted master excerpt, the selected variant and playlist identifiers, the sample’s track information and the expected language or audio role. Avoid publishing credential-bearing media URLs. Recheck the same relationship after a packaging revision. Bandwidth arithmetic is a separate release check covered by the main rendition-budget guide; it cannot prove that the declared audio exists.
Questions answered
Must every HLS audio option cause a separate audio-playlist request?
No. An AUDIO entry without URI declares audio carried in the referencing video media under RFC 8216.
Can the same omission be accepted for a SUBTITLES entry?
No. RFC 8216 requires URI for that type; inspect the complete tag rather than reusing the AUDIO rule.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.