Source-Side vs Display-Side Tone Mapping

Mechanism: Where Tone Mapping Occurs

Tone mapping is essential because HDR video signals encode luminance and color ranges that exceed what most displays can produce. The signal must be remapped to the display's actual brightness ceiling and color gamut.

Display-side tone mapping is the traditional approach: the TV receives an HDR signal and internally adjusts it to match its peak brightness, contrast capabilities, and color volume. The display performs this remapping without knowing the content creator's intent or the specific display model that will receive the signal.

Source-side tone mapping (SBTM) shifts this responsibility to the video source device (a streaming box, game console, or built-in TV app). The source queries the display's capabilities via EDID (Extended Display Identification Data), a handshake that travels through the HDMI DDC channel when you connect a cable. Using this data, the source device pre-adjusts its output before sending it to the display, theoretically producing an image optimized for that specific TV's performance.

EDID: The Capability Handshake

For source-side tone mapping to work, the source must know what the display can do. EDID communicates this automatically: supported HDR formats, peak brightness, color gamut, panel type, and other metadata. When a source device reads EDID through the DDC channel, it can configure its output to take full advantage of the display's potential rather than applying a generic tone curve that compromises both bright and dark content.

Static vs. Dynamic Metadata: The HDR Format Difference

The effectiveness of tone mapping depends partly on how the content is mastered. HDR10 uses static metadata, a single tone mapping curve applied to the entire title. Dolby Vision uses dynamic metadata adjusted per scene or frame, allowing different tone mapping for sequences with different brightness profiles. Dynamic metadata preserves highlight detail in bright, high-contrast shots that static tone mapping would clip; it also maintains shadow separation in dark scenes.

Source-based tone mapping works with both formats but is especially valuable for Dolby Vision content, where the source can apply dynamic adjustments tailored to each display rather than the display applying a one-size-fits-all curve after the signal arrives.

Double Tone Mapping: When Source and Display Conflict

If both the source and display perform tone mapping simultaneously, the result is double mapping, a compound compression that damages the image. Bright highlights clip from the first mapping, then the display's second mapping compounds the loss. Shadows crush because two tone curves applied in series compress the lower luminance range twice. Colors can appear unnaturally dense because luminance is compressed while chroma saturation is preserved or boosted.

HGiG (HDR Gaming Interest Group) specifies that gaming consoles should handle tone mapping based on the display's EDID data, and displays should disable their internal tone mapping to prevent double mapping. This coordination ensures the image reaches its intended look.

Real-World Scenarios and Platform Differences

Source-based tone mapping is most valuable in mixed-content scenarios: when HDR and SDR content, graphics overlays, and dynamic metadata coexist on the same screen. Streaming devices like Roku and Fire TV historically had limited access to display capability data, forcing TVs to handle tone mapping entirely. Built-in TV apps had an advantage because they could access internal TV data directly, creating inconsistent viewing experiences between the same TV's built-in Netflix app and an external streaming device.

SBTM addresses this by giving external streamers access to display capability signals, leveling the playing field. Both the transmitting device and receiving device must support SBTM for the feature to function.

On Android platforms, operating systems now provide consistent tone mapping across rendering components (HWC, SurfaceFlinger, and app layers). Before Android 13's tone mapping library, display-specific tone mapping operations weren't shared between these layers, causing visible quality differences; most noticeably when screen rotation switched between GPU and DPU rendering paths.

Complementary, Not Replacement

Source-based tone mapping does not replace HDR10, HLG, or other HDR standards. It complements them as an additional capability that improves consistency and image quality when both source and display support it.