HDR Communication & Documentation 3 — Questions and Answers
Question 1: A streaming platform rejects an HDR10 deliverable citing 'missing static metadata.' Which element was most likely omitted from the container?
- Dolby Vision RPU
- SMPTE ST 2086 mastering display metadata and MaxCLL/MaxFALL values (Correct answer)
- HDR10+ dynamic metadata SEI
- HLG OOTF reference display info
Correct answer: SMPTE ST 2086 mastering display metadata and MaxCLL/MaxFALL values
HDR10 requires SMPTE ST 2086 mastering display color volume plus MaxCLL/MaxFALL in the container; their absence triggers rejection.
Question 2: In HDR project documentation, what is the purpose of a 'Color Pipeline Document'?
- To list the hardware serial numbers on set
- To describe the end-to-end color science workflow from camera LUT to final deliverable (Correct answer)
- To track audio sync points
- To document the scheduling of color sessions
Correct answer: To describe the end-to-end color science workflow from camera LUT to final deliverable
A Color Pipeline Document maps every transformation from camera color science through grading to deliverable, ensuring consistency and repeatability.
Question 3: When preparing HDR content change orders after a client review, which detail is most critical to include for the colorist?
- The client's preferred font in the document
- Timecode in/out, scene description, and the specific luminance or color adjustment requested (Correct answer)
- The number of approval signatures obtained
- The name of the QC engineer who reviewed the cut
Correct answer: Timecode in/out, scene description, and the specific luminance or color adjustment requested
Change orders must pinpoint exact timecodes, describe the visual issue, and specify the desired correction so the colorist can act precisely.
Question 4: Why is it important to document which HDR display was used as the mastering monitor in a project's QC log?
- For warranty tracking purposes
- Because mastering display primaries and peak luminance are embedded in SMPTE ST 2086 metadata and affect reproduction on consumer displays (Correct answer)
- To satisfy audio loudness regulations
- Because the display brand determines the codec
Correct answer: Because mastering display primaries and peak luminance are embedded in SMPTE ST 2086 metadata and affect reproduction on consumer displays
The mastering display characteristics define the reference space encoded in ST 2086 metadata, directly impacting tone mapping on consumer devices.
Question 5: A director requests 'the HDR version should feel 10% brighter than the SDR.' How should this instruction be formally documented?
- As a verbal note in meeting minutes only
- As a signed creative intent memo specifying target peak nits, desired perceptual brightness offset, and the reference display for evaluation (Correct answer)
- In the codec settings of the export preset
- In the audio mix notes
Correct answer: As a signed creative intent memo specifying target peak nits, desired perceptual brightness offset, and the reference display for evaluation
Subjective creative directives must be formalized with measurable parameters and a reference display to ensure consistent implementation.
Question 6: Which version control practice is recommended when iterating on HDR grade deliverables?
- Overwriting the previous file with the same name
- Using dated or versioned filenames with changelog entries describing each modification (Correct answer)
- Storing only the final approved version
- Keeping versions only in the colorist's local cache
Correct answer: Using dated or versioned filenames with changelog entries describing each modification
Versioned filenames paired with a changelog allow all stakeholders to track what changed, when, and why across HDR grade iterations.
Question 7: A QC note reads 'false contouring in dark gradients on PQ pass.' What should the production communication to the VFX team specify?
- Increase the output bit depth to at least 12-bit for affected shots and verify dithering is applied (Correct answer)
- Reduce the frame rate to eliminate the artifact
- Apply loudness normalization to the audio track
- Re-encode using H.264 instead of HEVC
Correct answer: Increase the output bit depth to at least 12-bit for affected shots and verify dithering is applied
False contouring in dark areas is typically caused by insufficient bit depth; increasing to 12-bit with proper dithering resolves it.
A streaming platform rejects an HDR10 deliverable citing 'missing static metadata.' Which element was most likely omitted from the container?