It might just change your viewing experience for the (way) better.
On the right device, HDR can dazzle with its wide range of brightness and color. But one annoyance is that it can change appearance dramatically from one screen to the next. A scene that looks terrific on a high-end TV might have muddy shadows on the wrong phone or blown-out highlights in a dark room. It's a problem that Eclipsa Video, a new open HDR standard, is trying to solve. It's designed to make HDR content play more predictably across devices, apps and lighting conditions.
Google describes Eclipsa Video as a way to make HDR look "consistent, balanced and comfortable on every screen." It's Google's branded version of (the unfortunately named) SMPTE ST 2094-50, a new open standard the company developed alongside Apple and NBCUniversal.
What Eclipsa Video does
The format aims to address HDR's unpredictability with a more flexible set of instructions for displays. That includes how they handle brightness, contrast and highlights as the video changes. It accounts for a screen's capabilities and (on compatible devices) can make changes based on the ambient lighting in your room. The idea is to reduce HDR's pitfalls: crushed shadows, clipped highlights, washed-out tones and sudden spikes in brightness. Ideally, it lets HDR and SDR content coexist without friction on the same screen.
How does it do this? As Google describes it, Eclipsa relies on "two clever pieces of metadata." First, it establishes a white reference anchor, a baseline for mapping SDR content's brightest elements. It then reserves extra brightness for HDR videos. Second, there are headroom-adaptive gain curves, a way for content creators to attach custom instructions within the file. So, if your screen's brightness can't match the video's requirements, this metadata tells it what to do to create just the right effect.
Eclipsa Video vs. Dolby Vision and HDR10
In that way, it's like Dolby Vision: Although the details are different, both use dynamic metadata to adapt the picture as the video changes. Meanwhile, HDR10 is less adaptive, relying on a single set of static instructions for the whole video. (However, the newer HDR10+ variant does use dynamic metadata.)
Another differentiating factor is openness. Eclipsa and HDR10 are built around an open standard. Dolby Vision is a proprietary format.
Platform-wide Eclipsa Video support (playback and capture) is coming to Android 17. It will eventually be available on phones, tablets and TVs. But as with any video format, its wider availability will depend on support from device makers, streaming apps and content providers.
Facts Only
* Eclipsa Video is a new open HDR standard.
* It aims to make HDR content play more predictably across devices, apps, and lighting conditions.
* HDR presents an annoyance because its appearance changes dramatically between screens.
* Eclipsa seeks to reduce HDR pitfalls such as crushed shadows, clipped highlights, washed-out tones, and sudden brightness spikes.
* Eclipsa relies on two pieces of metadata: a white reference anchor for SDR content's brightest elements and headroom-adaptive gain curves for content creators.
* The format accounts for a screen's capabilities and can adjust based on ambient lighting.
* Eclipsa allows HDR and SDR content to coexist without friction on the same screen, ideally.
* Eclipsa is Google's branded version of SMPTE ST 2094-50.
* Platform-wide Eclipsa Video support for playback and capture is coming to Android 17.
* Support for Eclipsa Video will depend on device makers, streaming apps, and content providers.
Executive Summary
Eclipsa Video is a new open HDR standard designed to improve the consistency of High Dynamic Range (HDR) content across different devices, applications, and lighting conditions. The core problem addressed is the unpredictability of HDR where the appearance of a scene varies dramatically between screens due to inconsistent handling of brightness, contrast, and highlights. Eclipsa aims to make HDR content appear consistent, balanced, and comfortable on every display.
The technology functions by using two pieces of metadata: establishing a white reference anchor for SDR content's brightest elements and reserving extra brightness for HDR videos. It also incorporates headroom-adaptive gain curves that allow content creators to attach custom instructions regarding how the video should be rendered when screen capabilities vary from the video's requirements.
In comparison, Eclipsa shares a conceptual similarity with Dolby Vision in that both utilize dynamic metadata to adapt picture presentation based on changing content. HDR10 relies on static instructions for the entire video, making it less adaptive than systems like Eclipsa or the newer HDR10+. Furthermore, Eclipsa and HDR10 are built upon an open standard, whereas Dolby Vision operates as a proprietary format. Support for Eclipsa Video is slated to arrive across Android 17 and will eventually expand to phones, tablets, and TVs, pending support from device makers and content providers.
Full Take
The narrative positions Eclipsa Video as a necessary corrective to the inherent instability of HDR across disparate hardware ecosystems, framing the issue not just as a technical limitation but as an obstacle to a consistent viewing experience for all users. The comparison drawn with Dolby Vision highlights a crucial tension between open, adaptive systems and proprietary ones: adaptability versus ownership. While both leverage dynamic metadata, Eclipsa's focus on an open standard suggests an attempt to democratize HDR consistency beyond proprietary ecosystems.
The introduction of 'openness' as a core differentiator is significant. By basing the standard on open specifications rather than a single proprietary format, Eclipsa seeks to build a foundation where device makers and content providers have standardized ways to handle dynamic signal presentation, which could foster broader interoperability beyond current proprietary walled gardens. The rollout timeline tied to Android 17 suggests an alignment with evolving platform standards, which is a key mechanism for potential adoption.
The underlying implication is a shift from vendor-specific quality control to system-level consistency. If Eclipsa succeeds in making HDR behavior predictable irrespective of the specific display hardware or application context—by abstracting brightness and contrast instructions into flexible metadata—it shifts the burden of achieving visual fidelity from device-specific calibration to standardized content instruction. The critical question for adoption, then, is whether this technical flexibility translates into real-world market adoption without proprietary standards maintaining dominance in the high-value display market. What mechanisms will ensure that the open standard remains the primary driver rather than being sidelined by incumbent proprietary solutions?
Sentinel — Human
The text reads like an informative overview comparing new HDR standards by synthesizing known industry concepts and proprietary information, exhibiting a human editorial structure rather than pure synthetic generation.