Dolby Vision is transcoding to green

[Pukerud 1]

I have been looking around and I se a lot of discussion around HDR10 and DV but I can not seem to find an answer to this.

When I play a DV file on my TV everything work perfect (my tv supports DV). But when that same file is play on a device that needs transcoding every thing is green.

I saw there had been added options for HDR tone mapping , but this do not seem to effect DV.

Is there a future plan to support this ? Or am I just doing something wrong ?

 

 

---Edit added later:

To be clear I have tried every option in HDR tone mapping settings:

Edited June 7, 2021 by Pukerud

[Carlo 4560]

Hi, you need to enable tone mapping in the Transcoding menu sections.
This takes a powerful CPU or compatible GPU for tone mapping.

Have you enabled this at all yet to try it?

[Pukerud 1]

Yes, maybe I was not clear enough in my post. But I have tried every option under HDR tone mapping.

[Carlo 4560]

What GPU do you have and what are your current transcode settings looking like?

[Pukerud 1]

1060 3gb

[Carlo 4560]

Could you change the first option to Advanced so we can see more detailed info.

[Pukerud 1]

Sure just tell me what to set, So DV is supported ?

[Carlo 4560]

I looked at the title a couple of times and kept thinking HDR not Dolby Vision.
I believe to play Dolby Vision files this needs to be handled by the client/tv itself as I don't think it's possible to tone map Dolby Vision files at this time.

If I try forcing a transcode on my system of a Dolby Vision file I see a color conversion take place but not a tone map using the "User Sessions" menu option of the diagnostic plugin.

[speechles 2055]

isn't the DV layer some proprietary thing Dolby wants licensing for? The hardware in the Television should handle it but it needs to play direct for that to happen otherwise it will fallback to the HDR layer if there is one. That is why they have dual layer DV.

[Carlo 4560]

13 minutes ago, speechles said:

isn't the DV layer some proprietary thing Dolby wants licensing for?

Yep, that sounds about right.  Dolby wants their fee for anything licensed to decode Dolby media. 

[rbjtech 5284]

Single layer DV (ie BL+EL combined) is the only way to play the DV properly on a DV enabled TV - this works just fine, but during a transcode, the BL (HDR10) is not being used for the tonemap properly - the result is a green image.  I'm not sure if ffmpeg can extract just the BL (as it's now mixed in with the EL) to do the tone map.

Due to licensing, I don't think we will ever get to the situation where the EL layer is read, and tone map applied to that, but maybe it's possible to read just the BL (HDR10) for the tonemap ? 

Definitely a question for @softworkz

 

 

 

 

[softworkz 5066]

Dolby Vision is supposed to be downward compatible to HDR10. This works in some cases, in others it doesn't work. In the future, ffmpeg will be able to read DV metadata (at least some variants of it) and we will be able to do dynamic tone mapping probably.

Anyway, I don't think we have a tone mapping issue here. Probably rather a hw transcoding issue.

@Pukerud - Please try with hw acceleration disabled, and show your hw detection log

[softworkz 5066]

OK, now that the video snippet is working again: It could in fact be one of those DV flavors where tonemapping doesn't work currently.

[Pukerud 1]

hardware_detection-63758731057.txt

ffmpeg-transcode-b7958a97-6e73-4db0-8d2a-e8d8e85b9203_1.txt

Never been asked about a hardware detection log before, so hope I did it correct. If it helps at all. I turned of hw and played the movie again. Same thing green.

 

[softworkz 5066]

Thanks for the logs. It could have been a known decoder bug, but it isn't this is in fact one of those DV files that cannot be tone-mapped at this time, I'm afraid.

[Pukerud 1]

Good to know, am I understanding this correctly then ? It is the ffmpeg software that needs a "fix" and that may come in the future ?

[softworkz 5066]

30 minutes ago, Pukerud said:

Good to know, am I understanding this correctly then ? It is the ffmpeg software that needs a "fix" and that may come in the future ?

Sooner or later: most probably, but to be honest: I don't have a clear picture of these things, because there are so many profiles and sub-variants of Dolby-Vision. For some, there are public and even standardized specs, for others, details a private and need to be reverse-engineered. Some are HDR10 compatible, others are not.

This is a total mess. And absolutely not required to do what it's supposed to do. My personal suspicion is that Dolby does that to confuse all those that are not their licensors and still try to be compatible. Nobody would need Dolby for that at all. I would just avoid Dolby as much as possible. They are not providing an innovation here for which any patents should have been granted.

[vick1982 15]

so I guess this is still not resolved ?  anything I try to play that is dolby vision doesn't get tone mapped right... just funny green 

[softworkz 5066]

8 hours ago, vick1982 said:

so I guess this is still not resolved ?  anything I try to play that is dolby vision doesn't get tone mapped right... just funny green 

No. That's something different. Please start a new topic for "funny green"  

[Pukerud 1]

10 minutes ago, softworkz said:

No. That's something different. Please start a new topic for "funny green"  

Why is that something different? I would describe the clip in my post as "funny green". IF it is the same thing as I show in my clip vick1982. It is still not resolved. I changed preference to HDR 10+ instead of DV because of this.(I download in DV first and watch it DIRECT PLAY, then its downgraded to HDR 10+ after a while)

Edited November 15, 2021 by Pukerud
Direct Play

[softworkz 5066]

Sorry, I understood your saying "just funny green" like you would see a screen that is totally green (single color) - that would be a different issue, because green is the equivalent to "all pixels zero" in the YUV color space.

Now I've seen your videos above and yes, this is the one DV profile that nobody can play correctly at the moment (besides licensors of DV).

What I can say for rather sure is that we won't have it before ffmpeg or VLC. HDR10+ is a very good choice anyway and in a while we'll also be able to handle dynamic scene lighting data with tone mapping.

 

[vick1982 15]

On 15/11/2021 at 16:38, Pukerud said:

Why is that something different? I would describe the clip in my post as "funny green". IF it is the same thing as I show in my clip vick1982. It is still not resolved. I changed preference to HDR 10+ instead of DV because of this.(I download in DV first and watch it DIRECT PLAY, then its downgraded to HDR 10+ after a while)

yep... obviously I was talking abut the same issue... anyway so answer is Dolby vision files still don't play right.

[softworkz 5066]

38 minutes ago, vick1982 said:

so answer is Dolby vision files still don't play right.

The precise answer is that certain DolbyVision videos (of a specific profile) can't be displayed correctly. 

[FrostByte 5392]

Long version:

The best thing to do is stay away from DV profile 5 material (stuff from Disney+, Netflix, etc) if your video path doesn't support DV as there is no secondary HDR10 layer to fall back on with these files.  This stuff will look green or purple on nonDV setups.

The DV profile 7 stuff found on UHD discs has a secondary HDR10 layer which nonDV setups can fall back on and still trigger HDR. 

Tone mapping only works on HDR10 (at least as of now) and not the DV layer itself which is proprietary as mentioned earlier.

You can see the DV profile of your stuff by using the open source app mediainfo.

 

DV profile 5 with no HDR10 layer

HDR format : Dolby Vision, Version 1.0, dvhe.05.06, BL+RPU 

DV profile 7 with the secondary HDR10 layer

HDR format : Dolby Vision, Version 1.0, dvhe.07.06, BL+EL+RPU, Blu-ray compatible / SMPTE ST 2086, HDR10 compatible 

 

 

[rbjtech 5284]

QQ @FrostByte - I've only tested single layer DV7 profile with transcode/tonemapping (it's ok), I've never tested it using a dual layer DV7 profile.  I presume this is ok as technically the first layer is HDR10 anyway - has anybody confirmed this ?