Dolby Vision now possible through MP4 Mux.

Please post here for issues related to UHD discs
RESET_9999
Posts: 2298
Joined: Mon Aug 05, 2019 7:12 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by RESET_9999 »

daffie wrote:
Mon May 05, 2025 2:26 pm
RESET_9999 wrote:
Mon May 05, 2025 1:27 pm
yes, Profile 5 is supposed to be full range but Apple being Apple as always, all their stuff is in limited range. I don't think it matters though
But Dolby Vision from Apple is kinda crap anyways, right?
Yep, and IMO everything Apple does is garbage (except their ProRes codec).
Trees
Posts: 44
Joined: Sat Sep 03, 2022 8:04 am

Re: Dolby Vision now possible through MP4 Mux.

Post by Trees »

RESET_9999 wrote:
Mon May 05, 2025 1:27 pm
yes, Profile 5 is supposed to be full range but Apple being Apple as always, all their stuff is in limited range. I don't think it matters though
Thank you.

Interesting. Why do you think it doesn't make a difference? Someone asked AI:
When opening a 4K HDR MKV file with MediInfo it has bunch of flags. One of them is Color range; sometimes 4K HDR files have the incorrect limited color range and the correct full range. What does this mean? What does this mean when playing it on a HDR TV? Will the colours display different per setting?

Let's break down color range in the context of your 4K HDR MKV files and what it means for playback on your HDR TV.

What does "Color range" mean?

In digital video, "color range" refers to the range of luminance (brightness) values that are used to represent the colors. There are two main types:

Limited Range (or TV Range): This range uses values from 16 to 235 for 8-bit video. This is the traditional range used for standard definition and high definition television broadcasts. The "black" level is at 16 and the "white" level is at 235.
Full Range (or PC Range): This range uses the full spectrum of values from 0 to 255 for 8-bit video. The "black" level is at 0 and the "white" level is at 255.

Think of it like this: Limited range is like using only a portion of a ruler to measure things, while full range uses the entire ruler.

Why is this relevant for 4K HDR files?

HDR (High Dynamic Range) is designed to display a much wider range of brightness levels than standard dynamic range (SDR). To properly utilize the capabilities of HDR, the video signal should ideally be encoded and transmitted using the **Full Range**. This allows for the deepest blacks and the brightest whites, contributing to the more realistic and impactful image that HDR aims to deliver.

What does it mean when a 4K HDR file has the incorrect "Limited" color range flag?

If a 4K HDR file is flagged as "Limited" range in MediaInfo, it means that the video data within the file is encoded using the limited range (16-235). This is technically incorrect for HDR content, which is designed to use the full range (0-255).

What does this mean when playing it on an HDR TV? Will the colours display different per setting?

Yes, this absolutely will affect how the colors and brightness are displayed on your HDR TV, and the difference can be quite noticeable. Here's why:

Misinterpretation by the TV: Your HDR TV expects HDR content to be in Full Range. When it receives a signal that is flagged as Limited Range but contains HDR data, it has to make an assumption about how to interpret the luminance values.
"Washed Out" or "Crushed" Image:
-If the TV interprets the Limited Range data as if it were Full Range, the image will likely appear washed out. The darkest parts of the image (intended to be 0 in Full Range) will be displayed at the TV's black level corresponding to 16, making blacks look grey. The brightest parts (intended to be 255) will be displayed at the TV's white level corresponding to 235, making whites look less bright and potentially clipping highlights.
- Less commonly, but still possible depending on the player and TV's processing, the image could appear crushed. This happens if the TV incorrectly maps the Limited Range values (16-235) to the full output range (0-255). This would make blacks too dark and highlights too bright, losing detail in both the shadows and highlights.

In summary:

Correct (Full Range) Flag: The video data uses the full range of luminance values (0-255 for 8-bit), allowing for the deepest blacks and brightest whites that HDR is capable of. When played on an HDR TV, the image should look as intended, with vibrant colors and excellent contrast.
Incorrect (Limited Range) Flag: The video data uses a restricted range of luminance values (16-235 for 8-bit). When played on an HDR TV, the image will likely appear washed out or potentially crushed, losing the full impact of the HDR presentation. The colors and overall picture quality will be compromised.

Will the colors display different per setting?

Yes, the setting of the color range flag within the MKV file directly influences how the video is interpreted by your playback software and ultimately your TV.

If the file is flagged correctly as "Full Range": Your playback software and TV should handle the HDR data as intended, resulting in the best possible picture quality.
If the file is flagged incorrectly as "Limited Range": Your playback software and TV might misinterpret the data, leading to the washed-out or crushed appearance described above.

What can you do about it?

Unfortunately, you cannot simply change the "Color range" flag in MediaInfo and expect the video to magically become Full Range. The flag is simply metadata describing how the video data was encoded.

Re-encoding (Complex): The most correct way to fix this is to re-encode the video using the full range. This is a complex process that requires video editing software and a good understanding of video encoding parameters. It's also time-consuming and can potentially degrade the video quality if not done correctly.
Player Settings (Limited Help): Some video players might have settings to force a specific color range output. However, this is often a workaround and may not perfectly correct the issue, as the underlying data is still encoded incorrectly. It's also not guaranteed to work on all players or TVs.
Source Quality: The best solution is to obtain a copy of the 4K HDR file that is encoded correctly with the Full Range flag. This indicates that the source material was likely handled properly during the encoding process.

In conclusion, the "Color range" flag in MediaInfo is a crucial indicator of how the luminance data in your 4K HDR file is encoded. An incorrect "Limited" range flag will negatively impact the picture quality when played on an HDR TV, making the image appear washed out or crushed compared to a correctly encoded "Full Range" file.** Always aim for 4K HDR files that are flagged as "Full Range" for the best viewing experience.
What do you think?
RESET_9999
Posts: 2298
Joined: Mon Aug 05, 2019 7:12 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by RESET_9999 »

I dont know but I think I already tested this a long time ago when I was investigating the iTunes P5 colors shift.
The color range is just a flag and can be changed without re-encoding. You can try, Workflow 9-2 in my script.
Post Reply