The voice was cast for one language, the beats were timed to one script, and the claims were written for one market. By the time the second track starts, the decisions that would have made it work have already been made.
01
Why the track is declared at greenlight
Three decisions made early determine whether a regional track can work at all, and all three are made before anyone is thinking about the second language.
- 01Voice casting
An identity has to survive every declared track. Cast for one language and the second track gets a different-sounding character, because you are now matching a performance rather than casting a person.
- 02Beat timing
Episodes are timed against dialogue. A line that runs four seconds in one language may run six in another, and a 90-second episode has nowhere to put the extra two.
- 03Claims and cultural restrictions
For branded work, a claim substantiated in one market is not substantiated in another by being translated. For story work, the same is true of cultural restrictions.
02
Tracks block, repair and review independently
The corollary of sharing canon is that everything else is separate. A track has its own rights position where the grant is language-bound, its own captions, its own native reviewer and its own delivery package for its market.
That independence is what keeps one problem from becoming everyone's problem. A melody cleared only for Hindi blocks the Tamil track. It does not block the season.
| Element | Shared | Per track |
|---|---|---|
| Canon and story state | Yes | No |
| Picture and shot structure | Yes | No |
| Voice and pronunciation | No | Yes |
| Captions and reading speed | No | Yes |
| Rights where the grant is language-bound | No | Yes |
| Native review gate | No | Yes |
| Delivery package | No | Yes |
03
What we are not claiming
04
Questions people ask
Which regional languages do you support?
Two additional Indian-language tracks alongside Hindi at launch, decided per production during validation. We will name languages on this site when we can point at production evidence for them rather than an intention.
Is a regional track cheaper than a separate production?
It should be, because it shares canon, story state, picture and approvals, and only the track-specific work is new. Cost per language and market track is one of the core metrics we measure, and we will publish ours rather than estimate yours.
Who reviews a Tamil track?
A native Tamil reviewer, as a named approver at their own gate. A Hindi reviewer cannot be expected to catch a Tamil pronunciation problem, and a system that pretends otherwise is how localization quality quietly degrades.
Can different tracks have different edits?
Yes where the market requires it, and each divergence is recorded. The default is that tracks share the picture, because divergent edits multiply the review burden and are the main way a language track turns into a separate project again.
What if only one track performs?
That is useful information and it is one of the things the retention gate looks at. Language-track performance against the same episode is a cleaner comparison than most marketing tests ever get, because everything except the track is identical.