Default Track Flags
Default track flags provide selection hints that players interpret alongside language, accessibility, and user preferences.
Consider these audio descriptions in an MKV:
| Track | Language | Role | Default eligibility |
|---|---|---|---|
| Main soundtrack | English | Main programme | Yes |
| Translation | German | Main programme | Yes |
| Director commentary | English | Commentary | No |
The default flag helps a player form an automatic choice. In Matroska it describes eligibility for default selection; it is not a universal command to play one numbered track. More than one language can be eligible.
A viewer preferring German can therefore have a suitable default candidate even while English is also marked default. The player combines the file's information with its own selection policy, user preferences, accessibility choices, and any remembered or manual choice.
Why “default English” can still be the wrong choice
Two English tracks satisfy the language preference in the example, but their roles differ. The commentary flag, title, and default eligibility help distinguish them. Marking commentary default just because its language is English blurs the intended automatic choice.
A title containing “Default” is plain descriptive text. It does not set the structured flag. Likewise, removing a default flag does not remove the track: a user may still select the component explicitly.
Subtitles use another kind of hint
Default and forced subtitle flags answer different questions. A default subtitle may contain the full dialogue. A forced track commonly supplies text needed with the chosen soundtrack, such as a sign or a brief exchange in another language.
The forced designation describes the intended selection role; it does not inspect or shorten the subtitle contents. If a full-dialogue track is marked forced, all its events remain in the track. A player following that hint may show far more text than the author intended.
For an Emby selection comparison, start with the actual track combination: effective language, main versus commentary/accessibility role, default eligibility, and subtitle intent. Then compare the user's relevant preferences and whether the session has retained a manual selection. This explains a difference between two apps without assuming either has simply ignored the file.
Correcting these descriptions normally edits the container metadata. The encoded soundtrack and subtitle events can remain the same; what changes is the information automatic selection receives.