Jump to content

Why can some Dolby Vision sources correctly map colors while others cannot?


Recommended Posts

winniewangyh
Posted

I am using the Docker version of Emby with an NVIDIA GPU for hardware transcoding, but some Dolby Vision content plays correctly, while others have incorrect color mapping. What could be the reason for this? For example, the following two movies,If logs are needed, I would be happy to provide them. Please let me know how to obtain them.

image.thumb.png.965b491e5de18fa0f06230de20ecd4d5.png

image.png.f78218368d4b8e1163837b0613762543.png

image.thumb.png.5ef112d5a154922a2f7815379f3e9fd0.png

image.png.f34bd8d6ce58d27c9df373034c4158a8.png

Posted

Some profiles have HDR fallback while others don't..
I can't remember what profiles have the fallback but looking at your pictures the profile 5 video does not.

Emby does not support Dolby Vision tone mapping and there for needs the HDR for that, that's the reason you get strange colors when transcoding.

Reason Emby does not support Dolby Vision tone mapping is because Dolby Vision is a licensed product and Emby does not have a license to be able to legally tone map it.

  • Like 1
Posted

+1, your second example is a pure DV file (profile 5) while the first is most likely an HDR DV hybrid (which can be either profile 7.6 or 8.1). I've played around a little with converting 7.6 to 8.1, some devices are more compatible with 8.1. You can better see the HDR information with mediainfo. But at the end of the day if you're transcoding this content on your playback device you're losing out on the HDR anyway, so you'll want to figure out why it's transcoding in the first place.

  • Like 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...