One action can have two policies
A player may request its own content match while the device offers an additional manual feature. NVIDIA explicitly notes that some applications already support automatic matching when discussing its beta option.
The mere presence of both controls does not prove a conflict, but it creates more than one state to document. Do not assume one universal arrangement fits every app.
Record both original preferences
Write down the app's supported matching choice and the box's normal mode. Include TV and receiver information. Use the same permitted reference and playback sequence for comparisons.
Do not change HDR range, refresh policy and permanent resolution simultaneously. A smoother start after several changes leaves the cause uncertain.
Compare one controller at a time
Where documented and practical, assess the application's normal path first, then the device's offered experimental path with the app preference understood. Observe start, stop and return to browsing.
This is a proposed comparison, not a claim that every player exposes a switch or that a consumer should alter undocumented developer options.
Watch the transition timing
One blank at the beginning may be a mode change. Several changes around start, stop or preview transitions deserve a more detailed sequence. Continuous playback failure is another observation.
A television information overlay can document received refresh, but it still describes output rather than independently measuring encoded source cadence.
Give support the policy state
Report both settings, the action that triggered the request and the final display mode. That is more useful than simply saying matching is on.
No app implementation or HDMI behaviour was tested here. The article explains policy ownership using NVIDIA's documented example and does not guarantee an optimal configuration, a beta feature or IPTV Canada compatibility.
Distinguish an app request from a receiver result
The application can request a mode that the connected display route does not accept or establish reliably. A request appearing in an app menu is therefore not the final result. Record both the requested policy and the television's received signal where its diagnostics expose it. If a receiver or switch sits in between, preserve that equipment sequence; the app alone cannot certify the complete HDMI path.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
- NVIDIA SHIELD TV guide — Official current guide excerpts: microSD removable/device storage, display modes and experimental frame-rate matching; model/software qualifications retained.
- NVIDIA SHIELD TV Pro guide — Official guide sections inspected: USB port computer-transfer role, remote controls and maintenance. Guide's older AI limit is not treated as overriding newer Pro specifications.
