The procurement answer in one screen
“DTS:X” is not a complete hardware tier. It identifies an audio decoding and licensing capability, not the processor, Android release, memory configuration, output path or quality-control regime of an android tv box manufacturer. A procurement-ready statement must identify the DTS:X implementation, supported profiles and sample rates, decoded or pass-through behavior, physical output, content-protection route and test evidence. “DTS:X ready” on a quotation is not an acceptance criterion.
Ask the vendor for the exact SoC, AOSP or Google Android TV position, production BOM revision, RAM/ROM, HDMI and audio outputs, DRM position, middleware responsibility, codec test results and a configuration-controlled sample. A chipset name alone does not establish a shipping feature. The approved unit must match the proposed production unit in firmware, memory, ports, accessories and regional configuration.
Separate the request into 3 contracts: hardware and firmware capability, content-rights compliance, and operational assurance. The DTS:X Android TV box guide defines the codec-specific questions; the canonical android tv box manufacturer topic covers broader supplier selection.
Reject 3 weak answers. “Same as the previous generation” requires the predecessor, changed parts and retained evidence. “All boxes support DTS:X” requires an order-specific configuration. “No issue” requires the decoder implementation, licensing route, firmware behavior and physical output. A managed IPTV rollout also needs middleware, provisioning, regional rights and image lifecycle evidence; a retail shipment may need less integration control, but it still needs a tested unit.
The procurement decision is not simply which model carries a DTS logo. It is which android tv box manufacturer can connect protected content, Android software, decoder hardware, physical output and endpoint behavior to a signed golden sample. DataMax can be asked for a platform and evidence pack against this structure. The next sections turn that principle into RFQ lines, factory controls, model comparisons and deployment tests.
A decision path for the RFQ
Turn the requirement into a sequence: content contract, playback path, platform lock, evidence request, sample test and change control.
- Define the content contract State whether DTS:X must be decoded, passed through, output as PCM or only advertised. Record sample rate, channel layout, protected-content state and Dolby/DTS coexistence needs.
- Name the OS contract Require Google Android TV, AOSP Android TV, operator middleware or a white-label OTT build. State the release, build identifier, update owner and qualification evidence.
- Lock the signal path Identify HDMI, S/PDIF or analogue routing, EDID behavior, HDCP treatment, endpoint models and decoded-versus-encoded expectations.
- Freeze the configuration Request SoC, RAM/ROM, ports, wireless options, accessories and production BOM revision. Mark standard, optional and custom variants.
- Demand evidence Request codec reports, DRM documentation, Android qualification records, factory process evidence and sample traceability.
- Test the golden sample Check DTS:X playback, navigation, reboot recovery, thermal behavior, endpoint negotiation and middleware integration on the exact production image.
- Approve change control Define notification, retest and approval requirements for SoC, memory, firmware, middleware, supplier and accessory substitutions.
Paste-ready RFQ language should be specific: “State the exact DTS:X implementation, supported profiles and tested output path; provide the SoC and production BOM revision; identify the Android distribution and qualification status; list mandatory DRM and HDCP support; attach test evidence and nominate a golden sample.” Replace “DTS:X supported” with “decode failure must be recorded in the approved test report.”
Add a content-source field. State whether testing used protected operator content, a controlled licensed asset or a diagnostic file, and whether the result changes under the intended DRM. Unrestricted media playback does not close the risk around a protected service path.
Add an endpoint field. Name the television, AV receiver, amplifier, sound bar and cable path, including firmware versions where relevant. Require separate results for decoded PCM, encoded pass-through, channel mapping, synchronization, silence and source switching. Until the endpoint is identified, the requirement is a feature request rather than an acceptance criterion.
The first message to an android tv box manufacturer should contain the deployment, OS type, DTS:X behavior, output interfaces, content-protection needs, expected volume, target market, customization scope and a request for an equivalent platform plus evidence pack. DataMax’s inquiry page is the route for this procurement brief. Avoid asking for a “best DTS:X box”; the answer depends on signal path, OS, DRM and integration.
Require one response row per platform: SoC, OS, memory, storage, ports, DRM, DTS route, evidence attachment, deviation status and production availability. “See attached” is inadequate when the attachment combines standard, optional and custom versions.
Before sample approval, compare document to unit. Verify serial number, hardware revision, RAM/ROM, OS build, output configuration and regional firmware. A sample with higher memory, another wireless module or an extra output does not prove the mass-production configuration is equivalent.
The final decision record should state what is approved and what remains conditional. For example: “DTS:X evidence accepted for the listed HDMI path; S/PDIF behavior conditional on endpoint testing; 1G Ethernet not approved for this order; firmware changes subject to regression.” This preserves flexibility without concealing an unresolved assumption.
The traps in this category
The main divergence is between codec capability and product capability. A processor or reference design may support DTS:X while the production box omits the required route, license, firmware configuration or tuning. A quotation that names DTS:X without identifying the implementation gives procurement no auditable boundary.
Field trap
A codec label on the carton is not a test result. Specify the source format, decoder output, physical port, display or receiver configuration, firmware build and pass criteria. If those 6 fields are absent, DTS:X remains an unverified sales attribute.
The second trap is DRM and output-path confusion. Widevine and PlayReady govern protected-content delivery; HDCP protects the HDMI content path; DTS licensing governs DTS technologies. None automatically proves that S/PDIF or analogue output can carry the intended DTS:X experience.
Field trap
Do not allow “DRM ready” to replace a codec-and-interface matrix. Document content protection, decoder output and physical routing together; otherwise a qualified decoder can be paired with the wrong delivery design.
A third failure mode is treating a listed codec family as a qualified feature. “Dolby Vision/DTS” may describe broader support without identifying DTS:X, a profile, output route, license or endpoint certification. Require the vendor to replace the family label with the exact implementation. If it cannot, do not infer DTS:X from “DTS.”
A fourth failure mode treats pass-through as equivalent to decoding. One receiver may accept encoded DTS, one television may negotiate a different path, and decoded PCM can have different channel and sample-rate limits. These are separate test cases. Success on one television does not authorize claims for every endpoint.
A fifth failure mode is an approved sample that differs from the production BOM. Memory, firmware, audio components and output circuitry can change without changing the model name. Make the BOM revision part of approval and require notification for substitutions affecting decoding, licensing, interfaces, power, thermals or enclosure.
A sixth failure mode is unsupported test coverage. Ask which serial numbers were tested, on which fixtures, with which content, for how long and which exceptions occurred. A line can pass a short bench test yet fail after repeated app launches, reboot cycles or extended operation.
A seventh failure is the optional-field trap. “RJ45 1G optional,” “Dolby Vision/DTS optional” and several memory options mean the quoted unit may differ from the proposed volume build. Mark every option in the order and BOM.
Finally, output claims can exceed the datasheet. A platform marketed with “8K” must still be evaluated against its stated HDMI and decode limits. Procurement must reject any resolution claim that exceeds the production datasheet, regardless of model naming or launch material.
How the factory controls the variable
DTS:X behavior depends on component substitution, firmware integration, display-device behavior, licensing configuration and repeatable test execution. The factory evidence trail must connect those variables to the approved sample.
- Control incoming material Match SoC, memory, audio components and controlled parts to the approved BOM. Quarantine substitutions until engineering disposition is recorded.
- Inspect SMT and AOI Verify placement and soldering associated with HDMI and audio paths. Tie inspection coverage to the line risk analysis.
- Validate boot and firmware Confirm the approved image, bootloader, device tree, build identity and middleware before functional testing.
- Test display and audio Run controlled DTS:X material through the declared path. Record source, output, detected format, synchronization and restart behavior.
- Perform dark-room and burn-in checks Separate visible inspection from sustained-operation risk, with fixture, duration and serial range defined.
- Audit traceability Link serial number to BOM revision, firmware build, test result, rework record and shipment lot.
Evidence rule: “Tested” is not an acceptable process statement. The evidence pack must identify what was tested, on which firmware and hardware revision, using which source or fixture, what constituted a pass, and which record proves it.
Control begins at receiving. The incoming record should identify part number, supplier, lot and inspection result for controlled components. If the SoC, memory, audio IC or interface component changes, engineering should compare behavior with the golden sample before release to production. Procurement should ask which substitutions require notification.
SMT and AOI establish placement integrity; they do not establish signal-path performance. Audio and HDMI sections require inspection criteria matched to their failure modes, followed by functional measurement on the finished board. A supplier that cites AOI as proof of DTS:X playback has changed the test category.
The firmware gate should compare more than an OS release. Require the bootloader, kernel, device tree, vendor image, middleware, codec configuration and an immutable build identifier. If Android remains the same release but the device tree changes audio routing, the unit is not equivalent for DTS:X purposes.
Media testing must preserve source conditions. Record whether the source was a commercial content-service path, protected local asset or encoded test file; include source format, channel layout, sample rate, selected output and expected endpoint result. Repeat after an application restart and full reboot. A single successful launch can conceal a session-reset failure.
Dark-room and burn-in checks address different risks. Dark-room checks identify visible panel or enclosure defects; sustained operation exposes thermal, power, storage and stability issues. The factory should state the fixture, mode, duration, environmental conditions and disposition rules. The selected stress condition should represent the deployment risk rather than an arbitrary duration.
The audit trail must support forward and backward investigation. Forward, it links the incoming lot to the tested serial number. Backward, it identifies firmware, BOM revision, rework action and shipment lot associated with a field failure. Results without serial linkage provide a batch summary, not complete traceability.
An extreme macro photograph of a black system-on-chip package on a television mainboard, surrounded by memory chips and PCB traces, illustrates the physical concentration of platform decisions behind a small enclosure.

