Maybe because the display supports both, Plex isn’t doing anything to the video?
I think it was implemented so that HDR10+ is removed when Dolby Vision is present and supported but not HDR10+.
And Dolby Vision is removed if Dolby Vision is not supported but HDR10+ is.
Clearly it’s not correcting the device problem when both are supported.
That’s what I’m wondering - and also wondering if there is any possible fix for it. @sixones any thoughts on this?
That’s what I’m wondering - and also wondering if there is any possible fix for it. @sixones any thoughts on this?
Sorry, I’m a bit confused on what you are asking for here.
Due to various devices having issues, we always strip one or the other.
Hi Sixones,
As mention early, we have an issue with Plex with HDR10+ movies. (HDR10+ movies only, not DV/HDR10+ movies). Only Kodi trigger the HDR10+ on our TV which support HDR10+ and DV.
Regards
The poster’s issue seems that the blank screen on 4K Max still happens when the display supports both HDR10+ and Dolby Vision.
Apologies, too many different issues in a single thread, got a bit turned around.
I know why this could happen as we are detecting your setup supports DoVi, so we are preferring that but we haven’t clarified if the stream itself has DoVi. So we still end up stripping out the HDR10+, will put together a build that will solve this.
Would you be able to fetch logs? We always strip one or the other, so its likely something else going wrong if its still a problem for you.
Steps for fetching logs are available here; https://support.plex.tv/articles/201573117-android-android-tv-fire-tv-logs/
Thanks for clarifying!
Plex DoVi HDR10+ Firestick log.txt (4.7 MB)
Hi sixones,
Please find log attached. As discussed above, I am getting a black screen when the firestick is connected to a TV which can do both HDR10+ and DoVi.
Thanks!
Since the log says
[FFmpeg] [INFO] [StripNALUnitsFilter] Stripping HDR10+ from bitstream
I think in your case you’re running into the issue where Plex can’t disable Dolby Vision on 4K Max when it’s profile 7.
And profile 7 FEL files also cause a black screen.
Maybe Dolby Vision should be stripped when the profile is not supported, and here HDR10+ would be kept.
Would you be able to try this build and see if it solves your problem?
I think in your case you’re running into the issue where Plex can’t disable Dolby Vision on 4K Max when it’s profile 7.
Since it can’t use profile 7, it’s using the HEVC decoder so it should be coming through as standard HDR10. Though maybe the decoder is thinking it can handle the p7 and then fails miserably at it.
This should be solved in this build;
I think you forgot that the 4K Max ignores the picked decoder and always parses Dolby Vision when found in the bitstream.
It’s still not fixed.
Would you be able to provide logs after you replicated the issue?
Well it’s fixed in your build from
But in the latest release (9.31.0), profile 7 isn’t ignored.
And the HDR10+ filter is inserted even though the file isn’t HDR10+.
Log: log.txt (36.4 KB)
In the new build a DoVi strip filter is added.
Work perfectly. Now all the HDR10+ movies and Dolby Vision/HDR10+ load(with a preference for Dolby Vision with movies that have HDR10+ and Dolby Vision).
I still have some issues with some files which trigger Dolby Vision on Plex on my TV but not on my Fire Cube 3rd on Plex/Kodi. Those are converted profile 7 to 8.1. They always fallback on HDR10
If it also doesnt work in Kodi, it’s likely they aren’t being detected as DoVi p8.1. Can you share the XML metadata for one of the files?
Instructions for viewing the XML metadata are available here; https://support.plex.tv/articles/201998867-investigate-media-information-and-formats/
The fix hasn’t been released yet, it will be in v10.0.0 so what you are seeing is the expected behaviour for v9.31.
At the moment we aren’t detecting HDR10+ from FFmpeg (we need to patch it in so PMS knows if a file has HDR10+ or not). So if a file contains DoVi, and DoVi can be played then we always apply the strip HDR10+ bitstream filter, it would end up doing nothing if the file doesn’t contain HDR10+, but it’s still applied for now.
I haven’t had a chance to install 10.0.0.3816 yet, but huge thanks @sixones for being so responsive on this! I’ll try to install tomorrow, hopefully.
There part of the xml of the one of the files(it happen for all my LOTR and The Hobbit Remux).
Here the caracterisks of Fire Cube 3rd Device Specifications: Fire TV Cube | Amazon Fire TV
I will test it on the Fire Stick 4k Max.
Could be a issue with Fire OS and big files because i don’t see any difference between a working DV file and those one.
FilewithDolbyVisionthatdontwork.txt (3.6 KB)
Filewithdolbyvisionthatwork.txt (3.4 KB)
Thanks @sixones, it returns to HDR10 and plays correctly in that build. That said, changing audio tracks causes it to go back to DV and stop working. You have to stop playback, then change audio track, then play, and it works.
The only thing i saw that is different is that on my Remux files converted, the MaxCLL and MaxFALL are present and not on others DV movies or display at Maximum Content Light Level and Maximum Frame Average Light Level. The same thing basically but not display the same.
Edit doesn’t seem to be an issue.
Here the logs which does seems to detect Dolby Vision correctly
logdolbyvisionnotworking.log (78.2 KB)
logdolbyvisionworking.txt (97.5 KB)
Edit 2 : Seem an issue with OMX.amlogic.dolby-vision.dvhe.decoder. So that’s why Kodi is affected too.
Edit 3 : I have uploaded the logs from my Plex app on my TCL c845 which trigger Dolby Vision on these files.
