Dolby Vision/HDR10 video file defaults to dolby vision

[Nioh8]

• ExoPlayer version number: 2.16.1
• Android version: 9
• Android device: Nvidia Shield Pro 2019

Also referenced in issue #8944

So i am using justplayer (which is using exoplayer) on the nvidia shield to play my blu ray rips. blu ray rips which contain both the dolby vision and hdr10/10+ metadata.

My tv only supports hdr10 but instead of exoplayer recognising both metadata and switching over to hdr 10 it becomes washed out and dull as if dolby vision isn't switching off. I assume thats the issue anyway.

I have tested the same rips of another player on the shield like MX player and the hdr 10 comes through fine.

i could provide a sample rip to test if thats helpful?

i am only assuming this isnt a fault with justplayer and its something to do with exoplayer, my knowledge is limited so if there is anything i can do to help let me know thanks.

[christosts]

i could provide a sample rip to test if thats helpful?

Yes, a link to test content, reproduction steps and a bug report obtained from the device right after the issue occurs help us debug issues like this.

If you're unable to share bug reports or test content publicly, please send them to dev.exoplayer@gmail.com with subject "Issue #9794" . Please also update this issue to indicate you've done this.

Overall, have you tried using the ExoPlayer demo application directly with your content to see what happens?

[Nioh8]

I have sent an email with a link to media that contains the dolby vision/hdr 10 metadata.

as for testing the demo application. the only android enviroment i have is the nvidia shield, i have a windows pc
so i am not sure how i would test that on my end.

also not sure what i would have to do to send a bug report from the shield device.

my best help is the media file i have emailed with a link too, the media file in question i opened up with justplayer on my shield and the issue is the same, the HDR is washed out and the metadata switch over from dolby to hdr10 wasn't happening.

My tv is a samsung HDR10 HDR10+ HLG device.

is there anything more i could provide let me know thanks.

not sure if this would help but here is a link to the issue over on justplayers github. it may elobarate more on what i have tried to explain.

moneytoo/Player#166

[Nioh8]

just a small update, i managed to build the demo for my nvidia shield and assign the media that i was having the HDR issues with, same media as the email link. Same results with the washed out hdr. letting you know if it helps.

[christosts]

Thanks for trying it out on the ExoPlayer demo app. I will need some additional assistance: please play the content with the ExoPlayer demo app (a few seconds will suffice), then grab a bug report from the Shield and send it to us (or attach it on this issue).

I'm interested to see which decoder ExoPlayer picked on your specific setup. I've tried out the content on a few setups I have available:

• content decoded with a DV decoder and displayed on a DV-capable screen
• content decoded with an HEVC decoder and displayed on a HDR10-capable screen

I wonder if in your setup, the player picks the DV decoder and that creates the incompatibility issue with the non-DV capable display.

Thanks

[Rubarius]

Exactly the same problem on iFFalcon 55k61 and TCL v615 only the image turns green or purple. In Vimu in the settings there is a switch that disables Dolby Vision and all movies show normally in HDR, in MX Player I turn on HW, at the top when watching a movie, instead of HW+ and movies get HDR instead of Dolby Vision. I believe that in our case, the switch in the settings that forcibly disables Dolby Vision will help, as it is implemented in Vimu. The players think that there is a DV on the TV and display it on the screen, but the TV itself does not actually support the DV, although the corresponding mode is turned on and the Dolby Vision logo appears.

[christosts]

@Rubarius as mentioned above, we'd appreciate a link to the content and a bug-report taken from the device so that we can inspect how content is being decoded when the issue happens.