The photograph is illustrative, not evidence that a particular processor was fitted. Component identity must come from the controlled BOM. DataMax’s factory-quality page provides the starting point for an evidence request, while the buyer supplies the exact DTS:X source material and endpoint matrix.
Entry tier versus commitment tier
There is no universal feature split. For DTS:X procurement, the meaningful distinction is integration and evidence: a retail-style platform may suit a straightforward product, while a committed programme requires configuration control, middleware, licensing governance and repeatable test evidence.
| Procurement dimension | Entry-tier request | Commitment-tier request | Buyer evidence |
|---|---|---|---|
| Platform definition | Standard retail configuration | Frozen SoC, memory, ports and OS baseline | Configuration sheet and production BOM |
| DTS:X position | Compatibility statement | Documented decode, output and restart behavior | Content-specific test report |
| Android position | AOSP or retail Android TV build | Defined distribution, middleware and update ownership | Build identifiers and qualification records |
| DRM and HDCP | Published support | Mandatory service, version and output-path matrix | Certificates, test records and contract terms |
| Factory control | Batch-level inspection summary | Serial traceability, BOM control and change notification | Approved process plan and traceability sample |
| Customization | Stock enclosure and software | Operator boot flow, packaging, middleware and regional setup | Golden sample and deviation process |
| Release governance | Shipment-level release check | Revision-controlled release package and deviation approvals | Release note, build list and authorized changes |
| Field incident support | Standard fault-replacement flow | Serial-linked diagnosis and controlled firmware response | RMA sample, log set and corrective-action record |
| Licensing governance | Supplier-provided default configuration | Region, service and entitlement responsibility assigned | License matrix and renewal or escalation owner |
| Endpoint qualification | Representative television test | Approved receiver, amplifier and display matrix | Endpoint report and configuration revision |
The commitment tier costs engineering time and process discipline but reduces ambiguity. The entry tier moves faster when the application is retail and a controlled standard configuration is acceptable. It is a poor substitute for managed IPTV, where operator middleware, branding, regional rights and image governance are required.
This is not a claim that one tier has better hardware. An entry-tier box may decode adequately but lack the evidence needed for a managed fleet. A commitment-tier programme may start with a familiar SoC and add strict configuration control, custom imaging, endpoint testing and serialized records. Price the operational burden of ambiguity alongside hardware.
The ranking is a planning aid, not a supplier score. A general trader may coordinate acceptable standard products; a full-process OEM/ODM may own more engineering and production variables. Determine which party controls the BOM, firmware, test record and change notification.
A useful interview method is to trace one engineering change. Ask who authorizes a memory substitution, updates the image, repeats DTS playback testing, releases the shipment and stores serial-level evidence. If each answer points to a different external party, the programme has an interface-control gap. A commitment tier needs named owners and approval gates.
Choose the tier from the failure consequence. A distributor demonstration unit has a lower integration burden than a box distributed through an operator portal, remotely provisioned, middleware-updated and installed with another company’s endpoint equipment. The latter needs evidence spanning content, middleware, network, firmware, hardware and field diagnostics.
The mechanism behind the spec
DTS:X belongs to a family of audio technologies defined and licensed by the relevant specification authority. The RFQ should ask for the implementation level, source and output formats, channel configurations, sample rates, decoding behavior and licensing arrangement. The vendor should identify the component performing decoding and whether output is decoded PCM, encoded pass-through or format-dependent.
HDMI is a separate control path. Its version, EDID handling, HDCP requirement and receiver interaction determine whether an encoded or decoded stream reaches the intended display or amplifier. S/PDIF and analogue outputs create another matrix involving codec support, channel count, sample rate and implementation limits. Map each user experience to a physical port and tested endpoint.
Widevine L1 and PlayReady are protected-content systems. HDCP protects content sent over a protected digital link. DTS licensing covers DTS technologies. These mechanisms intersect but are not interchangeable. A DRM line cannot establish DTS:X playback with the operator’s application, middleware and hardware.
The implementation statement should locate each function. A decoder in the SoC, a licensed audio component, a display or an AV receiver may participate differently. Request a block-level signal description: source container and transport, audio codec, decoder, post-processing, output format and endpoint. This exposes assumptions such as an encoded stream sent to a receiver that cannot negotiate the format.
Separate the application from the hardware. The application supplies media and may invoke the platform decoder through Android media APIs. The vendor must configure the build, policies and hardware correctly. A capable platform can still fail if the application uses a restricted media path, firmware policy blocks the format or the active output route is missing.
Treat HDCP as a link condition rather than an audio-codec selection. Request protected-output behavior relevant to the deployment and the actual receiver or display. Evidence should state whether content is protected end to end, which path carries it and what equipment established the result.
S/PDIF and analogue outputs require separate matrices because each can impose different limits on encoded formats, decoded PCM, channel count and sample rate. Require the ordered port list, enabled routes and the result demonstrated on the golden sample. Testing an analogue jack does not establish HDMI behavior.
- Decoder The selected SoC or licensed component applies the required audio processing.
- Output policy Firmware selects decoded PCM, encoded pass-through or another permitted route.
- Physical link HDMI, S/PDIF or analogue interfaces carry the result within their constraints.
- Endpoint The television, receiver or amplifier must match the intended format and channel plan.
Android defines the application environment and update mechanism, not the electrical definition of DTS:X. AOSP Android provides the baseline; a commercial Android TV build, operator middleware and Google services introduce qualification and maintenance responsibilities. Assign ownership for codec configuration, licensing, recovery and updates.
For an android tv box manufacturer, the meaningful claim is an end-to-end path: protected source or licensed file, approved Android build, decoder component, firmware route, physical output and endpoint behavior. Each arrow needs an owner and a test. The AOSP versus Google Android TV guide helps decide the OS contract, while the HDR10+ Android TV box guide illustrates why display-path requirements belong in the same evidence chain.
A change to the mechanism triggers review of the complete path. An Android image update can alter media policy; an HDMI component change can alter negotiation; an audio component change can alter decoded output. Identify which layers changed and which regression tests must be repeated.
Separate vendor and buyer responsibilities. The android tv box manufacturer controls the SoC, firmware, outputs and internal fixtures. The buyer or integrator controls the television, amplifier, sound bar, cabling and installed-room configuration. Request evidence for the first group and perform acceptance tests for the second.
Which DataMax models actually sit here
The models below are screening platforms, not automatic DTS:X approvals. The supplied facts identify codec, DRM and fit, but do not establish a complete DTS:X implementation, licensing package or endpoint certification for every configuration. Confirm those items against the production datasheet and approved golden sample.

