The Same Film, in the Language of the House

Operators reach for subtitles first because they are cheap, and then wonder why a title with subtitles in a language still does not perform in that market. The reason is that reading and watching are different activities, and a large part of any audience will not do both at once. Children cannot. Anybody watching while cooking or folding laundry will not. Older viewers frequently find it tiring, and in several very large markets dubbing is simply the norm and subtitled content is regarded as unfinished. None of that is a preference you can argue with, so a catalogue that is technically available in a language and only subtitled is not really available there. An audio track is the version that gets watched.

The tempting shortcut when a dub arrives is to add it as a separate title, and it causes problems immediately. Your catalogue now contains the same film three times, search returns all of them, a viewer who watched the Spanish version gets recommended the English one, and your reporting splits a single piece of content across three rows so nothing tells you how the film actually performed. Keeping the tracks on one title avoids all of that. There is one entry with one set of artwork, one synopsis per language, one position in continue watching and one set of numbers. The metadata around it is covered under multilingual content, and how the entry itself is managed under movies management.

An audio description track narrates what is happening on screen for viewers who cannot see it, and it uses exactly the same mechanism as a dub. It is worth treating as a first class case rather than an afterthought, partly because accessibility requirements around broadcast and streaming have been tightening in a number of jurisdictions, and partly because the cost of supporting it is essentially zero once multiple tracks exist at all. The harder part is sourcing the track, which is a production question rather than a platform one. What the platform has to do is carry it, label it clearly enough that somebody can find it, and let it be selected the same way any other track is.

Most viewers will never open the audio menu, which means the track you start with is the track the overwhelming majority hear. Defaulting sensibly from the language the viewer is already using is therefore worth more than any amount of work on the selection interface, because a good default means the feature is invisible to the people it serves. The exception worth designing for is the household that watches in one language and browses in another, which is extremely common in multilingual markets and is precisely the case a single interface language setting gets wrong. Keeping content language and interface language separate is covered under multilingual content, and the player controls themselves under the video player.