Before the terminology: the decision
The widespread belief is that HDR10+ and Dolby Vision are interchangeable display labels, or that support can be inferred from “4K,” HDMI, or a DRM statement. That is wrong. hdr10 plus and dolby vision where licensing is heading describes 2 different control systems: HDR10+ is an open, royalty-free dynamic-HDR metadata approach, while Dolby Vision is a licensed ecosystem with defined device, content, decoder, and certification obligations.
For procurement, the first decision is whether the program actually needs dynamic HDR metadata. If the objective is operator middleware, IPTV, OTT, or gaming at 4K without a Dolby Vision program, Widevine L1 plus HDCP 2.2 may be the relevant baseline, subject to the production configuration. Dolby Vision should enter the specification only when the service plan includes Dolby Vision content, licensed app or middleware support, compatible displays, and the required agreements. HDR10+ follows a different path: the product must implement the applicable metadata processing and display path, while licensing is generally not tied to a device royalty. Exact implementation and certification obligations must be confirmed against the current HDR10+ adopter requirements and Dolby licensing terms.
A second decision concerns evidence. “Supports HDR10+,” “Dolby Vision,” “Dolby Vision certified,” and “Dolby Vision capable” are not interchangeable claims. The quotation should identify the tested standard, the software branch, the display mode, the HDMI configuration, the sample state, and the evidence owner. If DataMax is the manufacturing partner, request the production datasheet and conformity package alongside the commercial quotation. The shortlist begins with the DM21P for operator middleware and the DM21S for Android TV IPTV/OTT programs; a Dolby Vision claim must not be inferred unless the selected production configuration documents it.
The decision can be stated in 1 line: specify the licensed content path, select the production configuration with documentary support, and validate the complete source-to-display chain. A decoder specification alone cannot close that gap. This remains the central issue in hdr10 plus and dolby vision where licensing is heading for high-volume hardware programs.
Verification you can ask for on paper
The factory’s role is to turn a licensing or feature claim into a repeatable production state. That requires an evidence trail linking the commercial model, hardware revision, SoC, firmware, display path, test configuration, and responsible licence or certificate holder.
A workable process has 6 gates. SMT confirms that the correct components and board revision were fitted; AOI and functional inspection catch assembly defects; software validation confirms the advertised feature path; display testing verifies the negotiated mode; ageing separates early failures from stable assemblies; and the document audit confirms that the evidence belongs to the shipped configuration. The exact factory test sequence and sample count must be confirmed against the quality plan and production datasheet.
- Configuration baseline Record the model, SoC, RAM/ROM option, OS branch, firmware identifier, display output, accessories, and intended customer use.
- Incoming and SMT verification Tie component inspection and board-level checks to the approved BOM and work instruction; quarantine substitutions that lack traceability.
- AOI and electrical inspection Apply the factory’s documented inspection coverage, retain inspection records, and route exceptions through engineering disposition.
- Software and licence validation Verify the relevant feature path, service environment, package identity, update mechanism, and operator configuration rather than relying on a wallpaper or menu label.
- Dark-room display validation Record the source signal, resolution, refresh rate, colour format, HDR metadata, sink capabilities, and observed output for the exact reference unit.
- Ageing, audit, and release Complete the approved ageing procedure, reconcile the final BOM and software build, then archive inspection records, test logs, approvals, and certificates.
The paper trail should also identify who may change a compliant configuration. A hardware engineer, middleware integrator, and content operator can each alter the observed result: replacing a display adapter, enabling a different player, loading another certificate set, or applying an OS update may change the metadata path. The configuration record therefore needs an approval owner, an engineering change rule, and a retest trigger. Without those fields, a compliant factory sample can become an unrepresentative production unit.
A second audit layer is sample identity. The reference unit should carry a serial number or controlled sample identifier linked to the test log, firmware hash, hardware revision, and sink used in the dark room. The record should state whether the tested image was the retail image, an engineering build, or a customer-specific image. It should also identify the source device, source file or stream profile, display model, firmware version, HDMI mode, colour format, and measured outcome. “HDR passed” cannot support a release decision without those variables.
Paper-test request: Ask for the exact model and hardware revision, firmware build, test protocol, display and sink configuration, result summary, certificate identifier where applicable, and the document’s validity period. A generic “HDR capable” report is not evidence for a specific Dolby Vision or HDR10+ production claim.
Two audit questions expose weak evidence. First, can the supplier identify the public registry entry for a claimed certificate rather than attach a screenshot without verification? Second, can it show that the same display, decoder, firmware, and licensing configuration used in the audit remain available for production? For factory capability and documentation, DataMax’s factory-quality information and certification resources are appropriate starting points, but the buyer must verify the underlying documents against the selected SKU.
Entry tier versus commitment tier
The practical choice is not “low-cost box” versus “premium box.” It is an entry tier that establishes a conventional 4K playback path versus a commitment tier that embeds a dynamic-HDR program with more dependencies. The bill of differences includes firmware engineering, content agreements, sink qualification, test equipment, documentation, and operational ownership.
| Decision area | Entry tier | Commitment tier | RFQ consequence |
|---|---|---|---|
| Primary HDR objective | Conventional 4K HDR service path | Dolby Vision or HDR10+ program-specific path | State the required HDR system, not merely “HDR” |
| Content side | Service uses static HDR or SDR fallback | Content carries approved dynamic metadata and delivery profile | Identify the licensor, catalogue, region, and playback tier |
| Display validation | Baseline 4K and HDR output validation | Mode-by-mode validation with reference displays | Name sink models and required modes |
| Software ownership | Baseline firmware plus customer configuration | Feature integration, regression work, and version discipline | Assign firmware, app, middleware, and licence owners |
| Evidence | General 4K and DRM test records | Standard-specific reports or certificate evidence | Reject generic reports as substitutes |
| Operational exposure | Mainly device, app, and service integration | Device, content, display, network, and licensing dependencies | Include compatibility matrices in acceptance |
The entry tier remains appropriate when the service catalogue has no approved dynamic-HDR content, the television estate is unmanaged, or fallback to SDR is explicitly acceptable. In that case, the buyer should define ordinary 4K playback, protected-content access, output protection, and recovery rather than creating an open-ended feature request. An operator can also use an entry-tier hardware platform while planning a later dynamic-HDR variant, provided the quote does not imply that the current production image has already passed Dolby Vision or HDR10+ acceptance.
The commitment tier adds named work packages. Engineering must maintain a standard-specific decoder and metadata path; licensing must identify the rights holder; certification or compliance must define evidence; product management must maintain a supported display matrix; and operations must have a fallback policy when the preferred television or content profile is unavailable. These are separate deliverables with separate acceptance criteria. A supplier’s statement that Dolby Vision is “supported” does not establish any of them.
| Work package | Entry tier treatment | Commitment tier treatment |
|---|---|---|
| Firmware path | Baseline 4K player and ordinary HDR output | Named metadata-preserving path with version control |
| Sink matrix | Representative installation test | Per-model mode and fallback matrix |
| Licence administration | No program dependency | Named holder, scope, renewal, and audit route |
| Release regression | General smoke test after build changes | Standard-specific regression and evidence retention |
| Support policy | Replace or reimage on defect | Coordinated app, firmware, sink, and rights escalation |
The chart is a planning aid, not a certification result. A high complexity rank indicates more interfaces to verify, not a guaranteed field failure rate. The procurement question remains whether the program’s revenue, catalogue, and display estate justify those controls. A buyer can preserve that distinction by requiring the entry tier to name the protected-content baseline and the commitment tier to name the licence holder, certification route, metadata profile, sink matrix, and evidence owner.
The mechanism behind the spec
HDR10+ extends the HDR10 ecosystem with dynamic metadata. The display receives scene- or frame-level information that allows it to map HDR content to its own capabilities rather than applying 1 fixed conversion for the entire program. In an implementation, the metadata must survive decoding, composition, scaling, output, and the display interface. That means an HDMI 2.0b output alone does not prove correct HDR10+ behaviour.
The mechanism depends on an agreed implementation profile. The source encodes or supplies HDR10+ metadata; the playback and graphics path preserves it; the sink interprets it; and the test method confirms the required tone-mapping behaviour. The current HDR10+ specification, adopter agreement, test requirements, and licensing position must be checked against the current program documents. The buyer should therefore ask which HDR10+ version or profile is implemented, which metadata types are supported, whether all operator applications preserve the path, and which reference sink was used for acceptance.
Metadata can be lost before the cable reaches the television. A decoder may produce HDR frames without the dynamic metadata, an application may create its own composition surface, Android’s display pipeline may select another output mode, and a scaler may transform the signal without retaining the relevant metadata. Consequently, a useful RFQ asks where metadata is inspected. The candidate answers are the protected decoder, the compositor or player, the Android display service, the HDMI transmitter, and the sink. The test method should identify the point at which the information was observed.
Dolby Vision uses a different licensed architecture. It includes proprietary processing and display-mapping technology, defined licence levels for device manufacturers and content providers, certification obligations, and restrictions around production, distribution, and display of Dolby Vision content. The direction of travel is not simply “more devices”; it is tighter control over implementations, interoperable delivery, versioned content, and verification across device, software, and display.
HDCP is a separate link. A display path may support HDR signalling while protected content cannot pass without the required output protection. Widevine L1 and PlayReady govern protected-content access, not dynamic-HDR metadata. Buyers should keep these control layers separate in the RFQ:
| Layer | Question answered | Required evidence |
|---|---|---|
| DRM | Can protected content be accessed? | Widevine or PlayReady level for the production build |
| Output protection | Can protected video pass to the sink? | HDCP configuration and display-path result |
| HDR metadata | Is dynamic scene information preserved? | HDR10+ profile result or Dolby Vision test evidence |
| Display mapping | How is HDR adapted to the panel? | Sink, firmware, source, and mode under test |
| Content rights | May the service distribute the content? | Applicable content agreement and program conditions |
Architecturally, the buyer should trace 5 hops: protected source to decoder, decoder to compositor or player, compositor to output service, output service to HDMI, and HDMI to the licensed or capable sink. A failure at any hop can masquerade as an HDR licence issue. This distinction prevents a program from “fixing” licensing when the real defect is metadata loss, unsupported display mode, or a 4K/60 bandwidth limitation.
The platform decision must also respect that different hardware paths carry different implementation obligations. A box with a 4K@60 decoder does not automatically support every 4K@120 workflow. Conversely, a decoder can support a high frame rate while still lacking the metadata, output protection, or licence state required by the service. These distinctions explain why hdr10 plus and dolby vision where licensing is heading cannot be answered with a single “HDR-ready” checkbox.
The platform shortlist with datasheet values
DataMax’s TV box line provides different SoC, OS, memory, decode, and interface baselines. The values below are transcribed from the supplied product facts; optional configurations and any HDR feature not stated in those facts must be confirmed against the production datasheet. In particular, the Dolby Vision/DTS text for DM21S and DM22Q is reproduced as a supplied field, but the exact Dolby Vision level and licensing status still require documentary confirmation for the ordered configuration.

