HDR & display validation for product and firmware releases

For display development, player teams and quality assurance

Give your development team reproducible findings before a product or firmware release. We investigate the agreed behaviour of displays, players and HDR signal paths, define test conditions and record deviations. The results support specific corrections and comparison of the relevant versions after changes.

Two displays showing the same still-life scene
Compare picture reproduction under the same conditions.

Investigate and reproduce picture faults

Give developers a test case they can repeat: source signal, device version, settings and observed behaviour are recorded together. We help separate possible causes when content, player and display interact. After a correction, you can compare the relevant result under the same agreed conditions.

Create reproducible fault cases

Your team receives an example with the system version, source signal and settings recorded. The observed finding can then be checked again deliberately.

Investigate possible causes separately

We examine content, player, metadata and display according to the agreed task. You receive findings that help narrow down the cause.

Retest corrections under the same conditions

Compare the state before and after a change. Relevant tests are repeated under comparable conditions and the results are identified.

Test plans, version comparisons and retesting

Product release decisions need clear criteria. With your team, we define the properties and use cases to investigate, the relevant hardware and software versions, and which results count as deviations. Findings apply to the agreed test scope.

Investigate HDR and picture behaviour

Depending on the setup, tasks can include luminance and EOTF, colour deviations, clipping, banding or tone-mapping behaviour. Test signals, image surroundings and timing are defined for the investigation.

Compare firmware and configurations

We compare agreed versions or settings under the same conditions. Findings include the system version, signal source, settings and a reproducible test case.

Retest after corrections

After a change, we repeat the relevant tests and record which findings have been resolved or remain. Recurring checks can be agreed for subsequent releases.

From FF Pictures’ practice

Investigating HDR metadata

We investigate how HDR10+ metadata affects playback and how HDR displays respond to changing images over time. For your product or firmware release, we define the test signals, playback conditions and findings to be recorded.

Explore the HDR10+ metadata test

Typical check: detail disappears after an update

Example investigation.

  1. Starting point

    After a firmware change, bright clouds look flat in the same HDR scene.

  2. Investigation

    We compare the same clip, signal path and device mode. Metadata, tone mapping and signal levels are investigated specifically; a hypothesis is not yet a finding.

  3. Decision

    The development team receives a traceable comparison and explicit retest conditions for the next change.

Deliverables for your project

What you receive

These deliverables are tailored to your task before work starts:

  • Agreed test plan covering devices, versions, conditions and assessment criteria.
  • Measurement data or documented visual findings for the agreed tasks.
  • Reproducible fault cases and a prioritised findings list for your development team.
  • Result comparison and retesting after agreed corrections.

Define the assessment task

Firmware, players and content can all affect the image. We record hardware state, software versions, signal path, test material and expected behaviour. A traceable baseline makes later comparisons useful.

The release decision remains yours

The assessment supports development and quality assurance. It is not official certification. You define the requirements for your product release and who approves it.

Choose a starting point

  1. Investigate a fault case

    We define the test question and system version, then examine the conditions under which the fault can be reproduced. You receive documented observations and next checks.

  2. Compare versions

    We agree a limited test plan and compare relevant firmware or configurations under the same conditions. You receive traceable differences and findings.

  3. Use repeat tests as a team

    We document the conditions, test material and retest steps for your team. This helps verify corrections; the release decision remains yours.

We agree the scope and deliverables for your task. You can start with a single check.

Questions before commissioning

Can you assess a specific issue rather than an entire product?

Yes. We can focus the assessment on a specific display behaviour or reproducible fault.

What should we include in an enquiry?

Device and version details, an example, the signal path and expected behaviour. Share confidential material only through a separately agreed channel.

Development testing with a defined scope

Our investigation supports your development and release decision. It is not official VESA, HDMI or Dolby certification and does not replace testing by an authorised certification body. Supported devices, formats, measurement methods and interfaces are agreed before the assignment.

Project enquiry

Describe the picture fault and include the system versions, playback conditions and available test material. We agree the scope and technical approach with you.

Discuss display validation

All FF Pictures services