The same figures, in searchable form:
| Supplier type | Editorial score |
|---|---|
| General trader | 28 |
| Sourcing agent | 44 |
| Single-line factory | 72 |
| Full-process OEM/ODM | 89 |
| Model | SoC and OS | Memory | DRM and codec facts | Interface facts |
|---|---|---|---|---|
| DM21P | Amlogic S905Y4, quad Cortex-A35; AOSP Android 11 | 2GB / 8GB; 4GB and 16/32/64GB optional | Widevine L1 / PlayReady / HDCP 2.2 optional; AV1 [email protected], VP9/H.265 4K@60, H.264 4K@30 | HDMI 2.0b out x1; USB2.0 x2; TF; S/PDIF; 3.5mm AV; RJ45 100M; Wi-Fi6 2x2 + BT5.4; DC 5V/2A |
| DM21S | Amlogic S905Y5, quad Cortex-A55; AOSP Android 14 | 2GB / 16GB; 2/4/8GB and 16/32/64GB optional | Widevine L1 / PlayReady optional; Dolby Vision/DTS; AV1 / H.265 [email protected] 4K@60 | HDMI 2.0b out; S/PDIF; AV; USB2.0 x2; TF; RJ45 100M, 1G optional; Wi-Fi6 2x2 + BT5.4 |
| DM21T | Amlogic S905X5, quad Cortex-A510 (ARMv9); AOSP Android 14 | 4GB / 64GB | Widevine L1 / PlayReady optional; H.266/VVC [email protected] 4K@120, AV1/VP9/H.265 4K@120, AVS3 4K@120, H.264 4K@60; inline AI-SR | HDMI 2.0b out, no HDMI in; USB2.0 x1 + USB3.0 x1; TF; S/PDIF; AV; RJ45 100M, 1G opt; Wi-Fi6 + BT5.4 |
| DM22Q | Amlogic S905X5M, quad Cortex-A55 up to 2.5GHz; AOSP Android 14 | 4GB / 64GB; 2/4/8GB and 16/32/64GB optional | Widevine L1 / PlayReady optional; Dolby Vision/DTS; AV1/H.265 L5.1 4K@60; inline AI-SR | HDMI 2.0b out; USB2.0 x2; TF; S/PDIF; AV; RJ45 100M, 1G opt; Wi-Fi6 2x2 + BT5.4 |
DM21P is the operator-middleware direction in the supplied facts. DM21S is positioned for 4K IPTV and OTT white-label use; its listed Dolby Vision/DTS support makes it a more natural DTS-led starting point, subject to DTS:X implementation details. DM21T and DM22Q are higher-tier decode directions, but their facts must not be converted into an unverified DTS:X claim.
DM21P lists AOSP Android 11, S/PDIF and 3.5mm AV. DM21S lists AOSP Android 14, Dolby Vision/DTS, S/PDIF and AV. These facts make DM21S the natural starting point when DTS is the leading procurement discriminator. It remains conditional on the production datasheet, license route and controlled sample.
DM21T is described for premium UHD or cloud-gaming use. Its listed decodes reach 4K@120 for several formats, and its interfaces include HDMI 2.0b out with no HDMI in, one USB2.0 and one USB3.0 port. DM22Q is gaming-oriented and lists Dolby Vision/DTS with HDMI 2.0b out, 2 USB2.0 ports, S/PDIF and AV. Neither listing alone specifies DTS:X.
The processor and memory lines control the shortlist but do not infer audio behavior. Amlogic S905Y4, S905Y5, S905X5 and S905X5M must remain distinct in the procurement record. A substitution requires an updated BOM, codec evidence and golden-sample comparison.
OS age affects integration effort without determining DTS:X support. DM21P lists AOSP Android 11; DM21S, DM21T and DM22Q list AOSP Android 14. Managed deployments must separately assess middleware compatibility, image ownership, security maintenance and application compatibility.
Do not infer missing ports, licenses or optional-feature status. The supplied facts list optional DRM, optional RJ45 1G and optional memory variants for several models. A quotation must state which option is ordered, and a factory document must confirm it. Any unresolved DTS:X item remains open until the production datasheet and sample test close it.
Deployment scenarios and the spec each needs
The deployment determines which evidence matters. An operator needs middleware and service integration; an integrator needs physical interfaces and endpoint behavior; a venue needs repeatable playback and fleet management. One “DTS:X supported” line cannot answer all 3 use cases.
| Situation | Primary requirement | Model direction | Acceptance focus |
|---|---|---|---|
| • IPTV operator with managed middleware | • Stable AOSP integration, service security and controlled imaging | • DM21P is the operator-middleware fit | • Middleware boot, rights path, reboot recovery, device management and field failure reporting |
| • OTT or IPTV white-label programme | • AOSP Android 14 baseline, HDMI plus S/PDIF/AV and listed DTS support | • DM21S is the closest listed starting point | • DTS implementation, decoded and passthrough routes, Wi-Fi6 2x2 + BT5.4, and branding changes |
| • Premium UHD or cloud-gaming channel | • Higher decode capability and high-speed USB | • DM21T | • 4K@120 decoding claims, HDMI 2.0b limit, thermal behavior and endpoint compatibility |
| • Gaming-oriented retail programme | • 4K@60 AV1/H.265 direction and listed Dolby Vision/DTS support | • DM22Q | • Gaming output behavior, firmware stability, input latency where contracted, and DTS endpoint testing |
| • Hotel, hospitality or corporate venue | • Predictable HDMI output, central deployment and service recovery | • Select from the matrix after endpoint survey | • 100M/1G network choice, S/PDIF or AV need, operator-management hooks and fleet imaging |
For an operator, request the middleware build process, production image identifiers, update ownership and failure-recovery evidence. The integrator should document HDMI receivers, amplifiers, sound bars and displays, including EDID behavior and codec negotiation. A venue must test the complete endpoint chain in situ; a passing box test does not establish that every display accepts the intended route.
An operator deployment needs a fleet acceptance method. Define how a line sample is selected, how middleware versions are recorded, how service credentials and rights are provisioned, and how failures return diagnostics. A laboratory pass without the operator portal or production entitlement may not represent field behavior.
A retail programme uses packaging and online claims as control points. If the carton says Dolby Vision/DTS, confirm that the exact model, memory option and regional firmware carry the corresponding implementation. A white-label programme should place artwork, boot flow, support application, network settings and privacy disclosures under the same revision control as the hardware.
An AV integrator should perform the endpoint matrix after the factory sample passes. Record endpoint model, current firmware, HDMI cable path, selected audio mode and result. Repeat after a cold boot and input switch. If local media and streaming are both required, test both sources because codec availability can differ between application paths.
A venue deployment must include recovery behavior. Confirm what appears after network loss, application failure, source switching and power restoration. For hospitality or corporate use, evaluate the selected 100M or optional 1G Ethernet configuration, available S/PDIF or AV route and fleet-imaging method against the installed environment.
The final release should map deployment, hardware revision, firmware, middleware, content source, endpoint, test method and disposition. That matrix turns android tv box manufacturer selection into an auditable release decision. DataMax can support platform review, while the buyer remains responsible for confirming DTS:X licensing, endpoint behavior and the production datasheet. The operator-tier Android TV box solution helps define the managed-IPTV route; request a controlled review through sample ordering.
Further reading
- Guide android tv box manufacturer
- Rockchip Android TV boxes
- Edge computing boxes
- 4K 60fps Android TV box guide
- Rockchip Android TV box guide
- DataMax DM21P specifications and fit
- DataMax DM21S specifications and fit
FAQ
Is “DTS:X ready” sufficient for an RFQ?
No. It remains a marketing-level claim until the vendor identifies the implementation, supported formats and sample rates, output route, firmware behavior, licensing arrangement and test evidence. Procurement should require a configuration-specific report and golden sample. A chipset reference alone does not prove that DTS:X survives the complete product path.
Should the box decode DTS:X or pass it through?
The requirement depends on the endpoint. Some television and AV chains are designed for encoded pass-through, while other installations require decoded PCM output. The RFQ must name the desired route and test endpoint. Ask whether the application, receiver and box negotiate formats or remain inside a controlled chain.
Does Widevine L1 prove DTS:X readiness?
No. Widevine L1 addresses protected-content delivery, not DTS codec licensing, decoder configuration or physical output behavior. PlayReady and HDCP address distinct parts of the content path. Each mechanism needs separate evidence, and the combined end-to-end result still requires playback testing.
What should be frozen before production approval?
Freeze the SoC, memory and storage configuration, ports, OS release, firmware image, middleware version, packaging, accessories and applicable supplier substitutions. Record the approved golden sample and serial number. Any controlled-item change should trigger review and, where material, a fresh DTS and endpoint test.
How should an android tv box manufacturer prove repeatability?
Request traceability from component inspection through SMT and AOI, firmware validation, display and audio testing, dark-room or burn-in checks, and final audit. Evidence must identify the method, accepted limits, hardware and software revisions, serial or lot coverage and disposition rules. Generic claims such as “full inspection” do not establish repeatability.
Can a DTS:X label be used in marketing?
Only if the claim is supported for the exact production configuration, region and intended endpoint. Align packaging, web copy, model naming and datasheet with approved evidence. A marketing label must not exceed the platform’s actual HDMI, decode and licensing limitations.