The same figures, in searchable form:
| Evidence option | Editorial score |
|---|---|
| Supplier claim | 15/100 |
| Generic test report | 42/100 |
| Standard-specific report | 70/100 |
| Certificate with public registry lookup | 94/100 |
Source: DataMax editorial team, qualitative planning scale (0-100), not audited or measured data.
The evidence hierarchy does not replace engineering verification. A registry-backed certificate can establish an identity or formal status, while the standard-specific report establishes what was tested. The supplier claim remains useful for identifying a proposed route but cannot establish production conformity. Buyers should request both the formal evidence and the configuration record showing how the evidence applies to the ordered hardware and firmware.
| Model | Program fit | SoC and OS | Memory | Decode | DRM/HDR facts | Ports and connectivity |
|---|---|---|---|---|---|---|
| DM21P | 4K IPTV / operator middleware set-top box | Amlogic S905Y4, quad Cortex-A35; AOSP Android 11 | 2GB / 8GB; 4GB; 16/32/64GB optional | AV1 [email protected]; VP9/H.265 4K@60; H.264 4K@30 | Widevine L1 / PlayReady / HDCP 2.2 optional | 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 | 4K Android TV box for IPTV/OTT white-label | Amlogic S905Y5, quad Cortex-A55; AOSP Android 14 | 2GB / 16GB; 2/4/8GB; 16/32/64GB optional | AV1 / H.265 [email protected] 4K@60 | Widevine L1 / PlayReady optional; Dolby Vision/DTS | HDMI 2.0b out; S/PDIF; AV; USB2.0 x2; TF; RJ45 100M; 1G optional; Wi-Fi6 2x2 + BT5.4 |
| DM21T | Premium UHD / cloud-gaming box | Amlogic S905X5, quad Cortex-A510 (ARMv9); AOSP Android 14 | 4GB / 64GB; family options | H.266/VVC [email protected] 4K@120; AV1/VP9/H.265 4K@120; AVS3 4K@120; H.264 4K@60; inline AI-SR | Widevine L1 / PlayReady optional | 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 | Gaming-oriented Android TV box | Amlogic S905X5M, quad Cortex-A55 up to 2.5GHz; AOSP Android 14 | 4GB / 64GB; 2/4/8GB; 16/32/64GB optional | AV1/H.265 L5.1 4K@60; inline AI-SR, no NPU TOPS stated | Widevine L1 / PlayReady optional; Dolby Vision/DTS | HDMI 2.0b out; USB2.0 x2; TF; S/PDIF; AV; RJ45 100M; 1G opt; Wi-Fi6 2x2 + BT5.4 |
DM21P is the conservative operator baseline in this set, with Android 11, 2GB / 8GB, and 100M Ethernet. DM21S moves white-label IPTV/OTT work to Android 14 and includes the supplied Dolby Vision/DTS field. DM21T differentiates through decode capability, including H.266/VVC [email protected] 4K@120 and AV1/VP9/H.265 4K@120, not through an unstated HDR licence claim. DM22Q combines Android 14, 4GB / 64GB, and the supplied Dolby Vision/DTS field with 4K@60 AV1/H.265 decoding. Neither DM21T nor DM22Q supports an 8K-output claim; their stated maximum output/decode is 4K.
A product shortlist should remain separated from a program approval. The platform table identifies candidate baselines, not dynamic-HDR certification. For example, the presence of “Dolby Vision/DTS” beside DM21S and DM22Q narrows the enquiry, but it does not identify the Dolby Vision level, firmware support, content profile, certificate, or licence holder. Those items remain a datasheet and evidence question. This separation is particularly important for hdr10 plus and dolby vision where licensing is heading because a hardware line can evolve faster than its program evidence.
Where this matters in a deployment
Dynamic-HDR requirements emerge at the intersection of service, hardware, display, room, and operations. An operator may start with a national IPTV contract, but compatibility varies across operator middleware, set-top hardware, television models, and retail installation standards. An integrator may control the display and source device but not the content licence. A hospitality operator may control every screen in the room but still depend on a third-party IPTV platform and receiver hardware.
The following photograph shows the kind of environment where the box is rarely the visible object: the television and service experience dominate, while the compact receiver sits behind the panel and the guest never sees its HDMI, Ethernet, or thermal configuration.

