Account Preference or Title-Specific Choice: Which Should Win?
A precedence framework that treats account audio preferences as starting points and title choices as intentional, testable exceptions.
In short: As a household policy, use the account or profile preference as a starting point and respect a deliberate title-specific choice for that title or session. As a technical claim, do not assume either always wins. Verify the actual starting track, explicit selection, and persistence in the current profile, item, version, device, episode, and resume context.
“Which should win?” contains two questions: what behavior would be useful, and what behavior the current product actually implements. Keep those answers separate.
Define the desired policy
A broad preference reduces repeated choices when a viewer usually wants the same language or role. A title-specific choice handles exceptions, such as original audio for one film, a dub for a group session, or audio description where available.
A practical policy is:
- start with the viewer's broad preference;
- let an explicit title choice override the starting point for the intended scope;
- do not assume the exception should spread to unrelated titles;
- make shared-profile choices reversible for the next viewer.
This is a governance recommendation, not a statement about Norva's selection algorithm.
Map the possible scopes
Record where a choice might apply:
- account;
- profile;
- title;
- series or episode;
- media version;
- device;
- current playback session;
- eligible offline copy.
Only the current interface and observed behavior can confirm which scopes exist. A profile is an organisational context, not proof of a private or independent preference store.
Test actual precedence
Use one title with at least two clearly identifiable tracks:
- record the profile or account preference if visible;
- open the title and note the starting track;
- select another track explicitly;
- play a short dialogue sample;
- leave and reopen the same title;
- record the selected marker and what is heard;
- test one adjacent episode or device only if needed.
Do not change source, version, account setting, and device during the same test.
Original evidence: precedence worksheet
Use this table:
| Layer | Desired choice | Starting result | After explicit choice | After reopen |
|---|---|---|---|---|
| Account/profile | Visible preference or unknown | Exact track | Exact track | Exact track |
| Title/version | Explicit selection | Before sample | Verified sample | Observed result |
Add “not exposed” when a setting is absent and “not tested” when the context was not checked. Those labels are more reliable than a guess.
Decide what should happen next
If the explicit choice persists as desired, document its tested scope. If it resets to the broad preference, decide whether the viewer can accept reselecting for that title. If neither behavior is consistent, follow the preference-persistence diagnostic before reporting a defect.
Use the complete audio management guide to compare version, episode, device, resume, and offline contexts.
Protect shared-profile viewers
On a shared profile, the most recent explicit choice may surprise another person even when the product works as designed. Agree a session-opening check and a restore rule. The shared-profile audio guide provides a minimal household workflow.
Do not inspect private history to determine who changed the track. Ask the relevant viewers and focus on the current state.
Account for accessibility
An accessibility need should not be dismissed as an inconvenient exception. If a viewer relies on audio description or a particular language, prioritise participation and verify the option for each relevant title. Availability still depends on the supplied media and metadata.
Common mistakes and limitations
Avoid claiming universal precedence, confusing desired policy with observed behavior, testing on an ambiguous track, and generalising from one title to a whole library.
Norva's published pages can describe available features, while exact current behavior should be checked in the supported interface and, when unresolved, through support.
Frequently asked questions
Should a title choice permanently change the account preference?
Usually that would broaden an exception unnecessarily, but verify what the current controls actually do before relying on a policy.
What if the title has no matching preferred track?
Choose deliberately from the available entries, record the exception if useful, and do not treat absence as a preference failure.
Can a shared profile remember different choices for each person?
Do not assume so. Use separate personal contexts when appropriate or agree a recheck-and-restore routine.