MrMC

@ Grencola

Ops, you're right

The video on the Russian forum only shows re-authoring a Dolby Vision UHD disc from a retail disc "backup". You can't simply mux the base layer and enhancement layers to a single layer profile. If you aren't working with the master, it has to be re-encoded.

It definitely triggered Dolby Vision, but the colors are completely off.

timstephens24 wrote: 13 May 2018, 21:15 It definitely triggered Dolby Vision, but the colors are completely off.

whew. thanks for confirming colors are off.

wesk05 wrote: 10 May 2018, 21:35 It has Dolby Vision profile 5. There is no BL backward compatibility for this profile. The color space is Dolby Vision native ICtCp.

The guy doing this on makeMKV forum is likely jeopardizing his licenses! (He could very well be an employee working in one of the studios).

@wesk05, can you explain backward compatibility?

I don't have an HDR TV and yet some DV files seem to play with proper color. Other HDR material doesn't. So, I'm wondering if there's some sort of backward compatibility that allows them to play properly on my system?

cosmoxl wrote: 14 May 2018, 20:24 @wesk05, can you explain backward compatibility?

A Dolby Vision stream can be set to be backward compatible with HDR10 or SDR. In MediaInfo, you would see a string like this for Dolby Vision clips - dvhe.dtr@uhd24. The alphabet before "@" is the one that tells you what the backward compbatibility is for the particular clip.
These are the options:
n - no backward compatibility. Only supports ICtCp/ITP.
h - HDR10
r - SDR
b - Blu-ray HDR10

The LG Dolby Vision clips all have SDR backward compatibility. That's why they look normal on your non-HDR TV.

wesk05 wrote: 15 May 2018, 02:16

cosmoxl wrote: 14 May 2018, 20:24 @wesk05, can you explain backward compatibility?

A Dolby Vision stream can be set to be backward compatible with HDR10 or SDR. In MediaInfo, you would see a string like this for Dolby Vision clips - dvhe.dtr@uhd24. The alphabet before "@" is the one that tells you what the backward compbatibility is for the particular clip.
These are the options:
n - no backward compatibility. Only supports ICtCp/ITP.
h - HDR10
r - SDR
b - Blu-ray HDR10

The LG Dolby Vision clips all have SDR backward compatibility. That's why they look normal on your non-HDR TV.

Thanks! That explain it.

Just to clarify properly: no one is working on dual-layer DV support for the Apple box and no one probably will in the next few months, right? No need to drag on that DV topic for months and years if it doesnt happen anywhere.

Someone on Reddit is making good progress on converting single-layer to dual-layer that might be the only chance we will ever get.

Godmax wrote: 15 May 2018, 14:18 Just to clarify properly: no one is working on dual-layer DV support for the Apple box and no one probably will in the next few months, right? No need to drag on that DV topic for months and years if it doesnt happen anywhere.

Someone on Reddit is making good progress on converting single-layer to dual-layer that might be the only chance we will ever get.

"Someone of Reddit" is working in private, they need to share their information so others can help

Godmax wrote: 15 May 2018, 14:18 Just to clarify properly: no one is working on dual-layer DV support for the Apple box and no one probably will in the next few months, right? No need to drag on that DV topic for months and years if it doesnt happen anywhere.

Someone on Reddit is making good progress on converting single-layer to dual-layer that might be the only chance we will ever get.

Apple TV 4K already has support for single-track dual-layer (profile 4) and single-layer (profile 5) Dolby Vision profiles. What it doesn't support is dual-track Dolby Vision profile and it will never support that because it is meant for UltraHD Blu-ray format.

If you want to play Dolby Vision titles backed up from retail UltraHD Blu-rays on Apple TV 4K, you have to convert it to single-track profile 4 or 5. This is what the guy on Reddit is doing, but he is converting it to profile 5 which is not properly supported in MrMC. He should convert it to profile 4 which is properly supported in MrMC.