| Situation | Controlling requirement | Model direction | Field check |
|---|---|---|---|
| Operator IPTV rollout | Middleware, 100M Ethernet, DRM, managed deployment | DM21P baseline; compare Android 14 options if the operator requires it | Verify operator app, network, DRM, guide data, and update path |
| OTT white-label program | Android TV integration, branded UI, service continuity | DM21S | Test the actual app, account, playback, and optional Dolby Vision configuration |
| Premium cloud gaming | 4K@120 decode, latency, storage, thermal stability | DM21T | Measure game service, output mode, sustained thermal behaviour, and HDR sink support |
| Gaming-oriented retail product | Android TV UX, 4K@60 media, memory, operator distribution | DM22Q | Confirm licensed feature status and peripheral compatibility |
| Hotel room deployment | Remote management, stable service recovery, compact enclosure, display compatibility | Select by operator platform and television estate, not by feature label alone | Pilot at 4K60, verify account expiry handling, HDMI path, and support process |
| Digital signage | Continuous playback, app lifecycle, storage, remote recovery | Confirm against the production datasheet; no listed model should be selected from an unstated assumption | Run the real CMS, app, playlist, and recovery scenario |
An operator deployment adds fleet scale to the evidence problem. 1 failed television mode can affect many rooms or subscribers, yet the visible symptom may be inconsistent brightness rather than an obvious decoder error. The acceptance program should therefore sample every supported television family, verify the negotiated source mode, record the metadata path, and establish a diagnostic procedure that separates network, app, display, and licence issues. A single successful demonstration unit cannot represent an installed fleet.
Integrators face a different boundary. They can specify the television and cable, but they may not control the app, operator image, protected-content licence, or streaming catalogue. Their responsibility should be bounded in the statement of work: physical installation, source switching, EDID behaviour, network quality, display-side configuration, and an agreed fallback. If an upstream party must deliver Dolby Vision content, that dependency must be stated as an interface rather than implied by the television’s feature label.
For a venue, the operating period matters. A hospitality receiver may remain connected for many hours between staff interventions, while a digital-signage player may run a fixed playlist with little interaction. Thermal behaviour, app focus, wake policy, network reconnection, and account expiry can therefore expose faults that a short demonstration misses. The acceptance pilot should run through at least 1 normal operating cycle, including an update, a network interruption, a source change, and recovery to the intended application.
For the hospitality scene, the acceptance test should use the actual television model, room network path, operator middleware, and night-time ambient conditions. A laboratory demonstration under ideal conditions does not establish behaviour in a long-running room. The same rule applies to retail: installed displays, consumer expectations, and remote firmware updates can expose integration faults that a golden unit conceals.
The HDR10+ Android TV box guide helps define which implementation questions to ask, while the Dolby Vision Android TV box guide helps separate product support from content and display obligations.
The selection sequence that removes rework
Procurement should proceed from program obligations to evidence, then to hardware, then to validation. Starting with a chipset creates rework because the fastest decoder does not resolve missing content rights, unsupported sink modes, or an unverified firmware path.
- Define the service State the source, applications, protected-content system, content delivery mechanism, region, operator middleware, and expected display modes. Name any Dolby Vision content or HDR10+ source profile in the requirement.
- Fix the contractual position Identify the Dolby licence level and responsible holder where Dolby Vision is required. For HDR10+ confirm the current adopter, implementation-profile, and test obligations. Do not ask the hardware vendor to assume a content licence.
- Choose the platform Match OS, memory, decode, interface, and update requirements to the application. Select DM21P, DM21S, DM21T, or DM22Q only from the supplied datasheet fields and the confirmed production configuration.
- Define the display environment List television models, maximum HDMI mode, supported HDR systems, firmware versions, and any operator-controlled display policy.
- Freeze the evidence package Specify hardware revision, software build, standard-specific test method, sample identity, certificate or report identifier, sink used, and validity period.
- Approve the pilot Test installation, playback, source switching, network recovery, account expiry, service update, thermal behaviour, and the fallback path before volume deployment.
The sequence can be shortened for an established operator that already has an approved middleware image and television qualification. In that case, DataMax should receive the approved package and reproduce the same controlled conditions: identical SoC and memory tier, specified OS and firmware build, named accessories, and the operator’s reference sink. Any difference must be treated as a new configuration rather than silently covered by the original report.
The RFQ should paste specific lines rather than request “HDR support.” A usable clause is: “The selected DataMax model must support the operator application and protected-content system identified below. If Dolby Vision is required, identify the licence level, certification path, implementation version, supported profile, and evidence owner. If HDR10+ is required, identify the current implementation profile, metadata support, preservation path, sink test method, and evidence package. State model, hardware revision, RAM/ROM, OS, firmware build, HDMI configuration, display models, source modes, sample count, test protocol, and acceptance criteria.”
The RFQ’s first message should contain the target DataMax model, operator or OTT application, source and display mode matrix, Dolby Vision or HDR10+ requirement, required evidence, timeline, and quantity context. Submit that brief through the DataMax inquiry channel, or use the sample-order route when the next decision requires a representative unit rather than a paper claim.
A final control point is the acceptance sign-off. The program owner should sign the service and content assumptions; the device engineering owner should sign the platform and firmware identity; the display owner should sign the sink matrix; and the operations owner should sign fallback and recovery. This prevents 1 department from accepting a feature that another department assumed it would own. It also creates a clear answer when an issue later appears in the field: the buyer can identify which approved interface changed.
Failure modes that reach the field
Most field failures arise from gaps between a quotation, a laboratory configuration, and the deployed system. The licence can be valid while the app discards metadata; the decoder can support 4K while the television negotiates another mode; the certificate can match a chipset while the production firmware differs. Each quotation must bind its claim to an identifiable configuration.
Field trap
“4K HDR” substituted for a named standard. If the requirement does not identify HDR10+ or Dolby Vision, expected metadata, profile, sink modes, and licence evidence, acceptance can pass with the wrong implementation. The cost is not only a screen-level mismatch: catalogue packaging, app logic, certification evidence, and replacement analysis may all have to be revisited.
Field trap
Software identity drift. A factory-approved display test on 1 firmware build does not validate a later operator image. Pin the application version, firmware identifier, device tree, boot image, certificate set, and configuration profile; require regression evidence after any component or middleware change.
Another failure is configuration substitution inside an otherwise correct model. A quotation may specify 1 RAM/ROM combination, Ethernet option, power supply, or regional image, while the factory quotation or sales offer is interpreted as permission to substitute equivalent parts. Memory configuration can change operator certification boundaries, Ethernet options can alter network assumptions, and a different image can omit a licence or metadata path. The purchase order should therefore enumerate orderable variants rather than relying on a family shorthand.
Quotation language also diverges around “optional.” “Optional Dolby Vision,” “optional HDCP 2.2,” and “optional 1G” do not describe the delivered configuration by themselves. The buyer needs the selected option, its documentary status, and the difference between engineering availability and production availability. A feature available to an engineering sample is not automatically available in every production shipment. This is the practical meaning of hdr10 plus and dolby vision where licensing is heading for a purchase order: the feature must become a controlled configuration line.
Other common divergences include HDMI cable or sink limitations, TV firmware restrictions, an application that bypasses the protected decoder, content delivered without the expected metadata, and a device variant with different RAM/ROM or Ethernet options. A quotation that says “optional” must identify what is optional, which configuration is being supplied, and which capability is actually covered.
The commercial consequence of uncertainty also multiplies through logistics. A non-conforming batch may need sorting, relabelling, firmware remediation, display replacement, or return shipment. A service operator may defer launch or restrict features to selected television models. A hotel or venue operator may lose remote-management visibility if the fallback path bypasses the intended application.
For these reasons, DataMax’s compliance resources should be treated as an evidence gateway, not as a substitute for program approval. Each delivery needs a signed configuration record, relevant test records, applicable certificate or licence evidence, and a clear owner for the customer-side content and display requirements. For custom program integration, custom development can define the engineering boundary; the manufacturer overview provides context for evaluating DataMax as the production partner.
Further reading
- TV box vendor selection checklist
- AOSP vs GMS solution notes
- Telecom and pay-TV operator solutions
- Certifications and test evidence
- Amlogic Android TV boxes
- DataMax DM21P specifications and fit
- DataMax DM21S specifications and fit
FAQ
Is HDR10+ subject to the same device licensing as Dolby Vision?
No. HDR10+ is generally positioned as an open, royalty-free dynamic-HDR metadata approach, while Dolby Vision uses a licensed ecosystem with device, content, software, and certification obligations. A buyer must still verify the current HDR10+ adopter requirements and Dolby agreement terms for the intended program rather than assuming either technology is licence-free in every operational respect.
Does Widevine L1 prove Dolby Vision support?
No. Widevine L1 is a protected-content DRM level. Dolby Vision concerns dynamic-HDR metadata, processing, display mapping, content rights, and certification. A product may support Widevine L1 without Dolby Vision, and Dolby Vision support still requires its own configuration and evidence.
Which DataMax model should an OTT operator choose for Dolby Vision?
The supplied facts list DM21S and DM22Q with a Dolby Vision/DTS field, but the exact Dolby Vision level, licence status, and ordered configuration must be confirmed against the production datasheet. DM21P lists Widevine L1, PlayReady, and optional HDCP 2.2, not Dolby Vision.
Does HDMI 2.0b guarantee HDR10+ or Dolby Vision operation?
No. The interface identifies an output capability, not a complete dynamic-HDR implementation. The decoder, application, firmware, metadata path, negotiated mode, sink, source content, and applicable licence or certification evidence must all be verified.
What evidence should be attached to a production quotation?
Request the exact model and hardware revision, firmware build, standard-specific test protocol, tested source and sink modes, sample identity, result summary, certificate or registry identifier where applicable, and evidence validity period. A generic test report or unsupported supplier claim should not replace the program-specific package.
Can a product be marketed as 8K because the box is advertised that way?
No. For DM21T and DM22Q, the supplied datasheet caps output and decode at 4K. The RFQ, specification, artwork, and acceptance evidence must use the documented 4K limits. Any proposed 8K claim requires new, verified evidence rather than marketing language.